**** BEGIN LOGGING AT Tue May 11 02:59:57 2021
May 11 03:32:38 <ds2> pdp7: adapter board? for?
May 11 03:33:12 <ds2> pdp7: is the chip self thermal protecting?
May 11 03:37:33 <renrelkha> antenna are hard to install sometimes...
May 11 04:00:58 <pdp7> ds2: it is an adapter PCB that makes it possible to access all the IO with that heatsink installed.
May 11 06:08:50 <RajMehta[m]> <zmatt "Raj Mehta: is that a question?  "> I want to use beaglebone black with multiple 4-> ir sensors, 1-> Gyroscope sensor, 2-> Relay. so ir and gyroscope data are continued recive by beaglebone through GPIO pins. 
May 11 06:10:25 <RajMehta[m]> so beaglebone can handle all multiple data at time with accuracy ?
May 11 09:35:20 <zmatt> RajMehta[m]: I mean, using gpio mode is generally kind of a last resort thing since it requires everything to be handled by software.  what kind of protocol are these signals using?   if there's really no on-chip peripheral suitable for receiving these signals, the best option is probably to use PRU which is capable of receiving custom protocols (people have even implemented a 12-channel 100 Msps ...
May 11 09:35:25 <zmatt> ...logic analyzer using PRU)
May 11 09:36:00 <zmatt> (PRU is a subsystem on the AM335x SoC of the beaglebone)
May 11 10:07:21 <RajMehta[m]> i use I2C, Serial, and 24 GPIO pins
May 11 10:12:32 <zmatt> so, with gpio the limiting factor is software, especially linux.  linux userspace software will have a hard time monitoring gpios with any sort of accuracy because of the overhead involved and because linux will interrupt your software frequently
May 11 10:12:56 <zmatt> that's why PRU is useful, it's a subsystem with two dedicated cores that have GPIO wired directly into registers
May 11 10:36:28 <zmatt> (and are fully available for custom software, nothing else is running on them, nothing will interrupt them)
May 11 11:12:51 <RajMehta[m]> <zmatt "so, with gpio the limiting facto"> Thank you @zmatt your answer is useful for me.
May 11 12:13:46 <kremlin> m
May 11 22:52:28 <mattb0000ne> does anyone have recomendations on a reliable step down converter
May 11 22:52:50 <mattb0000ne> i got some amazon thing and it does not step down the voltage thank god I checked
May 11 22:52:55 <mattb0000ne> pos
May 11 23:00:16 <zmatt> what amazon thing, and what did you measure?
May 11 23:00:31 <mattb0000ne> output voltage
May 11 23:00:37 <mattb0000ne> switching to this
May 11 23:00:39 <mattb0000ne> https://www.digikey.com/en/products/detail/texas-instruments/LV14360PEVM/13283337
May 11 23:01:12 <mattb0000ne> https://www.amazon.com/Converter-Regulator-Adapter-Reducer-Electronics/dp/B07Q5W1BG3
May 11 23:01:15 <mattb0000ne> what I have
May 11 23:01:19 <mattb0000ne> doesnt work
May 11 23:01:33 <zmatt> "output voltage" yeah duh I meant what was the result
May 11 23:02:13 <mattb0000ne> higher like 12V
May 11 23:02:18 <mattb0000ne> not the 5V
May 11 23:02:38 <mattb0000ne> have 24V DC going in
May 11 23:03:56 <zmatt> try connecting a large resistor across its output, like 100k or something
May 11 23:04:22 <mattb0000ne> ok
May 11 23:04:54 <zmatt> it's definitely possible for a switching power supply to have trouble with being completely unloaded
May 11 23:05:11 <mattb0000ne> ok one second
May 11 23:06:04 <zmatt> like, the reviews seem to imply it works fine for most people (y'know, ignoring that one guy which had one explode)
May 11 23:06:07 <mattb0000ne> ok now 5.1
May 11 23:06:20 <zmatt> yeah that's what I thought
May 11 23:06:30 <mattb0000ne> that should be ok to go into the beagle right 5V/5A
May 11 23:07:39 <zmatt> 5.1 is within spec, that's only 2% above nominal
May 11 23:08:00 <zmatt> usb specified 5V ±5%
May 11 23:08:03 <zmatt> *specifies
May 11 23:09:14 <zmatt> it might be worth keeping that resistor in parallel to the beaglebone just to be safe
May 11 23:09:57 <mattb0000ne> i will
May 11 23:10:22 <mattb0000ne> and I dont need to change any settings just plug into VDD5V and GND
May 11 23:11:44 <zmatt> yeah, P9.05/06 connects directly to the center pin of the 5V barrel connector
May 11 23:13:01 <mattb0000ne> phew in business
May 11 23:13:29 <zmatt> it's recommended to connect both P9.05 and P9.06 to the positive output lead of your supply and connect both P9.01 and P9.02 to the negative output lead of the supply
May 11 23:13:41 <mattb0000ne> ok
May 11 23:14:18 <zmatt> using one pin for each will probably work fine in practice, but technically the headers are only rated for 1A per pin and the BBB can draw more than that
May 12 00:17:13 <mattb0000ne> zmatt: what is the different between connecting both USB and ethernet cord vs just ethernet cord when communicating with theh the BBB
May 12 00:17:30 <mattb0000ne> I am able to send commands with TCP if I have both the USB and ethernet cable plugged in
May 12 00:17:49 <mattb0000ne> but I get nothing if I just have the ethernet cable plugged in
May 12 00:18:02 <mattb0000ne> is that a port issue I am using 7777
May 12 00:18:19 <mattb0000ne> is there a way to force to the ethernet cord not sure how that works
May 12 00:18:51 <zmatt> whether usb is connected or not has no impact on networking via ethernet
May 12 00:19:45 <set_> GenTooMan: I got 'em working!
May 12 00:20:18 <zmatt> so you're probably just trying to connect explicitly via the usb interface (e.g. by connecting to 192.168.7.2, which is the beaglebone's IP on the usb0 interface)
May 12 00:20:38 <set_> GenTooMan: The motor(s). They are turning!
May 12 00:21:03 <set_> Slowly so far but the BBB will be attached soon to test things. Vroom!
May 12 00:21:50 <set_> and do not fret, I will get a power off button and limit switch just like rules state.
May 12 00:29:27 <mattb0000ne> what would be the ethernet interface address
May 12 00:30:03 <mattb0000ne> set you are still trying to fly
May 12 00:30:04 <mattb0000ne> ?
May 12 00:30:06 <mattb0000ne> pics
May 12 00:30:10 <mattb0000ne> updated pics
May 12 00:31:15 <set_> Oh...
May 12 00:31:22 <set_> No...I am not trying to fly right now.
May 12 00:31:49 <set_> I know that works. I am using some automation type motors for handling a CNC or other machine. I am not sure exactly what as of now.
May 12 00:32:29 <set_> Software Controlled, integrated motors...nice!
May 12 00:32:46 <set_> I feel so rich using this motor. I think I can fool myself.
May 12 00:32:47 <set_> Ha.
May 12 00:33:26 <set_> One dang incorrect wiring connection and I was thinking nothing worked. It works!
May 12 00:53:48 <mattb0000ne> zmatt: how would I get the address for the BBB's ethernet
May 12 01:03:16 <zmatt> mattb0000ne: usually you can just connect by hostname (either "beaglebone.local" or just "beaglebone") instead of having to worry about IP addresses
May 12 01:04:11 <zmatt> the IP address on ethernet is acquired automatically and assigned by your local dhcp server (typically your internet modem/router)
May 12 01:04:40 <zmatt> so it cannot be assumed to be fixed unless you specifically configure your dhcp server to always give your beaglebone the same IP address
May 12 01:04:48 <mattb0000ne> hmmmm
May 12 01:04:58 <zmatt> but I wouldn't recommend connecting by IP address in the first place
May 12 01:04:59 <mattb0000ne> so python wont understand that right
May 12 01:05:03 <zmatt> ?
May 12 01:05:16 <mattb0000ne> well this is via my little program
May 12 01:05:26 <mattb0000ne> so I open a connection in my code
May 12 01:05:45 <mattb0000ne> and I explicitly set the ip since that is how all the example codes do it
May 12 01:06:09 <zmatt> what module are you using to connect?
May 12 01:06:35 <zmatt> like, typically you can pass a hostname instead of an IP just fine
May 12 01:07:32 <mattb0000ne> it is the asyncio module
May 12 01:07:40 <mattb0000ne> i think they use selectors
May 12 01:07:44 <mattb0000ne> module underneath
May 12 01:07:53 <mattb0000ne> await asyncio.open_connection('192.168.7.2', 7777,loop=loop)
May 12 01:08:01 <mattb0000ne> is my call to establish the conneciton
May 12 01:13:40 <zmatt> you can just pass a hostname instead of ip address
May 12 01:14:53 <mattb0000ne> ok
May 12 01:17:39 <zmatt> e.g. https://pastebin.com/R85bPcWv
May 12 01:19:54 <mattb0000ne> would the beagle bone itself know beaglebone.local?
May 12 01:20:07 <zmatt> definitely
May 12 01:20:10 <mattb0000ne> ok
May 12 01:23:50 <mattb0000ne> so when I have them both use beaglebone.local I get 192.168.6.2 on the beaglebone and 10.42.0.46 on my laptop
May 12 01:24:10 <mattb0000ne> should I do a reboot and see if they will match
May 12 01:24:24 <mattb0000ne> maybe because I already started them they will keep going to the same address
May 12 01:24:55 <zmatt> beaglebone.local will yield *some* address of the beaglebone that is reachable from the computer where you do the lookup
May 12 01:25:03 <zmatt> so there's no reason to expect consistent results
May 12 01:25:51 <zmatt> if your laptop is connected to the beaglebone via usb it too much yield 192.168.6.2 or 192.168.7.2
May 12 01:25:57 <zmatt> *might yield
May 12 01:26:33 <zmatt> it doesn't matter, don't even look at the IP addresses, the whole point of using beaglebone.local is not having to worry about them
May 12 01:36:03 <mattb0000ne> ok let me restart
May 12 01:36:15 <zmatt> why are you restarting?
May 12 01:37:05 <mattb0000ne> misread what you wrote.
May 12 01:37:14 <mattb0000ne> i am getting connection refused error
May 12 01:37:27 <mattb0000ne> so i guess it is reaching but getting shot down
May 12 01:38:05 <mattb0000ne> ConnectionRefusedError: [Errno 111] Connect call failed ('10.42.0.46', 7777)
May 12 01:39:14 <zmatt> make sure your server is listening on "any ip", e.g. asyncio.start_server( handle_client, port=7777 )
May 12 01:39:39 <zmatt> or asyncio.start_server( handle_client, None, 7777 )
May 12 01:39:49 <zmatt> (replace handle_client by whatever your protocol handler is)
May 12 01:40:07 <zmatt> if you listen on '127.0.0.1' then the beaglebone will not accept any connections other than from itself
May 12 01:40:07 <mattb0000ne> ok
May 12 01:46:33 <mattb0000ne> that worked
May 12 01:58:36 <mattb0000ne> a mosfet failure is a permanent failure of the board
May 12 01:58:41 <mattb0000ne> or can you reset a mosfet
May 12 01:58:49 <zmatt> I have no idea what your words mean
May 12 01:58:57 <zmatt> what board?
May 12 01:59:03 <mattb0000ne> ERR LED Indicator - Error LED Indicator, it will illuminate when fault detected in on board MOSFET driver.
May 12 01:59:04 <zmatt> what mosfet?  failed how?
May 12 01:59:08 <mattb0000ne> https://docs.google.com/document/d/1icu1GVDxZhUn3ADSUc3JknNcmUMdPcsnJ4MhxOPRo-I/view
May 12 02:00:32 <zmatt> if the documentation doesn't specify what it means then I have no way of knowing either
May 12 02:00:36 <mattb0000ne> I am not sure why it failed
May 12 02:00:43 <mattb0000ne> that is all they give in the manaul
May 12 02:00:46 <mattb0000ne> that sucks
May 12 02:01:11 <mattb0000ne>  ok I am done with cheap amazon parts
May 12 02:01:16 <mattb0000ne> no more
May 12 02:03:47 <mattb0000ne> does this mean anything to you 'Support TTL PWM from microcontroller, not PWM from RC receiver'
May 12 02:04:03 <mattb0000ne> would a pin be TTL
May 12 02:04:19 <zmatt> yeah, rc receivers use a weird timing that doesn't resemble normal pwm
May 12 02:04:48 <zmatt> like, it indicates magnitude by absolute pulse width (regardless of frequency) rather than duty-cycle
May 12 02:05:04 <zmatt> so they're just saying it doesn't support that
May 12 02:05:42 <zmatt> which makes sense since it's just a motor driver
May 12 02:06:06 <zmatt> (rc servo format isn't directly usable for driving a motor)
May 12 02:23:48 <set_> Hello...yep. No more amazon parts w/out datasheets.
May 12 02:24:01 <set_> I learned this valuable lesson, too.
May 12 02:24:54 <set_> But...inexpensive parts, yes. No way to know how they actually operate, yes. Knowin' the expense of operation / inexpensive, priceless.
May 12 02:25:05 <mattb0000ne> or whats wrong
May 12 02:25:16 <mattb0000ne> they leave you this cryptic message about a mosfet
May 12 02:25:26 <mattb0000ne> this is my 4th motor driver
May 12 02:25:31 <set_> Aw!
May 12 02:25:40 <mattb0000ne> they have been 10 bucks each
May 12 02:25:59 <mattb0000ne> I am doing the final wiring and I do not want to have to mess with this once I close the enclosure
May 12 02:26:04 <mattb0000ne> argggg
May 12 02:26:09 <set_> I know the people at DR Robots give the datasheets for specific types of drivers.
May 12 02:26:23 <set_> Anyway...no more amazon. You are going to drive yourself loopy.
May 12 02:27:41 <set_> Now, if you build drivers and have datasheets, you can make a nice set of change on amazon. Factoids!
May 12 02:28:50 <set_> But...for purchasing? No. There is no way to tell whether or not you are dealing w/ a known datasheet on the product or not.
May 12 02:29:31 <set_> Hey mattb000be: What are you building?
May 12 02:29:35 <zmatt> mattb0000ne: I don't have any significant experience with motors, but one concern that would be on my mind is back-EMF when braking... that energy needs to go somewhere, and unless the driver has the means to brake resistively (i.e. dump the energy into a big heat sink) it'll brake regeneratively, i.e. the power is returned to the battery / power supply.  not all power supplies will appreciate that
May 12 02:30:06 <mattb0000ne> hmmm
May 12 02:30:26 <mattb0000ne> mosfet is a switch right ?
May 12 02:30:34 <mattb0000ne> maybe the back emf messes that up
May 12 02:30:37 <mattb0000ne> i think you are on to something
May 12 02:30:41 <zmatt> if the supply is incapable of receiving that returned energy the supply voltage will probably shoot up like a rocket, which could subsequently damage the MOSFETs
May 12 02:30:42 <set_> Dump that energy!
May 12 02:31:05 <zmatt> (and/or the power supply)
May 12 02:31:42 <set_> He is right, mattb0000ne. I have been reading recently (oops) and everything he just stated is an effect to motors moving.
May 12 02:32:22 <set_> regenerative braking will ruin some nice parts if not ruin them totally/for good.
May 12 02:33:20 <set_> I found some TI wiki pages in the form of .pdf. They have ideas on building drivers, what to place and where, and etc.
May 12 02:34:57 <set_> SLVA959A via '18 from TI.com.
May 12 02:36:41 <set_> "just an idea..."
May 12 02:42:15 <set_> I am not sure how big of rush this project is needing to be done but I saw the open source Amazon IPC3 && IPC5 from this co. has open source designs.
May 12 02:42:31 <set_> I can grab a couple real quickly.
May 12 02:43:07 <mattb0000ne> i am looking a polulu
May 12 02:43:17 <mattb0000ne>  but i want to  ask an EE about this back EMF
May 12 02:43:23 <mattb0000ne> and if there is a simpler solution
May 12 02:43:58 <mattb0000ne> brb
May 12 02:51:36 <set_> No issue.
May 12 02:51:39 <set_> Have fun!
**** ENDING LOGGING AT Wed May 12 02:59:56 2021