**** BEGIN LOGGING AT Thu Oct 10 02:59:57 2019 Oct 10 03:07:58 https://elinux.org/ECE497_Project:_XBee <<<--- is anyone working or has already worked on this project? Oct 10 03:21:20 I am receiving a segmentation fault as an error when I run the software on that page. Oct 10 03:22:09 Now. One of my XBee radios is plugged in via the MikroeBus Cape and the other is plugged in via breadboard. Oct 10 03:22:53 There is one issue. Oct 10 03:23:18 I do not have a resistive sensor. I have other sensors, though! Oct 10 03:23:33 ambient light or tmp? Oct 10 03:24:16 Currently, I am just trying to light up the LED w/ the .c source. Oct 10 03:45:59 https://pastebin.com/sEkef0Bf is my problem right now. I do not think that my, on my current kernel, uart files are located here. Oct 10 03:54:53 It's interesting that, UARTs being declared obsolete by microsoft in the mid 90's, the IO type seems to have been awfully persistent and useful to this date. Oct 10 03:55:13 Yep. Oct 10 03:55:23 I like serial interface stuff. Oct 10 03:55:36 It can read and write from far distances. Oct 10 03:55:45 they'll never go away, it's just a super simple low pincount form of bidirectional communication Oct 10 03:55:57 Never! Oct 10 03:56:32 but yeah they're dead on consumer PCs, which I'm guessing microsoft's statement was about Oct 10 03:56:32 Do either of you know where my uart files are located on the BBB w/ kernel 4.14.x? Oct 10 03:56:51 set_: uart devices? hasn't changed in years Oct 10 03:57:03 Since 2012? Oct 10 03:57:13 Seven years ago... Oct 10 03:57:13 oh dunno about that long Oct 10 03:57:16 Ha. Oct 10 03:57:30 though actually yeah I think the backwards compat symlinks still exist Oct 10 03:58:05 Hmmm. I will check online and see if I can find out where in the world is my uart located. Oct 10 03:58:16 should be ttyS Oct 10 03:58:25 /dev/ttyZZZN Oct 10 03:58:37 so the /dev/ttyOn (for n=0..5) paths will still work, although they're now symlinks to the new /dev/ttySn (for same n) Oct 10 03:58:42 Dang it. Oct 10 03:58:46 I should have known this. Oct 10 03:58:48 ah there we are, thanks zmatt :D Oct 10 03:58:58 I had a feeling it was something .. slightly unusual :D Oct 10 03:59:08 I even typed in /dev/ttyS2 for UART2. Oct 10 03:59:15 yep, that's the path Oct 10 03:59:20 Sheesh. Oct 10 04:00:48 Now, why would this fellow in that paste show his class initializeXbee() as /sys/kernel/debug/omap.../.../...? Oct 10 04:01:03 context? Oct 10 04:01:13 whatever he's doing there definitely no longer applies Oct 10 04:01:16 I cannot wrap my head around it. Oh. That paste I just posted. Oct 10 04:01:18 Aw! Oct 10 04:01:21 lemme see Oct 10 04:01:41 yeah that's some ancient way to do pinmux Oct 10 04:01:43 Right so anyhow Wait you have to have root access for that. Oct 10 04:01:55 https://pastebin.com/sEkef0Bf <<--- this one Oct 10 04:02:02 so nowadays you'd use config-pin for that Oct 10 04:02:08 Hmm. Oct 10 04:02:14 to configure the pins to uart mdoe Oct 10 04:02:16 *mode Oct 10 04:02:22 Oh. Oct 10 04:02:25 Right. Oct 10 04:02:31 you've done it before Oct 10 04:02:34 I know about config-pin. Oct 10 04:02:37 Right. Oct 10 04:02:46 I'd ignore 90% of what's on elinux.org .. so much of it is obsolete, its not even funny Oct 10 04:03:01 especially if you know stuff if from 2012 Oct 10 04:03:02 there shoudl be a half-life of articles on there Oct 10 04:03:12 Oh. Dang. So, Everything I just tried that I figured out how to make is useless. Great. Oct 10 04:03:25 Awesome! Oct 10 04:03:43 veremitz True I'm not even sure how to classify that stuff half the time. Oct 10 04:04:44 So, if I take out the .c source for making UART2 available on my BBB, config-pin would take its place? Oct 10 04:08:03 Nope. Oct 10 04:08:55 yep Oct 10 04:09:30 the code in that pastebin is completely replcaed by two invocations of config-pin (one for the rx pin, one for the tx pin) Oct 10 04:09:35 *replaced Oct 10 04:09:44 https://github.com/duganje/ECE497_XBEE/tree/master/ForceResistor <<<--- Not in this particular example. Oct 10 04:09:45 What? Oct 10 04:10:31 I know but I have made too many changes thus far. I will use config-pin for my uart channels but... Oct 10 04:10:48 oh god this code is horrible Oct 10 04:11:10 You should see how I changed everything to make things work (does not work). Oct 10 04:11:15 why the fuck is it opening and closing the serial port for every send/receive Oct 10 04:11:21 I do not know. Oct 10 04:11:23 ? Oct 10 04:11:29 very few changes should be needed Oct 10 04:11:44 basically just taking out the stuff in initializeXbee() in XBee.c Oct 10 04:12:14 The makefile was busted. I had to go into that file to switch initializeXBEE() to initializeXbee(). Oct 10 04:12:15 and the readAnalog() in sendResistor.c will need some tweaking Oct 10 04:12:35 Right. I just want to make it available for gpio30 for a LED. Oct 10 04:12:35 ?? Oct 10 04:12:48 but honestly most of this example is just silly Oct 10 04:12:52 Look at the makefile. It is incorrect for the class. Oct 10 04:12:54 Oh. Oct 10 04:13:14 I don't see anything wrong in the makefile, what are you referring to exactly? Oct 10 04:13:25 But since I am taking out that class. XBEE instead of Xbee. Oct 10 04:13:26 Only. Oct 10 04:13:38 in the makefile. See now? Oct 10 04:13:39 I don't understand what you're talking about Oct 10 04:13:44 no, not even a little bit Oct 10 04:13:49 Please hold. Oct 10 04:13:52 the file name is XBee.c Oct 10 04:13:53 not XBEE.c Oct 10 04:14:03 I know. I am talking about the Makefile. Oct 10 04:14:04 so the capitalization in the makefile is correct Oct 10 04:14:08 so am I Oct 10 04:14:09 Right. Oct 10 04:14:24 the makefile seems perfectly fine Oct 10 04:14:28 Okay. Oct 10 04:15:28 anyway, this example is just measuring an ADC and writing it to the serial port Oct 10 04:15:33 Right. Oct 10 04:15:43 that's much better done in something like python than C Oct 10 04:15:56 O,o Oct 10 04:15:57 especially since this C code is written more inefficiently than most python code would be :P Oct 10 04:16:03 -,- Oct 10 04:16:05 Ha. Ha. Ha. Oct 10 04:16:20 Still, it is a nice example for me try. Oct 10 04:16:27 not really Oct 10 04:16:38 Okay. Moving on. Oct 10 04:16:47 zmatt: I thought the python interface libraries were problematc, or has this been resolved.. Oct 10 04:16:49 if you want to confirm serial communication via the xbee module works, just confirm that directly, e.g. interactively using the python REPL Oct 10 04:17:05 veremitz: what libraries? pyserial is fine Oct 10 04:17:13 ah pyserial is well-tested, sure Oct 10 04:17:21 I was thinking more IO Oct 10 04:17:22 that's the only library oyu need Oct 10 04:17:27 yip Oct 10 04:18:13 if you do want to read an adc value or toggle a gpio, you can do either of those things in a single line of python using the pathlib library (which is part of the python standard library) Oct 10 04:18:33 ah neat, so the underlying stuff is working fine then :D Oct 10 04:18:47 what? opening a file and reading/writing a value? Oct 10 04:18:54 I really ought to plug my BBB back into something :D Oct 10 04:19:01 I pity the programming language where this doesn't work properly Oct 10 04:19:39 I assume fileIO is adequate for most basic functions Oct 10 04:20:12 esp. for toggling an LED :D Oct 10 04:20:15 technically it's actually better to use low-level write() than a buffered file output stream for sysfs attributes, but the C code set_ dug up doesn't do that either (it uses fprintf) Oct 10 04:20:33 yoikes Oct 10 04:21:10 but since a single char is being written it ultimately doesn't matter Oct 10 04:21:41 (or more generally something that's so small it will assuredly end up in a single write() call) Oct 10 04:22:33 maybe I should make a good python gpio library some time Oct 10 04:22:57 :D Oct 10 04:26:07 I should I use pathlib to show if the radios are configured properly? Oct 10 04:26:31 I don't know what you mean by that Oct 10 04:26:46 nothing in the code example you showed is doing anything with radio configuratoin Oct 10 04:26:49 *configuration Oct 10 04:26:54 Oh. Oct 10 04:27:07 I thought that this stuff was for XBee stuff? Oct 10 04:27:22 Please hold. Oct 10 04:27:29 presumably the code assumes it has already been setup to act like a serial port Oct 10 04:27:46 an end-to-end serial connection between devices I mean Oct 10 04:28:07 https://elinux.org/ECE497_Project:_XBee is what I found and how I came across this info. on github. Oct 10 04:28:08 Oh. Oct 10 04:28:47 Okay, so there is no way to set up the devices unless I use the digi software to set up the radio understanding of communication. Oct 10 04:29:17 via XCTU? Oct 10 04:30:01 I don't know anything about XBee Oct 10 04:30:12 Okay. Oct 10 04:30:13 No issue. Oct 10 04:30:20 they claim they make wireless stuff easy, so if you have any issues with it, take it up with them :P Oct 10 04:30:28 Otay! Oct 10 04:30:41 I can set up the devices for use w/ the BBB. Oct 10 04:31:06 Okay, it is a little more complicated than previously thought. Oct 10 04:31:17 Back to the old drawing board. Oct 10 04:31:58 is it? I don't see anything on the wiki page that seems to suggest any setup is required for the modules Oct 10 04:32:10 I'm not sure how they work then, but hey :P Oct 10 04:32:22 yeah my recollection was they were a wireless serial port, essentially Oct 10 04:32:29 with all the things Oct 10 04:32:36 They work in many ways. Oct 10 04:32:45 I could use usb or direct connections. Oct 10 04:32:45 veremitz: how does it know who its peer is? Oct 10 04:32:54 but I'm sure our friend here wants to do something Different Oct 10 04:32:56 Software via XCTU! Oct 10 04:33:15 set_: usb? when did usb come into the picture? Oct 10 04:33:18 zmatt: good question .. I've not used one yet. Perhaps they use a standard 'ID' ? Oct 10 04:33:29 I thought these people at the elinux page were figuring it out w/ software instead of XCTU. Oct 10 04:33:53 set_: seriously, forget elinux. That's gonna cause you a *lot* of pain. Oct 10 04:33:53 set_: their setup just seems to be "connect the module and use it" Oct 10 04:33:57 i.e. no setup required Oct 10 04:34:06 I can plug a XBee w/ a module adapter w/ USB into the BBB. Oct 10 04:34:28 veremitz: Okay. Oct 10 04:35:06 I mean, you could do that if you want to... I wouldn't want to, but you be you :P Oct 10 04:35:07 Well, maybe I just did not make them both discoverable to each other yet and that is the reason why they are not working. Oct 10 04:35:14 I be me! Oct 10 04:35:18 what module are oyu using? Oct 10 04:35:46 @zmatt: This is a long story but the XBee modules are not spaced correctly for the Breadboards. Oct 10 04:36:04 that's most definitely not what I asked Oct 10 04:36:13 you shouldn't need a breadboard anyway Oct 10 04:36:23 Therefore, a module is needed to put it on the Breadboard or to use it via usb. Oct 10 04:36:34 I'm sure there's an xbee cape (or several...) Oct 10 04:36:43 The usb-XBee module I have is the Wireless Connectivity Kit. Oct 10 04:36:44 or you can use jumper wires ;) Oct 10 04:36:54 there is, but a cape seems overkill considering you basically just need a few wires Oct 10 04:36:58 ^ Oct 10 04:37:03 There is a MikroeBus Cape. Oct 10 04:37:16 I wouldn't touch this mikrobus crap with a ten foot pole Oct 10 04:37:21 Okay. Oct 10 04:37:25 That might be another issue. Oct 10 04:37:49 but that's another example of a "cape" that's basically just a few wires Oct 10 04:37:56 Right! Oct 10 04:38:01 Easy, peasey. Oct 10 04:38:17 meanwhile, you haven't answered my question Oct 10 04:38:22 Yes I did. Oct 10 04:38:28 oh Oct 10 04:38:30 Wireless Connectivity Kit. Oct 10 04:38:44 that sounds like a horribly generic term, is that really its name? Oct 10 04:38:52 Yes. Oct 10 04:39:04 https://www.digi.com/products/models/xkb2-a2t-wwc this? Oct 10 04:39:12 It is dated from 2011. Oct 10 04:39:29 That is it. Oct 10 04:39:33 But... Oct 10 04:39:54 oh there's more than one Oct 10 04:40:11 I am using a soldered pinout board that just makes the spacing better for breadboards. Oct 10 04:40:33 and... Oct 10 04:40:39 The MikroeBus Cape. Oct 10 04:40:46 w/ Xbee click board. Oct 10 04:41:22 I set all this up to make it work but I forgot the XCTU software set up. Oct 10 04:41:26 This was my fault. Oct 10 04:41:43 I forgot to make sure the two XBee modules were paired. Oct 10 04:42:05 But, w/ the terrible source from that example, I might just try another example. Oct 10 04:42:12 Right/ Oct 10 04:43:50 so I'm pretty sure the elinux page example is for much older/dumber modules that don't really have any setup Oct 10 04:44:12 Oh. Oct 10 04:44:14 Okay. Oct 10 04:44:16 Great. Oct 10 04:44:21 Or good. Oct 10 04:44:32 I will try another example some day. Oct 10 04:48:25 also, I'm confused about your statement you're using the xbee click, since that seems to require you to solder on a raw module, while the kit you mentioned has modules with pins Oct 10 04:50:42 using the dev boards included with the kit and connecting those via usb would probably indeed be the least error-prone method of getting them to work, plus it has useful buttons and leds Oct 10 04:51:15 once you have that working you can focus on moving to a direct connection between module and BBB Oct 10 04:58:08 * Humpelstilzchen wonders whys he sees every morning a conversation with set_ in the backlog **** BEGIN LOGGING AT Thu Oct 10 10:50:10 2019 Oct 10 11:25:08 Anyone know what is the proper place to report bugs with the rcn-ee Buster snapshot images? I just flashed one to my BBB and it fails to start DHCP servers for its usb0 and usb1 connections. The connection itself works, if I assign a static IP on my laptop I can connect to the BBB. It seems that no dhcp server is started and running /opt/scripts/boot/autoconfigure_usb0.sh manually does not start it either. Oct 10 12:03:42 rcn-ee[m]: ^^ Oct 10 13:41:34 blathijs: which image? console/iot/etc... Oct 10 13:49:48 rcn-ee[m]: Console, should have mentioned that Oct 10 13:50:30 and which snapshot version/date number. :) that way i can check. Oct 10 14:38:20 blathijs: console images don't ship dnsmasq, maybe i should add it, as we do ship the wirless-tools... the idea behind console, it was a bare-min, and you do what you want.. Oct 10 14:47:12 Ah, so it is by design. Bit unexpected for me, though I only recently switched from iot to console, so I guess I never tried the USB networking since then. Oct 10 14:48:13 simpler setup is to use systemd-networkd... it's already installed anyway, and then you can remove ifupdown, connmand, and any package with 'dhcp' in the name ;) Oct 10 14:48:23 i can add it, doesn't make sense to have the wireless tools in a base image, but not dnsmasq... You just the first to bring it up.. Oct 10 14:49:02 well you don't need dnsmasq to use it as wifi client obviously Oct 10 14:49:17 rcn-ee[m]: I might have asked this before, but is there any place that documents all the images available for the BB that could at least document this? I've found the BB images offering a bit confusing, with some images from your domain, some from the bb.org domain, different snapshots, etc. Oct 10 14:49:32 problem with usb networking not working out of the box is that not all beaglebones have ethernet, and wifi needs setup before it works, so how are you going to get into your beaglebone? serial console? :P Oct 10 14:50:04 blathijs: beagleboard.org are offically blessed.. everything else is just "testing" to get blessed.. Oct 10 14:51:09 zmatt: which is why it would make sense for the console to get it back.. (thinking pocketbeagle) the original idea behind console, here's somethign smalll do what ever you want.. (made sense in the BBB only days) Oct 10 14:51:30 rcn-ee[m]: yeah, but you do need to get *into* the system first Oct 10 14:51:50 It's a bit weird that there is no official bare console image, then. I previously assumed that the IoT was that, but then discovered (after putting a few in production) that those images have tons of unsecured crap that I didn't need. Oct 10 14:52:21 blathijs: well the "console" isn't offical.. Oct 10 14:54:47 blathijs: https://github.com/beagleboard/image-builder/commit/83f7386f5b5eab586379d4c5f0d7ff336cffa75f so it'll work on next Monday's weekly build.. Oct 10 14:56:54 rcn-ee[m]: anyway, I can actually highly recommend systemd-networkd... like if you'd want simple usb networking on the console image, you'd just have a script set up the usb part (I just put g_ether in /etc/modules but as usual a more complicated solution is needed for triple-platform support) and have the interfaces configured by systemd-networkd... something along the lines of ... Oct 10 14:57:00 ...https://pastebin.com/X97bJNff Oct 10 14:57:00 that requires the minimum amount of packages Oct 10 14:57:26 namely... systemd. Oct 10 15:00:45 rcn-ee[m]: Yeah, so I'm saying there *should* be an official console image. Oh well, great that there is a non-official one :-) Oct 10 15:01:08 rcn-ee[m]: Thanks for fixing this? I'll doublecheck if just install dnsmasq on a running image makes it work as well. Oct 10 15:02:00 As for systemd-networkd, haven't played with it, but it seems useful at first glance :-) Oct 10 15:02:12 blathijs: Jason's hates there are "two" images on beagleboard.org, i don't think he want's another one.. Remember each image needs to be fully tested... We don't have those resources.. Oct 10 15:02:43 blathijs: I've been using it for years now on laptop, server, and embedded... it's not perfect, but I'm quite happy with it Oct 10 15:03:53 for wireless I just have wpa_supplicant manage the wifi part standalone (it doesn't need a network management to tell it what to do, it can do a fine job on its own) and when it brings up the link systemd-networkd will take care of configuring it (dhcp and such) Oct 10 15:04:08 *a network manager Oct 10 15:06:52 rcn-ee[m]: I can confirm that installing dnsmasq indeed makes DHCP work Oct 10 15:07:35 thanks blathijs ! Oct 10 19:54:34 Humpelstilzchen: I like to discuss things. I will try to refrain. Oct 10 19:56:53 @zmatt: My connections are these ---> BBB(1) and xbee S2C. Then, BBBW(2) to xbee S1 via breadboard set up. Oct 10 19:57:58 Oh and the xbee S2C is set up by way of Mikroe Bus Cape on BBB(1). Oct 10 19:58:05 ... Oct 10 19:58:25 Anyway, I will set up the radios w/ the XCTU software to make sure they both are paired to one another first. Oct 10 20:25:16 like I said before, you may want to consider using the dev boards included with the kit to connect the modules via USB, at least initially... once you have working software you can then look into connecting them more directly Oct 10 20:25:54 but then at least you will know your software is working, hence any issues would be due to the connection... instead of having to wonder where the problem lies when it (inevitably) doesn't work at first Oct 10 20:26:13 Okay. Oct 10 20:26:28 I will try to connect via those USB connections. Oct 10 20:28:44 Just for reference, I also have a book on the subject, "Hands On XBee Lab Manual, Titus," that has worked while sending communication to light LEDs. Oct 10 20:28:52 Thank you for your help. Oct 10 20:28:57 of course if you want to use a direct uart connection right away that's fine too, but then focus on confirming the bbb<->module communication works for each module before trying to get them to communicate with each other Oct 10 20:29:11 Right, good idea. Oct 10 20:29:12 or trying to get any sort of high-level example working Oct 10 20:29:19 Okay. Oct 10 20:29:54 So, make sure the BBB can recognize the uart connections from the Xbees? Oct 10 20:29:56 using usb initially lets you defer that until later Oct 10 20:30:39 that's a really strange way to phrase it Oct 10 20:30:49 oh. Oct 10 20:30:50 Okay. Oct 10 20:31:16 You are right. Oct 10 20:31:23 I mean making sure the BBB<->module serial connection is working (i.e. the hardware connection is okay, you're using the right uart/pins, the pins have been configured correctly, etc) Oct 10 20:31:39 Oh. Got it. Oct 10 20:32:30 when using usb that part is free, but when using wires or a breadboard or this weird mikrobus setup, obviously all sorts of things can be wrong Oct 10 20:33:09 Right. I see that the MikroeBus Cape needs Number Three on the Cape to be occupied by the XBee S2c. Oct 10 20:33:23 That is the one w/ the UART connections. Oct 10 20:33:30 But... Oct 10 20:33:32 That shall wait. Oct 10 20:34:49 I think the hardest part is the set up on the XCTU software. I have to read up on it more. making these radios work is not plug and play. Oct 10 20:36:11 is the zigbee module you're using a through-hole or surface-mount version? (I couldn't tell from the Kit's documentation which one it actually uses) Oct 10 20:36:15 *xbee sorry Oct 10 20:37:22 (i.e. https://www.digi.com/products/models/xbp24cdmuit-001/product-images/xbee-pro-s2c-th-ufl vs https://www.digi.com/products/models/xb24cdmris-001/product-images/xbee-s2c-smt-rfpad Oct 10 20:37:27 ) Oct 10 20:40:14 Surface mount. Oct 10 20:40:59 the xbee s2c on the click board is surface mounted. Oct 10 20:42:40 I have the click board from Mikroe and it is a surface mount type. Oct 10 20:44:08 I have both of the xbee modules datasheets open now. Oct 10 20:44:11 so... this is the part where I'm slightly confused... that xbee module already came on the click board right? so what did you get in the kit exactly? Oct 10 20:44:21 because the kit comes with two modules right? Oct 10 20:44:43 yea. That one kit has S1 through hole Xbees. Oct 10 20:45:59 The Wireless Connectivity Kit has the Xbee S1 modules but I am using one from that kit on a breadboard and the other one is a MikroeBus Cape click board type module. Oct 10 20:46:02 also, how are you able to use that XCTU software to configure the xbee that's on the click? like, how do you connect it to your PC? Oct 10 20:46:14 are the S1 and S2C modules compatible with each other? Oct 10 20:46:18 yes. Oct 10 20:46:21 I looked that up. Oct 10 20:46:31 The S2c is compatible w/ the S1. Oct 10 20:47:15 Back in the day, since the S1 and S2 are legacy products, these two could not communicate. Oct 10 20:47:27 But, w/ the S2c version, compatibility is not an issue. Oct 10 20:47:45 ok Oct 10 20:49:27 Let me try to configure these xbees real quickly. Oct 10 20:58:40 Okay. I tried some pyserial communication on /dev/ttyS2 but the XCTU software cannot find the module (XBee S2C). Oct 10 21:00:13 set_: xbee's thru xctu need all the usart pins.. (unless you reset the module your self..) Oct 10 21:01:19 Oh. Oct 10 21:01:21 Okay. Oct 10 21:01:59 i used a few mikro xbee's i used this adaper and 6 wires: https://www.sparkfun.com/products/11697 Oct 10 21:02:05 I will go and set up XCTU software w/ the two S1 (legacy) modules instead. Oct 10 21:02:06 Okay. Oct 10 21:02:41 From sparkfun's picture (4th picture)... bottom 4 wire GND, v3.3, DOUT, DIN Oct 10 21:03:01 +rcn-22[m]: I Have a Wireless Connectivity Kit too. It comes w/ two xbee connection dongles. Oct 10 21:03:12 on the right side DIO4, RTS Oct 10 21:03:46 yeah, but the Mikroe can't be plugged into anything, you'll need to fly wire those 6 wires.. Oct 10 21:03:52 Oh. Oct 10 21:03:53 Okay. Oct 10 21:04:03 Thank you. Oct 10 21:04:18 I was thinking I could just use the click board as is. Oct 10 21:04:25 (and the firmware on the mkroe was ancient... download the "old" firmwares in xctu..) Oct 10 21:04:50 once you update, you can ignore the old firmware options later.. Oct 10 21:04:57 Okay. Oct 10 21:08:43 Okay. I am in XCTU now. Oct 10 21:09:02 Both XBee S1 boards are connected and ready for take off. Oct 10 21:09:14 I will try w/ the BBB later on. Oct 10 21:21:04 I got the two S1 xBees communicating. Oct 10 21:21:10 via serial. Oct 10 21:21:19 on XCTU only. Sorry. Oct 10 21:50:42 oh there's more than one "xbee-s2c" ... how annoying Oct 10 21:53:22 ditto s1 Oct 10 21:57:08 oh never mind apparently they just differ in firmware Oct 10 21:58:53 @zmatt: Are you still reading on Xbee stuff? Oct 10 21:59:28 I got the Xbee S1 modules on the Grove Development Boards (Wireless Connectivity Kit) to work but not w/ the BBB yet. Oct 10 22:00:07 I am about to try. It seems there is some library for it but I figured I would use .c instead of java. Oct 10 22:03:22 https://github.com/digidotcom/xbee_ansic_library/ is what I found. Oct 10 22:04:20 I saw they also have python code Oct 10 22:05:00 but when it's operating in transaparent serial mode (which is the default mode), you don't really need any library other than pyserial Oct 10 22:05:23 Oh. Oct 10 22:13:18 ok well it seems like with the mikrobus cape you won't be able to use hardware flow control for the uart (on any of the four slots), so that's already pretty shit Oct 10 22:14:15 Okay. No issue. Oct 10 22:14:32 I have four or five of this little, handy modules. Oct 10 22:14:49 ? Oct 10 22:15:00 Two S1 modules that i can connect via breadboard thus far and some other modules. Oct 10 22:15:26 or I can connect the S1 modules by way of USB like you described. Oct 10 22:15:57 I can take off the mikroebus cape and use the BBB pins instead. Oct 10 22:16:15 or use USB w/ the Wireless Connectivity Kit (Grove Connectors). Oct 10 22:16:39 I found the Python Library too. Oct 10 22:16:52 uhh options 3 and 1 sound like they're the same thing? Oct 10 22:17:13 unless you mean to actually use the grove connectors... they don't seem to have any useful use as far as I can tell Oct 10 22:17:41 No. Oct 10 22:17:49 The Grove connections are not good. Oct 10 22:18:05 I haven't looked at the python library code so I don't know what it does exactly or if it's any good :P Oct 10 22:18:38 I looked around and could not figure it out. It think it just sets the boards up for "readiness." Oct 10 22:18:50 I do not think I can use it for changing the state of sensors. Oct 10 22:19:16 what sensors? Oct 10 22:19:41 looks like the python library is pretty featureful Oct 10 22:19:52 Well, I wanted to try to set up the Xbee modules on the BBB to run sensors of some sort. First, an LED would be a nice start. Right? Oct 10 22:20:05 Or...what did you think? Oct 10 22:20:22 xbee just offers communication, what you do with that communication is not the concern of the xbee modules nor any python library for them Oct 10 22:20:24 Did you just want me to connect to the BBB and transfer data? Oct 10 22:20:32 Oh. Oct 10 22:20:33 Okay. Oct 10 22:20:42 I got you. Oct 10 22:23:33 anyway, like I said, in transparent mode you don't need any python library other than pyserial Oct 10 22:24:08 since the xbee modules will basically behave as if they form a direct serial connection between the two BBBs Oct 10 22:25:31 nevertheless, using the xbee python library offers richer features Oct 10 22:25:43 and the docs seem quite good Oct 10 22:25:57 and have step by step instructions Oct 10 22:25:59 https://xbplib.readthedocs.io/en/latest/getting_started_with_xbee_python_library.html Oct 10 22:26:20 (reminder: as always, use "pip3" instead of "pip") Oct 10 22:28:03 Okay. Oct 10 22:28:08 I will test it soon. Oct 10 22:28:33 I will bbl. I have to check on granny-littles. Please forgive me for leaving in the heat of this discussion. Oct 10 22:28:57 there's no discussion heat :P Oct 10 22:29:02 and also, I'm off myself Oct 10 22:29:07 Fine. Oh! Oct 10 22:29:10 Off is nice! Oct 10 22:29:25 Breathers! Oct 10 22:29:40 bbl. Peace out for now. Oct 10 22:32:15 rcn-ee[m]: those mikro bee products are fucking awesome Oct 10 22:33:24 And there is a book about it!! "Hands On XBee Lab Manual, Titus". Woohoo!! Oct 10 22:35:04 what is "awesome" about them? they just took a standard module and put a non-standard connector on them :P Oct 10 22:36:47 (which means fewer signals of the module are accessible, and in combination with their mikrobus cape for bbb you don't even get working flow control) Oct 10 22:37:38 holy shit and they're expensive Oct 10 22:37:40 zmatt: i will tell you in a couple of miniutes, going for a smoke first Oct 10 22:37:54 compare: https://www.mikroe.com/xbee-click vs https://www.adafruit.com/product/968 Oct 10 22:37:55 and yes i do very much think they're great Oct 10 22:38:11 whjk Oct 10 22:38:15 k Oct 10 22:39:27 zmatt: what do you think of the ft232h chip? is it stupid because all the native protocls are simplke and easy to implement oneself., and you can just get spomething else from the shelf to do the same thing? (ok, no i'm going for a smoke, biab) Oct 10 22:40:19 is that question supposed to be related to this or is it a random one? Oct 10 22:41:24 I'm not really sure what you mean anyway... it's an usb to serial converter Oct 10 22:47:20 also nice... I see the xbee click has a trace and a via in the antenna keepout region (i.e. the area where the xbee module docs specify that no metal is allowed on any layer of your pcb) Oct 10 22:55:54 actually, better value for money would be https://www.sparkfun.com/products/15126 Oct 10 23:04:51 zmatt: sorry to leave you hanging, i've got lots of pots on the boil, catch you next... Oct 10 23:14:55 Otay. Oct 10 23:15:23 The BBB does power the S1 Xbee and Connectivity Kit. Oct 10 23:18:48 Off to test XTCU config. w/ two BBBs and the S1s kit. Oct 10 23:21:52 How would I test the usb connection on the BBB to see if the "Connectivity Kit" works w/ the S1 Xbees? Oct 10 23:22:02 why the interest in Zigbee? Oct 10 23:22:23 They have a long range and I wanted to try them out years ago. Oct 10 23:22:31 why not LoRa? Oct 10 23:22:34 I never got time b/c i got caught up doing other things. Oct 10 23:22:43 I think LoRa might even be more difficult. Oct 10 23:24:38 Well, the kit does not allow for me to upload the config. to the xbees via XCTU and plug and play. Oct 10 23:24:39 ... Oct 10 23:24:48 via USB, anyway. Oct 10 23:25:40 should be pretty straight forward ;) Oct 10 23:26:28 I figured this much. Oct 10 23:26:34 Boy, was I wrong. Oct 10 23:27:12 some of them are just like a modem Oct 10 23:28:38 Right but w/ my knowledge, handouts and hand-me-downs are just fine. I build still. I do not make my own things just yet. Oct 10 23:29:04 Zigbee can have a lot of protocol stuff Oct 10 23:29:31 You mean, like w/ location and usage? Oct 10 23:30:46 So, I see i have a 232 serial IC on my BBB now. Oct 10 23:31:09 I think this is the Xbee. Oct 10 23:32:29 I guess I should be in serial instead of ssh now. Sheesh. Oct 10 23:33:03 Zigbee has keys and other details... donno if those Xbee shields hide that detail or not Oct 10 23:34:38 I think the 802.15.4 Xbee I am using are not the Zigbee protocol ones. Oct 10 23:34:50 Zigbee is 900 mhz. Oct 10 23:35:13 I have two S1 Xbees I am using right now. They are legacy products. Oct 10 23:35:39 set_: I pointed to the getting-started of the python xbee library, it seemed quite detailed on how to get started Oct 10 23:36:04 including first testing with a python script for one side and xctu on the other side Oct 10 23:36:10 Oh? Oct 10 23:36:16 I must have read over that idea too quickly. Oct 10 23:36:20 I must have missed it. Oct 10 23:36:54 Okay. Oct 10 23:36:56 I Found it. Oct 10 23:37:01 I am on that page. Oct 10 23:37:03 Off to test. Oct 10 23:37:19 ds2: Sorry man. I am a bundle of joy w/ this Xbee stuff right now. Oct 10 23:38:35 ds2: these things can even simulate a point-to-point serial link (after initial setup using their software), so then the application code doesn't need to know anything at all about the wireless stuff Oct 10 23:39:05 although that doesn't seem like a great way to use the modules... it obviously doesn't scale Oct 10 23:39:46 zmatt: ah... the flip side is those things don't expose the low level zigbee details? Oct 10 23:40:41 I haven't really examined what their API exposes Oct 10 23:42:04 these aren't zigbee modules anyway Oct 10 23:43:10 https://xbplib.readthedocs.io/en/latest/api/digi.xbee.devices.html#digi.xbee.devices.Raw802Device Oct 10 23:45:01 okay that isn't as informative as I hoped Oct 10 23:45:11 they can be :D Oct 10 23:45:14 it all looks pretty low-level to me though Oct 10 23:45:25 not the S1 modules he has I think? Oct 10 23:45:32 *he's using right now Oct 10 23:45:57 it looks like XBee expanded the name beyond Zigbee Oct 10 23:48:07 dunno what the history behind the name is since the older modules don't appear to suport zigbee Oct 10 23:48:14 unless I didn't look carefully eonugh Oct 10 23:48:56 yeah the S1 is just "802.15.4 Oct 10 23:48:57 " Oct 10 23:48:58 zigbee is a different protocol and implementation. Oct 10 23:49:02 i just remember them from a trade show...was expensive for what it was Oct 10 23:51:36 xbee is a serial (async) port extension where as zigbee is an actual packet exchange format based on IEEE 802.15.4 Oct 10 23:53:19 well xbee just seems to be a product family... maybe their transparent serial protocol is similar regardless of the underlying protocol used? that part seems mostly useless anyway, and fortunately you can entirely ignore it Oct 10 23:57:29 Probably a good way to look at it. Zigbee is a HL communication standard from the Digi who makes the xbee. Xbee treats the radio more like a modem. Oct 10 23:58:08 Well PC modem of old anyhow. Oct 10 23:59:00 you seem to be referring the transparent serial mode... but like I said, that mode seems pretty useless to me compared to the full API they expose Oct 10 23:59:52 unless you literally just want to replace a serial link by a wireless one Oct 10 23:59:58 then I guess it's convenient Oct 11 00:00:01 Yea boy! Oct 11 00:00:15 replace the serial by Wireless! Oct 11 00:00:25 Sorry. Oct 11 00:00:32 set_: ? Oct 11 00:00:50 not applicable to you Oct 11 00:01:15 Oh. Oct 11 00:01:17 No issue. Oct 11 00:03:44 GenTooMan: btw are you saying Digi had a primary role in the creation of ZigBee? I can't really find much about the history of the protocol, but they currently are only a mid-tier member of the Zigbee Alliance Oct 11 00:18:06 @zmatt: You were right about the library. It is a nice one. Oct 11 00:18:14 Python3 compat. only too! Oct 11 00:19:45 On these specific "Capes" for the Xbee Modules (the connect. Kit), only allows for ADC, PWM, and Digital I/O. I think. Oct 11 00:21:22 But...UART is available on the S1 xbee modules as pin names, e.g. RX/TX. Oct 11 00:21:40 set_: uhh what are you talking about? Oct 11 00:21:50 No clue. Oct 11 00:21:59 also don't worry about the xbee module pins for now, you're using the usb thing remember Oct 11 00:22:10 Do not worry. I will keep on trying to wrap my head around these facts. Oct 11 00:22:11 Right. Oct 11 00:22:23 I have the USB connected and it works. Oct 11 00:22:25 so it should show up on the bbb as a serial port (probably /dev/ttyUSB0 or so) Oct 11 00:22:30 Right. Oct 11 00:22:34 ttyUSB0. Oct 11 00:22:43 which is the port you'd specify to the python library Oct 11 00:23:01 that's all you should need to follow their getting-started example Oct 11 00:23:25 I typed up my python code thus far, local_xbee = XBeeDevice("/dev/ttyUSB0", 9600) Oct 11 00:23:33 Okay. Oct 11 00:23:54 I am trying to read some I/O lines right now. Oct 11 00:24:08 ?? Oct 11 00:24:25 how about just following the getting started guide first? Oct 11 00:24:31 instead of doing random other stuff Oct 11 00:24:35 Further down in their site, there are some ideas. Oct 11 00:24:43 it works. Oct 11 00:24:59 The getting started guide works. Oct 11 00:25:16 glad to hear, then you can proceed to the rest of their docs Oct 11 00:25:22 Right! Oct 11 00:25:34 you can ignore the "Handle analog and digital IO lines" section, there's nothing useful there Oct 11 00:25:41 Okay. Oct 11 00:25:57 there's no point in using those signals on the xbee module since the beaglebone has plenty of IO capabilities already Oct 11 00:26:06 Aw, right. Oct 11 00:26:43 But controlling it from the BBB might make a good tutorial for people like me who do not understand common sense in electronics. Oct 11 00:26:54 bzzt. bzzt. Oct 11 00:27:38 wait it supports doing IO on a *remote* xbee device? you're just allowed to do that? wtf Oct 11 00:27:47 Yes! Oct 11 00:27:55 Nice, heh? Oct 11 00:28:00 no Oct 11 00:28:04 No? Oct 11 00:28:11 well Oct 11 00:28:12 depends Oct 11 00:28:21 That is what is nice w/ these devices. Oct 11 00:28:27 I thought, anyway. Oct 11 00:28:45 Like a BBBW to BBBW but in a different sort of way. Oct 11 00:31:50 my point of concern would be security :P Oct 11 00:32:20 Right, but there are ways to control security. Oct 11 00:32:22 but okay, ignoring that, if this actually works I can see it might have some value Oct 11 00:32:29 Nice! Oct 11 00:32:33 Now you are talkin' Oct 11 00:32:38 for some limited applications Oct 11 00:32:50 Right. PWM, digital, and ADC. Oct 11 00:33:06 I guess digital would be GPIO? Oct 11 00:33:14 yes Oct 11 00:33:19 Extra nice! Oct 11 00:33:21 anyway, I was going to zZ Oct 11 00:33:24 No! Oct 11 00:33:35 Okay. I accept you have to sleep too. Oct 11 01:20:04 Well. I got the Xbee to send messages from the BBB to my computer at home but no IO stuff yet. Oct 11 01:20:18 "home is where my bbb is!" Oct 11 01:27:04 cliche? Oct 11 01:38:29 Dudes, I can do it. It works w/ XCTU and to serial communication from the BBB to the Xbee S1. Oct 11 01:38:43 ADC, here I come! **** ENDING LOGGING AT Fri Oct 11 02:59:59 2019