**** BEGIN LOGGING AT Sat Jun 22 02:59:57 2019 Jun 22 23:54:05 https://imgur.com/a/CtcKd4W shows a photo of unidirectional/bidirectional level shifter for changing 3.3v to 5v. Jun 22 23:54:06 ... Jun 22 23:54:37 Anyway...I listed a question in that photo as a comment. Jun 22 23:55:06 I am basically asking if I need to use this level shifter as a motor driver type for programming purposes. Jun 22 23:55:59 I am using Encoder 4 on the BBBlue as a PRU out for messing w/ ArduCopter (still). Jun 22 23:57:27 I know about the common ground and I think I need more than two pins for this case. So, would I be using enable A or plain "A" on that pinout of the level shifter to or from the BBBlue? Jun 22 23:57:53 set seth Jun 22 23:58:16 you want to use a level shifter as a moter driver set_ ? Jun 22 23:58:21 I don't think that's recommended Jun 22 23:58:27 I'd use a level shifter for logic signals Jun 22 23:58:31 Yes. Jun 22 23:58:34 not for something beefy like a motor Jun 22 23:58:37 you need a motor controller Jun 22 23:58:37 Oh no. Jun 22 23:58:54 but if it can put out enough current then I guess you can use it Jun 22 23:59:00 No. I need to get pru to Sbus for transferring data. Jun 22 23:59:02 I think. Jun 22 23:59:05 with appropriate protections like clamp diodes Jun 22 23:59:18 Logic Signal...yes. Jun 22 23:59:33 so it doesn't go out power a motor directly Jun 22 23:59:38 No. Jun 22 23:59:40 Right. Jun 22 23:59:51 It will not power a motor directly. Jun 23 00:00:13 good Jun 23 00:00:32 See. The Sbus is 5v on my rx while the BBBlue gives out the 3.3v signal. Jun 23 00:00:48 what do you call sbus ? Jun 23 00:00:51 I think this has been my issue all along and not my wiring. Jun 23 00:01:26 Oh. Sbus is an inverted UART from some co. that was made and copied w/ the current co. that made my rx. Jun 23 00:01:44 I have a FrSky rx. if that matters. Jun 23 00:02:19 you tie Vcc to 3.3V, Vdd to 5V, you tie enable A to Vcc, you use A as your 3.3V input, and E is your 5V output Jun 23 00:02:33 Dang. Jun 23 00:03:05 mawk: Any experience in this stuff...sheesh. That was awful quick. Thank you. Jun 23 00:03:21 I did not want to make a conclusion w/out asking around. Jun 23 00:03:30 I just looked at the datasheet Jun 23 00:03:33 http://www.ti.com/lit/ds/symlink/cd40109b.pdf Jun 23 00:03:58 Yea. http://www.ti.com/lit/ds/symlink/cd40109b.pdf. That is the link. Jun 23 00:04:29 I was reading it over. I saw the beginning where it stated the content of the flow. Jun 23 00:05:36 See. I think there may be an issue. Jun 23 00:06:04 So, is this as a bidirectional input/output? Jun 23 00:06:21 A is your input, E is your output Jun 23 00:06:27 it can't be used in reverse I fear Jun 23 00:06:33 Okay. Jun 23 00:07:26 I was asking b/c I am very unfamiliar w/ PRU stuff. The PRU I have gathered is an input and not an output. But, w/ the BBBlue, PRU pin 15 on encoder 4, pin 4, is an output. Jun 23 00:07:27 ... Jun 23 00:07:31 This is what I thought. Jun 23 00:07:54 this sounds an unrelated problem Jun 23 00:08:05 Right. But on this idea... Jun 23 00:08:06 as long as you connect outputs to inputs nothing can really go wrong Jun 23 00:08:36 The PRU Pin 15 on the BBBlue is supposed to drive data. At least, this is what i thought. Jun 23 00:09:40 I am basically adding this device, the one you described to me after reading the data sheet, to that encoder pin 4 on the BBBlue to change the supply logic. Jun 23 00:11:04 But...is the PRU logic 3.3v? Jun 23 00:11:13 I think, yes Jun 23 00:11:18 Okay. Jun 23 00:15:16 Hey mawk: I am going to try what you described to the best of my knowledge. I am basically, from what i thought, turning on the PRU at boot to transfer data to the Rx and not vice versa but I think I have been incorrect this entire time. Jun 23 00:16:50 Anyway...thank you again. I will test soon on this idea. **** ENDING LOGGING AT Sun Jun 23 02:59:57 2019