**** BEGIN LOGGING AT Mon Nov 15 02:59:57 2021 Nov 15 03:01:40 Hello, Nov 15 03:02:37 Can anyone please guide me how to acquire data from a sensor through USB Host in Beaglebone black? Nov 15 03:09:18 Um, what data are you trying to acquire and what sensor are you using? How are you trying to acquire it? UART? GPIO? Um, SPI? Nov 15 03:10:45 I used a python script once to get data from a sensor...I put it in .csv format for later! Is this what you are describing? If not, there are many ways, methods, and different ideas to gather before answering so quickly. Nov 15 03:11:08 ... Nov 15 03:11:13 All I can do is try to help. Nov 15 03:12:18 https://web2.norsonic.com/product_single/soundlevelmeter-nor139/ Nov 15 03:13:23 I have to acquire data from this sensor. It has USB output so it would be better if I can acquire through USB Nov 15 03:13:36 oh. Nov 15 03:13:37 Okay. Nov 15 03:13:47 Please hold. Let me look up ideas... Nov 15 03:15:16 Sure. Thanks Nov 15 03:17:10 I think you can just use a SD Card on this thing to track environmental measurements and then put it in the 'puter. Nov 15 03:17:25 What USB type does it have on it? Nov 15 03:18:44 I see. USB 2.0 and RS232! Nov 15 03:19:30 Are you going to use the BBB w/ it? Nov 15 03:19:57 Plug it in and see if they have an open source lib. in their ranks! Nov 15 03:20:07 I will keep checking. Nov 15 03:20:15 I will use industrial BBB and cellular modem cap Nov 15 03:22:16 Oh. Hey, I see they have a user manual but it needs one to sign in and deal w/ these people. Nov 15 03:22:49 I am not going to sign in. Maybe someone else can help, i.e. one that deals w/ these people. I am sorry. Nov 15 03:23:04 But...if they have a SDK to use, show it. I can maybe help then! Nov 15 03:26:23 I have that document Nov 15 03:26:31 How can I share with you? Nov 15 03:28:52 Google Nov 15 03:29:02 do a share w/ google Nov 15 03:29:08 or pastebin Nov 15 03:29:15 It's a pdf. Nov 15 03:29:19 google Nov 15 03:30:15 Do you have the SDK or the manual? Nov 15 03:31:53 I have a manual. Nov 15 03:32:02 oh. Nov 15 03:32:36 So, once we figure out how the thing understands things, we can then use Linux and the BBB to procure the data? Nov 15 03:33:04 I mean...you are using your BBB for the procurement right? Nov 15 03:33:18 Yes that's right Nov 15 03:33:57 Okay, skip the manual for now. Once you plug in the device to your bbb and look for what is available on USB devices on the BBB, what do you see? Nov 15 03:34:23 it should be in /dev/ Nov 15 03:34:35 USB0 or USB1 or whatever... Nov 15 03:34:57 or...does it come across as something completely different? Nov 15 03:35:11 Bus 001 Device 004: ID 0403:d920 Future Technology Devices International, Ltd Nov 15 03:35:11 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Nov 15 03:35:32 Hmm. Is it plugged in? Nov 15 03:35:40 Yes Nov 15 03:36:33 when I plugged in Bus 001 Device 004 appear Nov 15 03:36:45 Okay...let me see. try this when it is not plugged in: ls -la /dev/tty* && ls -la /dev/* Nov 15 03:36:57 Then, when it is plugged in, type the same thing to figure out what device shows up. Nov 15 03:37:19 There should be a difference in available ports on the /dev/ dir. Nov 15 03:38:01 That thing looks nifty but I do not think they are Open Source. Are they Open Source? Do they offer open schematics and open source SDKs? Nov 15 03:38:42 I don't think they are open source Nov 15 03:39:01 Okay. Hmm. So, w/ that in mind... Nov 15 03:39:20 They gave a document that has set of commands to interact with device Nov 15 03:40:39 1. I think that gathering data outside of their normal way is impossible. 2. There is no way for the BBB to access the data in SD Card format unless you build something, i.e. SD Card port on the Linux bound BBB. Nov 15 03:40:59 Or...RS-232 port? Nov 15 03:42:17 I agree with you. It seem that it is bit tricky Nov 15 03:42:23 *seems Nov 15 03:42:23 Well... Nov 15 03:43:07 I was going to ask someone else who is more inclined to know how things work on the BBB, e.g. does the SD Card holder have access to be read/write from and so on? Nov 15 03:43:18 Now, I think if you have a SD Card to USB dongle... Nov 15 03:43:26 Then, you can read and write to the card. Nov 15 03:44:00 But...I do not know of such a dongle outside of one person. Some guy from NY builds them. Nov 15 03:44:08 Or...you can build it. Nov 15 03:45:12 Nope. Never mind me. It seems we are at odds w/ building something. You need a RS-232 to SD Card reader or a SD Card to USB reader. Nov 15 03:45:28 Hmm. That sounds neat. Nov 15 03:46:47 Do you mean from the sensor SD card to USB or RS232 reader? Nov 15 03:48:07 So, the USB on the BBB. That USB needs a dongle to read/write to SD Cards. I think this is the only way to get your SD Card data from the Nor-139 and parse it or whatever you plan on doing w/ it. Nov 15 03:49:50 The person from NY stopped producing the USB-to-SD dongles. Odd. Nov 15 03:49:54 Oh well. Nov 15 03:50:17 His might have been backwards in this form of operation anyway. Nov 15 03:51:50 Hmm. This brings up an interesting question. Is there such a dongle for use in Linux outside of popular brands? Nov 15 03:51:56 In that can I will have to remove the SD card from Nor-139 and connect to SD cards to USB converter? Nov 15 03:52:04 Right. Nov 15 03:52:50 The SD Card connector on the BBB does not allow for use outside of pushing an image from it, right? Let me double check. Nov 15 03:53:43 The Nor-139 will be away from the lab so it is not feasible to do that. I need to acquire data remotely Nov 15 03:54:25 Yep. So, the SD Card connector on the BBB is only for a secondary boot source. Nov 15 03:54:33 Oh. Nov 15 03:54:44 Do you use AT Commands? Nov 15 03:55:19 So, the BBB and Nor-139 are attached already and remote. Nov 15 03:55:21 Okay. Nov 15 03:55:45 And...can you connect to the BBB remotely? Nov 15 03:56:36 Yes I use AT Commands. Nov 15 03:57:10 The plan is to attach BBB and Nor-139 and operate remotely Nov 15 03:57:31 I am planning to get a cellular cape for BBB Nov 15 03:57:45 For remote communication Nov 15 03:58:12 Oh. Nov 15 04:01:27 Hmm. Nov 15 04:02:10 So, what language do they say you can use w/ the AT Commands? Nov 15 04:03:26 Their SDK or language, from scratch, needs you to have access to all available datasheets, connections, and to know the language of use. Nov 15 04:03:29 Right...so. Nov 15 04:03:46 ls -la /dev/tty* Nov 15 04:04:00 If you are remote, ssh in and type that idea out. Nov 15 04:04:27 If you cannot turn off the module from a remote location, can you reboot it? Nov 15 04:05:13 You can probably have access to the BBB and data but the location of the tty device needs to be known. Nov 15 04:06:11 On the BBB used, you definitely need your /dev/ttyS* or /dev/ttyUSB* locations known. Nov 15 04:07:37 For instance, just try this out. You have a XBee for instance, use the AT commands to set up your connection, pair them, and then have those modules/modems chat w/ each other either by way of AT or python for instance. Nov 15 04:08:21 So, then, even in that circumstance, you will need to have the device location on your BBB system. Nov 15 04:08:31 Even if it is by USB connections... Nov 15 04:10:41 find your device list and list them, know them, and use them. Nov 15 04:12:08 ssh username@ip_address Nov 15 04:12:28 or ssh name@location Nov 15 04:13:13 then... ls -la /dev/tty* Nov 15 04:13:39 Oh. I see the issue. Nov 15 04:13:54 Time to use all our TTY devices to find it. Nov 15 04:13:56 Dang. Nov 15 04:15:12 Let me test real quickly. Nov 15 04:17:02 I am going to type ls -la /dev/* when nothing is plugged in via the USB connector on the BBB. Then, I will plug something into the USB connector after it is shutdown. I will start it again and type ls -la /dev/* Nov 15 04:17:12 Then, I can find what is going on during the process. Nov 15 04:19:45 You want me to shutdown the sensor> Nov 15 04:21:35 No. Nov 15 04:21:41 Do not worry about it. Nov 15 04:22:10 I am setting up a system right now. I will show you what is available during on and w/ nothing in the USB Port. Nov 15 04:22:40 Then, I will boot w/ a USB dongle connected. I will find something to stick in the USB Port and then run ls in the /dev dir. Nov 15 04:23:03 5 minutes. Nov 15 04:23:58 Sure. Take your time, I will wait. Nov 15 04:26:13 Okay. It is just two photos I am setting up. ls in the /dev dir. Nov 15 04:31:37 So, this is the /dev dir. w/out anything attached to the USB on the BBB: https://imgur.com/a/JmWonPv Nov 15 04:32:41 Hmm. Nov 15 04:32:43 This is odd. Nov 15 04:32:59 My board is not showing ssh'ing is available when USB gadgets are attached. Nov 15 04:33:19 scratch that. I am in. Nov 15 04:33:55 try /dev/ttyUSB0 Nov 15 04:34:12 Guest82: that lsusb output looks like it shows up like an ftdi serial device, presumably an integrated usb-serial converter in the device connecting to a serial interface Nov 15 04:35:18 do have documentation of that serial protocol? Nov 15 04:35:20 *do you Nov 15 04:37:30 I have a user manual of the device Nov 15 04:38:17 can you share it? Nov 15 04:38:33 annoying that the manufacturer doesn't simply put it online :/ Nov 15 04:40:12 hmm, and they have software for doing this but it's Windows-only Nov 15 04:40:16 https://drive.google.com/drive/folders/1YZZLhdbZdCYDbT6Fl-ExfWoyWXnlWG63?usp=sharing Nov 15 04:41:22 set_ /dev/ttyUSB0 is not working Nov 15 04:42:03 what are you trying to do with it? Nov 15 04:42:04 Hmm. Did you ssh in and then write a script to read your data? Nov 15 04:42:51 Guest82: @zmatt is by far more experienced in this field if you need technical typing. Seriously. Nov 15 04:43:57 but...I can try to see what they have posted in the .pdf files. Nov 15 04:44:04 zmatt I need to acquire data to BBB from this sensor (Nor-139) and push it to the sever remotely Nov 15 04:44:31 yes I meant, what did you try just now that's "not working" ? Nov 15 04:44:47 set_ Thanks for that Nov 15 04:45:18 I am trying to connect sensor to BBB Nov 15 04:45:36 no issue. I usually beat around the bush for years. @zmatt is a pro at technical chats. Nov 15 04:45:38 I am in very early phase of this task Nov 15 04:46:13 He even has a nice way to configure things quickly! Nov 15 04:46:13 Guest82: what did you mean by "/dev/ttyUSB0 is not working" ? Nov 15 04:47:37 I mean I couldn't see USB device Nov 15 04:47:45 on the BBB? Nov 15 04:48:02 Yes Nov 15 04:48:19 but when I do lsusb I get this Nov 15 04:48:28 yes you already showed the lsusb output Nov 15 04:49:05 When I remove the sensor from BBB FTDI  disappears Nov 15 04:49:11 based on which I would definitely expect it to show up as /dev/ttyUSB0 Nov 15 04:49:32 Right...the BBB has only USB device, i.e. /dev/ttyUSB0. Nov 15 04:49:40 ehh, no Nov 15 04:49:44 No? Nov 15 04:50:07 Well, it can support more but the BBB has one USB Port. Nov 15 04:50:08 non-acm usb serial devices (such as FTDI serial devices) are simply numbered sequentially as they are discovered Nov 15 04:50:09 Sorry. Nov 15 04:50:16 Oh. Nov 15 04:50:34 (and you can have multiple when using a usb hub) Nov 15 04:50:44 Right. That is what I was thinking. Nov 15 04:50:56 but since this is the only usb-serial device connected, it would normally be /dev/ttyUSB0 yes Nov 15 04:51:11 Right. That was my thought. Nov 15 04:51:18 Guest82: after plugging it in, can you grab the last bit of kernel log using: dmesg | tail -n 20 Nov 15 04:51:27 and then share it using pastebin.com or some other paste service Nov 15 04:51:35 (don't paste it directly into chat) Nov 15 04:52:01 the documentation seems very sparse about the serial communication Nov 15 04:52:20 they mostly seem to expet you to use their software, which only runs on Windows Nov 15 04:52:23 *expect Nov 15 04:55:59 https://imgur.com/a/ja0tB1M Nov 15 04:57:03 hmm, no driver seems to be leading for it Nov 15 04:57:09 *loading Nov 15 04:57:57 They have got windows USB driver software Nov 15 04:58:43 well yes because windows sucks and doesn't really have class drivers, but any ftdi device would normally just work on linux... lemme look up that vid/pid Nov 15 05:00:10 w/out the driver, how is one supposed to use it at all? Nov 15 05:00:12 hmm, 0403 is FTDI alright, but 0403:d920 isn't in the usb IDs database Nov 15 05:01:03 set_: linux has a driver for ftdi devices (ftdi_sio) Nov 15 05:01:18 I know but I figured this one was a special case. Nov 15 05:02:28 it's just not in the list, presumably because it's a really obscure device and noone has bothered to add it Nov 15 05:02:53 It even seems like a weird link outside of http/https. Nov 15 05:03:01 ?? Nov 15 05:03:08 I looked up their website. Nov 15 05:03:36 it stated ww3 or wwd or something first and then their site. Nov 15 05:03:44 Let me go and check again. Nov 15 05:03:50 Guest82: there's probably a way to force the ftdi_sio driver to be used for this device Nov 15 05:03:59 (and if that works, to request it to be added to the list) Nov 15 05:04:09 Yes! Nov 15 05:04:13 True.Its weird.  It's a Japanese firm. Nov 15 05:04:53 Oh. It is https://web2. and then the site. Nov 15 05:05:00 Oh well. Nov 15 05:05:25 How can one force the FTDI driver so it can be used in Linux? Nov 15 05:06:17 zmatt How can we do that? Can you please elaborate on that? Nov 15 05:06:23 I am checking Nov 15 05:06:40 Sure. Thanks Nov 15 05:07:18 Hmm. Nov 15 05:07:23 So, it may be a COM port. Nov 15 05:07:25 Guest82: try removing the device, then executing the following two commands on the beaglebone: https://pastebin.com/pRX6RHq7 and then plug it back in Nov 15 05:07:36 Right-o! Nov 15 05:07:39 Nice. Nov 15 05:09:25 I looked at the commands. That is neat. Nov 15 05:09:46 so, echo'ing and then piping the rest handles this issue? Nov 15 05:12:50 I will try that now Nov 15 05:18:23 So, linux can overwrite, w/ tee, your driver for your module? I never knew. Nov 15 05:19:01 I looked up tee w/ examples. I have not used that command in some time. Hmm. It sounds neat. Nov 15 05:19:40 I'm just using it as a way to write something with root privileges Nov 15 05:19:45 Usually, one would just use it to produce stdout to file(s). Nov 15 05:19:46 Oh. Nov 15 05:20:17 since you can't do 'sudo echo blah >file' since that applies sudo to "echo blah" (which doesn't need it) rather than to the redirection to file Nov 15 05:20:47 Right. I did learn you can sudo sh "echo blah > /file" Nov 15 05:21:58 A short bit ago, that is exactly what i was looking to do. I never once thought of tee. Nov 15 05:22:06 that works too yes Nov 15 05:23:44 https://pastebin.com/CiqMdeSj Nov 15 05:24:04 well there ya go Nov 15 05:24:06 Seems it's working Nov 15 05:24:21 Damn! Nov 15 05:24:32 Sorry. Dang! Nov 15 05:24:45 That is near awesome. Nov 15 05:24:47 this chat is not PG-rated :P Nov 15 05:25:10 I try though. It is hard not to hold back but I try anyways. Nov 15 05:26:10 I cannot believe Linux is that powerful w/ a two-line command. Nov 15 05:26:43 I wonder now. Guest82: Be careful! Who knows who would want to find out about your hearing tests. Nov 15 05:27:02 Sound acquisition or however you are using this device. Nov 15 05:27:22 Will it be too much if I ask you some more help to understand how to acquire data to BBB from this sensor Nov 15 05:27:24 ? Nov 15 05:28:03 No. It is not too much to ask. I say, use an easy scripting lanuage where you can install /dev/ttyUSB0 into it as a device to use. Nov 15 05:28:03 it kinda is since it's just too poorly documented. however, there's nothing BBB-specific about this task Nov 15 05:28:45 Thank you very much for help me fix zmatt Nov 15 05:29:04 *helping me fix it Nov 15 05:29:18 from this point on you can do serial communication with the device, the details of doing so are however device-specific Nov 15 05:29:20 Oh. I thought you were thanking me for fixing @zmatt. Ha. Nov 15 05:29:52 note that you'll need to execute these two steps each time after boot, unfortunately Nov 15 05:30:01 Write a script! Nov 15 05:31:14 Can one write a script even if modprobe is used? Nov 15 05:31:31 I did not even know modprobe worked on the BBB. Nov 15 05:31:51 uhh, why wouldn't it? it's part of every linux system Nov 15 05:32:09 I was unaware. I must have been using it incorrectly. Nov 15 05:32:39 the main problem is that the usb device needs to be plugged in *after* performing these steps... there's probably a way to force linux to rescan/reprobe the device, but I don't know off the top of my head how to do that Nov 15 05:33:09 If you could share any example code for serial communication that would be great? Nov 15 05:33:23 that's just way too generic a question Nov 15 05:33:24 If you have any Nov 15 05:33:32 I can try but do not laugh. Nov 15 05:33:33 like, what programming language? Nov 15 05:33:37 set_: please don't try Nov 15 05:33:40 Fine. Nov 15 05:33:55 That saves me a headache. Nov 15 05:33:58 Python would be great Nov 15 05:34:16 Guest82: I'm pretty sure pyserial is installed by default Nov 15 05:34:18 on the BBB Nov 15 05:34:20 But I don't mind if you have it in other programming language Nov 15 05:34:52 I can check on my side. What kernel and image are you using, Guest82? Nov 15 05:35:00 kernel is irrelevant Nov 15 05:35:11 Oh. Nov 15 05:35:13 Okay. Nov 15 05:35:57 you can confirm it's installed by doing e.g. python3 -c 'import serial' Nov 15 05:36:11 I say kernel b/c of what is available in the languages used in each, different kernel. For instance, in Python3.7 to Python3.9, some has changed. Nov 15 05:36:21 (which will print nothing if it's installed, or something like "ImportError: No module named serial" if it's not installed) Nov 15 05:36:37 set_: that still has nothing to do with kernel Nov 15 05:36:55 Okay. Okay. Nov 15 05:37:13 and current debian buster images ship with python 3.7, not 3.9 Nov 15 05:37:20 Right. Nov 15 05:37:46 Guest82: https://pythonhosted.org/pyserial/shortintro.html Nov 15 05:38:10 You are right about that idea. I was using the Bullseye and noticed that by default, 3.9 is used. Nov 15 05:38:32 So, I figured there was some reason for this upgrade. Nov 15 05:39:12 @zmatt It is not installed. I get an ImprtError message Nov 15 05:39:28 Guest82: just checking, you're using "python3" and not "python" ? Nov 15 05:40:08 ("python" in debian buster still refers to the (obsolete) python2 for backwards compatibility reasons) Nov 15 05:40:30 Yes I am using python3 Nov 15 05:41:24 okay then just install it using "pip3 install pyserial" Nov 15 05:41:34 Like w/ C/C++ and their standards. When you stdout to file in Linux, you can see all the warnings from the different versions of C/C++ from a SDK install, e.g. C++ 11 may want it this way while C++ 17 uses this difference in source and those warnings are dedicated these different syntaxes used in each different verioning. Nov 15 05:42:05 set_: what on earth are you rambling about now? Nov 15 05:42:07 ... Nov 15 05:42:16 Never mind me. I almost made sense. Nov 15 05:43:21 C++ 11 wants their syntax this way while C++ 17 wants their syntax this way. When I have used and esp. while installing SDKs, the warnings from gnu C or C++ has these warnings from when building the SDKs. Nov 15 05:43:50 Those warnings are what should be updated in source. Nov 15 05:43:56 Sometimes. Nov 15 05:44:03 that is all. Nov 15 05:44:06 generally getting warnings has more to do with the compiler version than with the C++ standard version Nov 15 05:44:28 but also, what does this have to do with anything? Nov 15 05:44:43 Both actually, right? Nov 15 05:44:46 Oh... Nov 15 05:45:00 Nothing. Just chatting about how to update a SDK in general. Nov 15 05:45:14 Like librobotcontrol for instance. Nov 15 05:45:20 Is there a way to save this chat? I will be useful if I have to go back and check Nov 15 05:45:29 In Bullseye, GNU-10 is around now. Nov 15 05:45:46 Guest82: https://libera.irclog.whitequark.org/beagle/2021-11-15 Nov 15 05:46:15 So, that compiler needs specificities on the language to compile correctly. Nov 15 05:46:36 I get why it is a compiler issue but I may never get to compiler quarks in time. Nov 15 05:46:49 quirks. Sorry. Nov 15 05:47:21 Many thanks @zmatt Nov 15 05:47:37 Both C/C++ is long enough w/ their rules and that is outside of the compilers they use. Nov 15 05:47:49 guess now thta people are around I'll repost my question really quick Nov 15 05:47:59 No! Nov 15 05:48:02 Just kiddin'. Nov 15 05:48:04 When trying to boot one beaglebone, I see this in the logs: http://0x0.st/-RqQ.txt Nov 15 05:48:11 The other one boots fine off the same card Nov 15 05:48:35 Is the NIC dead? Can I do anything else to find out or mitigate without a USB UART Nov 15 05:48:36 mewt: you mentioned arch linux, have you tried an official beagleboard.org debian image? Nov 15 05:48:42 (I have one coming) Nov 15 05:49:11 I recently started using BBB. So recommendation to get good information? Nov 15 05:49:24 I can do that tomorrow Nov 15 05:49:32 I'll report back with results I guess Nov 15 05:49:59 Anyway...I tried to boot into a Bullseye image w/ librobotcontrol under GNU-10 and got past the warnings (luckily) but the usage is busted for now. Nov 15 05:50:10 I cannot test all drivers while passing. Nov 15 05:50:35 So, I will look into my stdout to file and see if i can update it. Nov 15 05:51:04 The reason I say this is this...I got a cheap DSM2 controller. I want to use to finally get this BBBlue of the damn ground. Nov 15 05:51:34 I started this sucka and it is not finished until the BBBlue flies! Nov 15 05:51:49 Sorry. Nov 15 05:58:32 Guest82: BeagleBone Black * anything * in google Nov 15 05:58:55 (and discard any results from before 2019 or so) Nov 15 05:59:27 for instance, * anything * can be networking, there is a forum.beagleboard.org, and the site beagleboard.org. It has some ideas. Nov 15 05:59:50 Yea. that cape_mgr and slots is not good any longer. Nov 15 06:01:13 and now, sysfs is trying to go away b/c people say it is more complicated than sysfs entries. I think it will be around but that is a bit different now w/ that gpiod and character devices in Linux. Nov 15 06:01:55 now, GPIO is like its own microcontroller. Nov 15 06:03:34 ??? Nov 15 06:03:44 Oh okay. Make sense Nov 15 06:03:45 sysfs gpio ain't going anywhere Nov 15 06:03:55 sysfs in general definitely ain't going anywhere Nov 15 06:04:25 https://pastebin.com/YfmMnQwM is a form of what may work if you use python3 instead of a lib. or you can find a lib. in Python3 for the BBB. Nov 15 06:04:28 Okay, okay. Nov 15 06:04:30 Sheesh. Nov 15 06:04:54 I found that years ago...and just found it again somehow. Nov 15 06:04:57 why are you showing an example that involves gpio, which is not relveant for Guest82 ? Nov 15 06:05:07 (and worse yet, an example for RPi rather than BBB) Nov 15 06:05:17 Well, he can kick out the Rpi stuff. Nov 15 06:05:25 I will I try to write a script to read from a sensor and definitely get back to you with questions. Nov 15 06:05:37 set_: nothing in that script is relevant except "import serial" Nov 15 06:05:42 and the GPIO is if he needs it I guess. Right! Nov 15 06:05:53 he doesn't since this is a usb device Nov 15 06:05:59 Oh. Nov 15 06:06:02 Right. Nov 15 06:06:07 No I/O. Nov 15 06:06:26 Argh. But... Serial = "/dev/ttyUSB0" can be used. Nov 15 06:08:00 Let me get the site so if he needs to direct the attention of the Rpi to the BBB, he can. This can be ported to the BBB easily and what can be erased is easy to see in his need. Nov 15 06:09:10 This guy has a neat site for porting to the BBB but it is in Rpi stuff. Use the Serial stuff and change it to suit Python3 needs: http://www.python-exemplary.com/index_en.php?inhalt_links=navigation_en.inc.php&inhalt_mitte=raspi/en/gsm.inc.php . Nov 15 06:09:20 ... Nov 15 06:09:36 You can port that to using Linux serial or Python serial and the BBB. Nov 15 06:10:54 some is relevant but you may be caught using some of it in specific instances. Nov 15 06:10:58 pyserial works the same on every linux system, it doesn't matter if you're using a BBB or an RPi or a desktop linux system Nov 15 06:11:12 it works exactly the same Nov 15 06:11:25 Right. I get that...but Linux has other serial libs, i.e. not just pyserial. Nov 15 06:11:34 same for any other serial lib Nov 15 06:12:06 Okay. Nov 15 06:12:20 using a usb serial device works exactly the same on any linux system Nov 15 06:12:24 Oh. Nov 15 06:12:28 Now I get you. Nov 15 06:12:36 Now, you are 100% right! Nov 15 06:14:01 so. in python3 w/ pyserial, using ser.Serial("/dev/ttyUSB0", baudrate=9600, timeout=1) is a good idea if necessary from whatever the docs. state? Nov 15 06:14:26 And then, you can use all of the ser. functions. Nov 15 06:14:28 the correct baudrate to use will depend on the device Nov 15 06:14:45 whether to use a timeout (and what timeout to use) depends on how you're writing your code Nov 15 06:15:05 Right. I barely understand time as it is now. That was just an example. Nov 15 06:15:33 Why would I need different timeout==(n) or whatever? Nov 15 06:15:49 sorry. timeout=(n) Nov 15 06:19:09 for a timeout of different times? Nov 15 11:57:24 hi Nov 15 15:39:41 remind me again to ssh into the beagle you do not need to do anything special on PC side? Nov 15 15:39:47 i just moved to debian 11 Nov 15 15:39:58 need to setup my connection again Nov 15 15:41:57 no, normally not Nov 15 15:43:26 do you think it is weird that the PC's network manager would not show a connection however I still have access to the internet Nov 15 15:44:14 what is throwing me off is on debian buster (really LMDE4) it gave me that ethernet icon and said I was connected to the beaglebone or internet, I could never connect to both at the same time Nov 15 15:45:49 how are you connecting the beaglebone? Nov 15 15:45:50 i have trouble shooting these things Nov 15 15:46:05 ethernet cable like before Nov 15 15:46:15 and how are you connecting to the internet? Nov 15 15:46:42 ethernet cable so I have a small powered router Nov 15 15:47:05 why a router? did a switch not work? Nov 15 15:47:12 so i have my modem cable into the router and one cable going to the PC and beaglbone Nov 15 15:47:41 I can see one device on the network manager and I can browse the internet as normal Nov 15 15:47:45 oh never mind I'm confusing your setup with someone else I think Nov 15 15:47:58 I cannot ping the beaglebone at all Nov 15 15:48:06 you're trying to ping beaglebone.local ? Nov 15 15:48:11 yes Nov 15 15:48:18 i get a time out Nov 15 15:48:44 and you didn't, like, change the beaglebone's hostname from "beaglebone" to something else? Nov 15 15:50:33 since you have a router, just plain "ping beaglebone" (or whatever the hostname of your beaglebone is) without ".local" should also work Nov 15 15:50:40 typically Nov 15 15:53:34 when you say hostname, this is a brand new install of an OS Nov 15 15:53:42 on the beaglebone? Nov 15 15:53:44 so I lost any setup i may have performed previously Nov 15 15:53:53 nothing was touched on the beaglebone Nov 15 15:53:56 just the PC Nov 15 15:53:58 I'm talking about the beaglebone Nov 15 15:54:18 yeah that has not changed Nov 15 15:54:18 no setup should be needed on the PC normally Nov 15 15:54:25 i can connect on my lap top Nov 15 15:54:35 just this PC after putting debian 11 on it Nov 15 15:55:00 did you do some minimal install that doesn't include libnss-mdns ? Nov 15 15:56:52 possibly I can check are there any other packages I would need. What is throwing me off is the internet works fine so it can communicate with stuff Nov 15 15:56:59 just not the beagle Nov 15 15:57:43 libnss-mdns is all that's needed for .local name resolution Nov 15 15:58:03 ok Nov 15 15:58:08 i will check that Nov 15 15:58:23 i also tried the 192.168.7.2 Nov 15 15:58:29 and it gave me a port 22 error Nov 15 15:58:42 debian@192.168.7.2 Nov 15 15:59:00 there's absolutely no reason for that to ever work except when the beaglebone is connected _via usb_ to the pc Nov 15 15:59:02 mattb0ne, 7.2 is only on usb... if your plugged into ethernet, it'll be what ever your dhcp gave it out.. Nov 15 15:59:20 i see Nov 15 15:59:43 (beaglebone.local should work regardless of how the beaglebone is connected) Nov 15 16:00:21 ps, another way to find it, if mnds doesn't work, install avahi-discover and then run that app on your x86 host.. Nov 15 16:03:38 ok I will try these out Nov 15 16:04:03 can a computer see the beagle on the ethernet cable like you can when it is connected usb Nov 15 16:06:39 all devices on a single ethernet network can see each other Nov 15 16:20:34 that network is formed right after you plug in or do you need to "create" the network Nov 15 16:21:57 the former Nov 15 16:22:49 an ethernet exists implicitly... if a computer has an ethernet port, it's on an ethernet network, albeit it might be the only device on that network (if nothing is plugged in) Nov 15 16:22:58 *an ethernet network Nov 15 16:24:16 got ya Nov 15 16:24:27 two devices can form a network by connecting directly, larger networks are formed using ethernet switches. the various LAN ports on a router are typically all on an internal ethernet switch Nov 15 16:24:47 an ethernet can also be extended to include wireless clients using a wifi access point Nov 15 21:16:51 zmatt: I should be able to ping the beaglebone even if I have not ssh'ed into it correct? Nov 15 21:17:01 i get 100% packet loss with mtr Nov 15 22:02:40 wait, so you can resolve beaglebone.local but you can't reach it? Nov 16 00:36:35 So, on classic BeagleBoard, I have a USB hub connected. Plugged mouse and keyboard into it. Power on the board, boots and finds the devices. Apparently hotplug is not supported, because unplugging/plugging either one of them does not work. Comments? I have a Rev C4 board. **** ENDING LOGGING AT Tue Nov 16 02:59:57 2021