**** BEGIN LOGGING AT Mon Apr 20 02:59:57 2020 Apr 20 03:04:58 hello Apr 20 03:05:04 I think? Apr 20 03:05:17 set_ is not in the building. Apr 20 03:14:29 GenTooMan: Looks to be from where I sit. Just inactive. Apr 20 03:16:21 zmatt: From what little further digging I've done in the past couple days, it looks like you are (not surprisingly) correct, most of the PRU pins overlap with the LCD pins used by the HDMI chip. Apr 20 03:16:47 Again, not really surprising, just happened to run across it independently this evening. Apr 20 04:39:25 IanWizard: I actually told you that Apr 20 04:43:11 at least I think I did Apr 20 04:43:13 That's why I highlighted you when saying "you're (not surprisingly) correct" Apr 20 04:43:32 I didn't doubt you, I just happened to see it independently Apr 20 04:47:03 :) Apr 20 10:54:19 hello i'am havin a problem using remoteproc for pru Apr 20 10:54:33 when i acces /sys/class/remoteproc/ Apr 20 10:54:53 i only get remoteproc0 there is no rproc1/2 Apr 20 10:55:05 can anyone help me how to fix this Apr 20 10:56:59 amine63: what firmware image are you running? Apr 20 10:57:33 wheni run sudo /opt/scripts/tools/version.sh Apr 20 10:57:38 i gethis Apr 20 10:57:50 (don't paste multiline output into chat Apr 20 10:58:00 use a paste service like pastebin.com ) Apr 20 10:58:42 ok then how to know the firmware Apr 20 10:58:46 in general, pru can be used either using remoteproc-pru or uio-pruss. the former has been the default for quite a while, though you can switch between the two at any time Apr 20 10:59:10 version.sh is fine, just don't try to paste its output into chat Apr 20 10:59:11 git:/opt/scripts/:[b61125c1485bee929340cacc06c85c6fcfd678bc] Apr 20 10:59:12 Overlay:[univ-bbb-xxx-00A0] Apr 20 10:59:47 like I just said, use a paste service like pastebin.com to share multiple text snippets Apr 20 11:00:22 if your beaglebone has internet access you can also have it generate a paste snippet using the pastebinit utility (e.g. "sudo /opt/scripts/tools/version.sh | pastebinit") Apr 20 11:01:05 otherwise just copy-paste the output into the big form at pastebin.com, click the Create New Paste button at the bottom, and give us the url of the resulting page Apr 20 11:05:28 https://pastebin.com/7PHY68sK Apr 20 11:07:06 your firmware image is somewhat old (2018-01-28), though remoteproc-pru was nevertheless the default back then. however, it is not enabled because you changed it to use uio-pruss instead Apr 20 11:09:05 for some reason there are two pru overlays enabled in your /boot/uEnv.txt: AM335X-PRU-RPROC-4-4-TI-00A0.dtbo (which is for remoteproc-pru, however that overlay is for the wrong kernel version: it's for kernel 4.4 but you're using kernel 4.9) and AM335X-PRU-UIO-00A0.dtbo (for uio-pruss, any kernel version). The latter setting is used, hence you have uio-pruss enabled currently and not remoteproc-pru Apr 20 11:09:28 hence no remoteproc devices for pru Apr 20 11:12:27 uncommenting just the line for AM335X-PRU-RPROC-4-9-TI-00A0.dtbo and commenting out the other two uboot_overlay_pru lines should fix the problem. however, if you're not already heavily invested in this system (i.e. don't have a lot of important data / customizations) you may also want to consider getting the latest image (2020-04-06), which is a new debian release (buster) and includes kernel 4.19 Apr 20 12:18:59 does anyone have a current part number for BBB cape connectors? I need the stacking type (Major League SSHQ-123-D-06-G-LF) Apr 20 12:19:09 nobody seems to stock Major League Apr 20 12:21:30 there must be something from Samtec, but I can't seem to find it Apr 20 13:10:58 jkridner: any pointers? Apr 20 13:11:35 mouser stocks a header kit for the BBB, but it's not the stacking type connector, just the pin headers Apr 20 13:15:21 oh, they also stock the stacking type! from Adafruit Apr 20 13:15:34 hm, not exactly cheap... Apr 20 13:16:51 thinkfat_ at least you can get it Apr 20 13:17:45 yes, but I might need a couple of them, not just one kit.... Apr 20 13:27:38 hello peoples Apr 20 13:27:50 does a TTL connection require a Tx and Rx Apr 20 13:28:19 the beagle is nice because it give you strip that matches up and you just plug right in Apr 20 13:28:39 MattB0ne: there is no such thing as a "TTL connection", I'm guessing you mean an uart connection Apr 20 13:28:48 the jrk motor controller doesnt appear to have enough pins to support a serial and a TTL cord Apr 20 13:29:10 if you put it that way support two UART connections Apr 20 13:29:23 ??? Apr 20 13:29:28 I have no idea what you mean by that Apr 20 13:29:54 so I am trying to setup the USB dual connection like you mentioned Apr 20 13:30:20 so I have TTL going to the computer and just Tx and Rx going to the beagle Apr 20 13:30:24 that's just a software setting, like I said it is a way to test your hardware setup (and in particular therefore is not a different hardware setup) Apr 20 13:31:31 it causes the serial port on the jrk (tx/rx) to be usable as a serial port on your computer, basically as if the jrk is a usb-to-serial converter Apr 20 13:31:41 so on the SW side of things I have pyserial sending stuff how do I get the other view Apr 20 13:31:51 i am not sure on wording how to I make it dual Apr 20 13:31:52 thus allowing your computer to communicate via the jrk to the beaglebone Apr 20 13:32:30 thus you can just open a terminal program on both sides (e.g. screen on the beaglebone) and confirm they can communicate (what you type in one should appear on the other) Apr 20 13:32:49 so basically nothing changes on the wiring though Apr 20 13:33:01 no since it's a way to test that your wiring is okay Apr 20 13:33:11 if you subsequently change the wiring, the test becomes invalid Apr 20 13:33:51 that way you can test purely the wiring without having to deal with the motor control protocol Apr 20 13:34:21 and once confirmed that works, you switch back the jrk back to normal uart mode Apr 20 13:35:13 it was just a suggestion to perhaps make it easier to figure out what's going on, since there'd be less unknowns to diagnose Apr 20 13:35:24 ok Apr 20 13:35:36 I am going to do that since I am having that read issue Apr 20 13:36:17 so I have two terminals open Apr 20 13:36:37 on one I ssh in and launch screen on my UART so /dev/ttyS4 Apr 20 13:37:42 on the other you open the second COM port exposed by the jrk (which they call the "TTL Port") Apr 20 13:38:17 see also page 17 of https://www.pololu.com/docs/pdf/0J38/jrk_motor_controller.pdf Apr 20 13:38:51 that screenshot shows how the jrk shows up as two COM ports, one of which is named "TTL Port" in the device manager Apr 20 13:38:56 that's the one Apr 20 13:39:15 so I need windows for this test Apr 20 13:39:21 oh I thought you were using windows Apr 20 13:39:26 i can Apr 20 13:39:29 if need be Apr 20 13:39:35 I mean no, same goes for any OS Apr 20 13:39:44 I just pointed to that screenshot because I thought you already were Apr 20 13:39:55 how do I reference that com port via linux Apr 20 13:40:18 I can plug in my TTL cord onto the beagle Apr 20 13:40:22 it'll show up as two serial ports there too. maybe check the kernel log Apr 20 13:40:26 your what? Apr 20 13:40:51 again, do not mess with the hardware connections since that would make the entire test pointless Apr 20 13:40:51 right whenever I plug in I get two entries for the beaglebone Apr 20 13:40:58 for the jrk Apr 20 13:41:00 I'm talking about the jrk Apr 20 13:41:09 that's why I pointed to the jrk documentation Apr 20 13:41:22 and said "shows how the jrk shows up as two COM ports" Apr 20 13:41:29 noticed yet I'm talking about the jrk? Apr 20 13:41:35 the jrk isn't the beaglebone Apr 20 13:41:38 :P Apr 20 13:41:59 make sense trouble shoot just the jrk first Apr 20 13:42:19 I have never connected the jrk to my linux machine without going through the beagle Apr 20 13:42:20 no this is about troubleshooting your hardware connections Apr 20 13:42:36 well then maybe don't start right now Apr 20 13:43:40 if you know it works on windows then connect it to windows Apr 20 13:44:14 ok Apr 20 13:44:32 so I can putty to the one com port Apr 20 13:44:39 to the TTL com port Apr 20 13:44:54 I feel good about that, I would need to ssh via a terminal in windows Apr 20 13:45:04 can I do this from a regular cmd prompt Apr 20 13:45:06 .. or use putty for that as well Apr 20 13:45:20 ok two putty sessions Apr 20 13:45:31 putty doesn't care about many sessions you open Apr 20 13:45:37 *how many Apr 20 13:45:59 have you configured the jrk to dual port mode? Apr 20 13:46:12 and normally when I was connecting to the jrk to my windows box via the micro usb port Apr 20 13:46:29 now I would also add the tx and rx connections via my TTL cord Apr 20 13:46:35 what? Apr 20 13:46:36 no Apr 20 13:46:43 NO Apr 20 13:46:53 that is how I see the TTL port in windows Apr 20 13:46:54 lol Apr 20 13:47:09 no, the ttl port shows up the moment you connect the jrk via usb Apr 20 13:47:16 that's what I already said many times Apr 20 13:47:22 and I linked to a screenshot showing that fact Apr 20 13:47:26 so that is all I need Apr 20 13:47:37 i figured I would want to test the Tx and Rx Apr 20 13:47:47 that's the whole point of this Apr 20 13:47:57 ok let me just do what you say Apr 20 13:48:06 i will turn off my brain for a bit Apr 20 13:48:49 jrk is connected to PC via usb, jrk uart (tx/rx) connected to beaglebone uart via level shifter Apr 20 13:49:28 the purpose of the test is to validate the uart connection between the jrk and the beaglebone Apr 20 13:50:51 i see i see Apr 20 13:50:52 configuring the jrk into dual port mode lets you do that, since it basically turns the jrk into a usb-serial adapter... you'll be able to open the jrk's uart interface as a COM port on your PC Apr 20 13:51:12 which is why it shows up named "TTL Port" Apr 20 13:51:25 and you think using screen is better than pyserial for sending commands Apr 20 13:51:33 well you won't be sending commands Apr 20 13:51:38 just typing Apr 20 13:51:44 ok Apr 20 13:51:48 it'll just connect two terminals together Apr 20 13:51:55 ok Apr 20 13:52:07 let me try that out and see how it goes Apr 20 13:52:25 i should just see what I type on the second screen otherwise no beuno Apr 20 13:52:28 got it Apr 20 13:52:28 be sure to select the same baudrate for both (when using screen you pass the baudrate as argument, e.g. "screen /dev/ttyS4 9600" Apr 20 13:52:32 ) Apr 20 13:52:51 ok mission received Apr 20 13:52:56 i am off brb Apr 20 13:53:03 if you're uncertain which COM port is the TTL Port, check windows device manager Apr 20 17:24:31 sorry it took so long Apr 20 17:24:42 the dual port thing worked Apr 20 17:24:56 if I type in screen I can see what I type in the TTL temrinal Apr 20 17:25:10 so that must mean the jrk is working and wiring is correct right? Apr 20 17:25:41 also what does the -ctrscts mean on screen Apr 20 17:25:47 I tried looking at the options on screen Apr 20 17:25:59 but could not unpack what flags were set Apr 20 17:26:18 also what should I try next Apr 20 18:33:26 so what now Apr 20 18:40:40 MattB0ne: since the serial communication link seems to work fine itself, yet (in normal uart mode) the motor controller's uart interface doesn't seem to behave as documented, I'd suggest contacting the manufacturer Apr 20 18:40:56 ok Apr 20 18:41:19 would me sending stuff via pyserial in the current setup be informative? Apr 20 18:42:43 MattB0ne: you could also test their C example(s) Apr 20 18:43:17 that might actually be a more useful first step Apr 20 18:44:01 MattB0ne: I mean, sure do a quick check with pyserial again if you're uncertain whether or not you messed with anything since it last misbehaved Apr 20 19:08:11 i tried their c code Apr 20 19:08:16 i get back garbage Apr 20 19:08:23 that is what started me on this journey Apr 20 19:09:18 then I'd really suggest you contact the manufacturer Apr 20 19:10:35 so just to clarify: when doing the dual port test, what you typed in one terminal appeared *only* in the other (and vice versa) ? Apr 20 19:40:37 right no echo Apr 20 19:40:47 though I could not type in the TTL terminal Apr 20 19:40:55 may of had a setting wrong or something Apr 20 19:42:24 uhh, if it's not working in both directions, it's not working. Apr 20 19:42:42 check the settings of your putty session, make sure hardware flow control isn't enabled Apr 20 19:45:00 speed (any standard speed up to 115200, use same value on both ends), 8 data bits, 1 stop bit, no parity, no flow control Apr 20 19:46:30 in fact the direction going *to* the beaglebone is the one you were having trouble with, so that's what you were supposed to be testing in particular Apr 20 19:46:36 you already knew beaglebone -> jrk was working Apr 20 19:57:10 let me try that Apr 20 20:14:13 huh. beaglebone-ai dts hasn't landed in linux yet. Apr 20 20:18:16 MattB0ne: just to be sure, this shows the connection scheme I'm assuming you're using (at the top), along with some examples of loopback tests you could do to further diagnose the issue if it's not working, with the second diagram being the most basic test that excludes the level shifter: https://photos.app.goo.gl/niqoqoqFzuHrMNvZA Apr 20 20:20:22 in all cases what you type should come out of jrk TX or BBB TxD (depending on what window you type in) and whatever is received on the jrk RX / BBB RxD should show up in the corresponding window. if you follow the arrows in each diagram you can see what should show up where Apr 20 20:20:35 in all cases the testing should be done in dual port mode obviously Apr 20 20:23:09 (it obviously shouldn't matter which channels you use of the level shifter, I just used 1 for jrk->bbb and 2 for bbb->jrk because it happens to line up nicely with the pins on the jrk) Apr 20 20:38:57 ok I set the serial to those settings, 8 bit, 9600 Baud rate no parity or flow control still cannot type Apr 20 20:39:20 do I need both terminals up first or I should be able to type regardless Apr 20 20:40:10 I mean, how would you know if it's working if you don't have both open, given that what you type in one window should appear in the other? Apr 20 20:43:12 i cannot do anything on the putty side Apr 20 20:43:23 that is an indicator that it is broken Apr 20 20:43:32 I don't know what you mean by "do anything" Apr 20 20:43:37 i remember you saying if you cannot type something wrong Apr 20 20:43:48 it will react to what I do in the other terminal Apr 20 20:43:56 by which I mean, if what you type doesn't show up in the other terminal then there's something wrong Apr 20 20:44:03 okay so one direction works, the other doesn't Apr 20 20:44:08 but I am unable to type or do anything in that Apr 20 20:44:27 if i were to press keys in the TTL window the cursor will not respond Apr 20 20:44:32 and even type in that windo Apr 20 20:44:40 window* let alone the other Apr 20 20:44:55 you're not supposed to see any reaction in the window you type in Apr 20 20:44:56 at all Apr 20 20:45:00 only in the other window Apr 20 20:45:56 ok well then both are borked Apr 20 20:46:07 if I type in the ssh window I see what I type in both windows Apr 20 20:46:23 in the TTL window nothing shows up on the other side Apr 20 20:46:26 that is equally wrong Apr 20 20:46:48 presumably if you disconnect the RxD line on the BBB that problem disappears? Apr 20 20:47:19 correct Apr 20 20:47:35 anyway, this is completely in line with the weird issue you were seeing with pyserial, so at least that part is consistent Apr 20 20:47:57 so not my wiring woohoo! Apr 20 20:47:59 so I suggest you start testing where it's coming from Apr 20 20:48:09 could it be my overlay? Apr 20 20:48:17 to figure out if it's coming from the jrk or the level shifter Apr 20 20:48:18 no Apr 20 20:48:51 it's either the jrk, the level shifter, or your connections (although I'm not sure how you could wire it wrong in a way that would cause this) Apr 20 20:49:19 i would need to wait for that new level shifter to come in Apr 20 20:49:28 I only have this one on hand at the moment Apr 20 20:49:40 ? Apr 20 20:49:52 and I cannot bypass the level shifter because of the 5V logic from the jrk right Apr 20 20:50:16 no but you can easily test whether the jrk or the level shifter is causing the echoing Apr 20 20:50:18 to swap the level shifter I am assuming is the next step Apr 20 20:50:33 how Apr 20 20:50:35 there's no need to swap out the level shifter unless you've determined it to be the cause Apr 20 20:50:52 which, while possible, doesn't seem very likely to me Apr 20 20:51:46 do I take jrk out of the circuit and loop it back Apr 20 20:51:47 ? Apr 20 20:52:00 if the level shifter is doing it then the problem would persist if you disconnect TX on the jrk side Apr 20 20:52:24 right but that fixes it Apr 20 20:52:32 so it has to be something with the jrk Apr 20 20:53:18 can you test the last diagram in my photo? Apr 20 20:53:24 ok Apr 20 20:53:43 can you repost Apr 20 20:53:46 pleace? Apr 20 20:53:48 please? Apr 20 20:53:54 on the windows comp may of missed it Apr 20 20:54:03 since I was dragging the laptop around Apr 20 20:54:36 (i.e. the wire you disconnected from the jrk TX, connect it to the same pin of the level shifter as the one jrk RX connects to, or just connect it to jrk RX itself) Apr 20 20:54:39 https://photos.app.goo.gl/niqoqoqFzuHrMNvZA Apr 20 20:55:16 so anything you type in the BBB goes through the level shifter to the jrk and also back through the level shifter to bbb rxd Apr 20 20:55:42 so in that config you expect anything you type on the BBB side to show up in both windows Apr 20 20:58:46 just to confirm again, it's configured in "USB Dual Port" mode yes? Apr 20 21:00:00 (since you do not seem to have any sort of mental model of what it is you're testing I feel the need to keep confirming obvious things) Apr 20 21:14:31 yes Apr 20 21:14:47 i appreciate the support Apr 20 22:05:38 how do I do that junction with jumper cables Apr 20 22:06:28 MattB0ne: if necessary you could omit the connection to jrk RX (i.e. just make it a loopback test from bbb via level shifter back via level shifter back to bbb) Apr 20 22:06:41 then you don't have any junction Apr 20 22:07:56 i did the looop back Apr 20 22:08:06 so it fixes ssh-> TTL Apr 20 22:08:11 ?? Apr 20 22:08:33 what I just said would leave no connections to the jrk, hence the TTL Port terminal would not be involved Apr 20 22:08:36 it does not have the echo in the SSH terminal when typing in the ssh terminal Apr 20 22:09:23 ok i was just checking both terminals so once it is wired what am I checking Apr 20 22:09:55 nm Apr 20 22:09:58 so if I loop back Apr 20 22:10:00 how were you checking with both terminals if you had no way to make a junction, which I assume you didn't because you asked how to Apr 20 22:10:06 I see what I type in the ssh Apr 20 22:10:10 which is expected Apr 20 22:10:29 nothing in the TTL as you said the jrk is discconected completely Apr 20 22:10:37 yes and since the data goes via the level shifter in both directions, you know the level shifter is working fine Apr 20 22:10:55 ok so my jrk is messsed up Apr 20 22:11:44 it would seem so Apr 20 22:12:18 dang Apr 20 22:12:37 well it is good that i tested everything else so I can complain Apr 20 22:12:46 but maybe we're just overlooking something, so just contact the manufacturer Apr 20 22:12:52 ok Apr 20 22:13:20 well thanks for the trouble shooting assist Apr 20 22:13:51 granted i am newb but it seems like this think could have been improved from a design persepctive Apr 20 22:14:12 the symptoms seem to be: the uart inexplicably echoing data received on RX back to TX (both in UART mode and in USB Dual Port mode), and in USB Dual Port mode, data written to the "TTL Port" isn't transmitted from the TX pin Apr 20 22:41:00 One note about those Pololu controllers: Plug in the USB to a power supply to the JRK when testing via micro USB to power supply. Apr 20 22:43:46 Scratch that idea. Sorry. I mean... Apr 20 22:44:19 Plug in the Micro USB to a USB hub that is powered via battery or by way of wall adapter. Apr 20 22:44:51 Have you two tried this effect? Apr 20 22:48:51 So, even though you are powering the motor driver onboard the JRK w/ a battery, you still need to have the usb comm. to work via the Micro USB on the JRK to a powered USB hub. Apr 20 23:10:48 set_: you are saying the laptop is not sufficent Apr 20 23:10:54 or computer Apr 20 23:11:12 either way I think I was covered. I had a 12V PSU and the usb cable Apr 20 23:29:43 And if all else fails you have your car battery. :D Apr 20 23:33:05 If you are using the BBB to test things and need to communicate from the BBB to your JRK and get feedback, you may want to make a makeshift circuit via: JRK Micro USB to Powered USB Hub && situate the BBB w/ its own power supply and have all tied in to the powered USB Hub. Apr 20 23:33:05 ... Apr 20 23:33:12 That is all I was trying to convey. Apr 20 23:35:23 set_: why? Apr 20 23:35:27 he had a proper setup Apr 20 23:36:15 his jrk requires a proper 6-16V supply anyhow, usb is not used to power it Apr 20 23:38:33 Okay. I was just wondering if that may be the cause. I did not have the details on how things were set up. Apr 20 23:39:36 @zmatt: It requires 6 to 16v of supply. Right but that supply is from the screw terminals and not the the extra power from the Micro USB. Apr 20 23:40:56 set_: ?? Apr 20 23:41:08 I see no reason to think it draws any power from usb at all Apr 20 23:41:59 in fact, it explicitly says its 5V supply used to power the logic derives (via an LDO) from VIN (the 6-16V input) Apr 20 23:42:08 usb is just for data Apr 20 23:44:40 Okay. Apr 20 23:45:46 So, the Micro USB from the JRK is attached to the BBB's USB port and the BBB is attached via barrel jack? Apr 20 23:46:14 set_: no. please stop trying to help. Apr 20 23:46:19 Fine. Apr 20 23:46:34 I don't have the energy to try to explain his problem to you after having already spent a lot of time trying to diagnose it Apr 20 23:46:43 Okay. no issue. Apr 21 00:46:26 set_ before you assemble the circuit for communicating with your AX12 servos come up with a plan :D Apr 21 00:46:34 Okay. Apr 21 00:46:45 Fine. A plan A and a plan B, too! Apr 21 00:47:40 Well try writting something down at the very least. That will start you thinking before doing. Apr 21 00:47:50 GenTooMan: I plan on checking the voltage on each end after the circuit is made. Apr 21 00:47:53 Oh. Okay. Apr 21 00:48:24 Then, I planned on working from that point forward. Apr 21 00:51:11 The faltering in my plan is this ---> The schematic has a DIRECTION_PORT label on it. I do not know what this exactly entails. Apr 21 00:51:13 have you built many digital circuits? Apr 21 00:51:28 Enough where...well. No. Apr 21 00:51:37 I have made some but not many. Apr 21 00:53:14 The schematic sucks. I know I cannot build anything from this schematic, i.e. esp. from three chips. Apr 21 00:53:47 But, I can try! Apr 21 00:55:49 right.. you only need 2 chips ... by the way. Apr 21 00:56:49 Two? Apr 21 00:57:07 I see the HC126 labeled twice and the HC04 labeled once. Apr 21 00:59:28 right but again their are 4 hc126 circuits and 6 HC04 circuits per IC Apr 21 01:00:00 that's why I told you to get the data sheets so you would see where power and all the circuits were. Apr 21 01:00:57 I have the datasheets. I have been reviewing them. Apr 21 01:02:42 Okay. It seems that the schematic from the link provided a couple of days ago and yesterday noted two "open parts" to the circuit. Apr 21 01:02:52 Did you see that section of the TTL schematic? Apr 21 01:03:11 It is from the Half Duplex UART schematic. Apr 21 01:03:30 Is that the diagram I pointed out to you? Apr 21 01:04:51 Yes. The same. Apr 21 01:05:10 I knew about it. You are not taking all the credit. Apr 21 01:05:12 you need 2 parts from a single HC126 and an inverter from the HC04 ... Apr 21 01:05:12 Ha. Apr 21 01:05:20 Okay. Apr 21 01:05:46 although you could get clever an using a single IC in total I didn't want you to get confused. Apr 21 01:06:05 Fine. Apr 21 01:06:29 I get hardwired confusion on my end. You already know. Apr 21 01:06:43 yes self induced at times. Apr 21 01:06:50 All self-induced! Apr 21 01:07:19 So, I get the pin out from this schematic. Apr 21 01:08:14 I do not get the "issues" from the different chips that I may encounter. So, me staying up to date on the datasheets will persist. Apr 21 01:08:23 ... Apr 21 01:09:14 From the HC126, it shows, twice on two separate chips, RXD and TXD going to nothing. What does this mean? Apr 21 01:09:29 Is that just the schematic symbol for the HC126? Apr 21 01:10:00 I looked on the datasheet, the HC126 has a separate type of symbol for it. Apr 21 01:11:04 Now, the HC04 symbology is on point from the datasheet to the schematic. Apr 21 01:14:24 Is it possible to read CPU temp. any more? Apr 21 01:17:10 AI, yes. Apr 21 01:18:37 kenunix depends on what the people broke in the software :D Apr 21 01:19:08 set_ those are 2 seperate HC126 circuits not 2 different IC's Apr 21 01:20:16 Oh. Apr 21 01:20:47 I see OE1 and OE2 can be used, then. Apr 21 01:20:47 that's what I told you before you confused yourself. :D Apr 21 01:21:22 So, I power them, GND them, OE1 w/ y/a and OE2 w/ y/a. Apr 21 01:21:40 Okay. Apr 21 01:25:07 Right that's why I suggested thinking it through first. Here is a motis operandi suggestion. Find out what you need (circuit diagram) then look at what you have and match the parts. Obviously you need 2 HC126 circuits (not parts) and an inverter (HC04) so a bit at a time. You need 5V power for the IC (unfortunately the AX12 is a 5V bus). Apr 21 01:25:13 KenUnix: I've not looked, but surely it's available in sysfs somewhere? Apr 21 01:26:29 blind duck phase on my part, okay. Apr 21 01:27:08 Okay. I found that I will need some caps, too. Apr 21 01:27:16 0.1 us. Apr 21 01:29:48 I will need some resistors, too. Okay. Apr 21 01:30:34 you mean 0.1uF you should have those like coming out your ears but I digress Apr 21 01:32:00 Sorry. Apr 21 01:32:02 Yes. Apr 21 01:32:15 I have some but I might have to search for them. Apr 21 01:32:50 It's supposed be in /sys/class/thermal but it's not there Apr 21 01:33:10 hmm Apr 21 01:33:45 GenTooMan: What is the DIRECTION_PORT? Is it the input or output of this circuit? It must be the input pin. Apr 21 01:34:08 B/c I see data out, VDD out and GND out. Apr 21 01:34:24 From what I read TI took it out of image Apr 21 01:34:58 So, the signal comes in via the "DIRECTION_PORT" and I make an additional 5v supply available where listed on the schematic. Apr 21 01:35:42 IanWizard - From what I read TI took it out of image Apr 21 01:36:06 their should be RX TX going into the HC126 and out of the HC126 ports. Apr 21 01:36:34 Right. That is within the circuit for the Half Duplex UART. Apr 21 01:37:59 But...on the schematic, there are three output pins (DATA, VDD, GND) and this DIRECTION_PORT idea. Apr 21 01:38:12 and a 5v input pin. Apr 21 01:38:33 Half Duplex? What does it echo back everything sent? Apr 21 01:39:32 Transmission... Apr 21 01:39:42 It can only have one master at a time. Apr 21 01:39:55 direction port controls the direction of the data going in and out from the RX and TX lines. You have 3 control signals 2 power connections and one half duplex port. Apr 21 01:39:55 No body uses half duplex anymore then use full duplex Apr 21 01:40:08 Nope. Apr 21 01:40:27 GenTooMan: Okay. Apr 21 01:41:00 So, that is basically what we are making. Either the it is being received or transmitted. Apr 21 01:41:08 when direction port is low it's transmitting when high it's receiving. Apr 21 01:41:14 Okay. Apr 21 01:41:24 one challenge at a time set :/ Apr 21 01:41:35 Okay. I know, I know. Apr 21 01:41:54 I wanted to make sure I understood the outer portions too. Apr 21 01:42:04 Not just the circuit. Apr 21 01:42:29 kenunix except clever Chinese lesson learned being clever doesn't mean you are being smart. Apr 21 01:42:53 I guess I was trying to figure out the philosophy of it all, i.e. the why instead of the how. Apr 21 01:45:55 This is the best way for you to learn. Do you have a 5V USB com device with "ttl" output? that would be the best for testing the servo from your PC Apr 21 01:46:16 Um. Apr 21 01:46:17 Hmm. Apr 21 01:46:24 USB to TTL converter? Apr 21 01:46:35 I think. Apr 21 01:46:40 I might have two. Apr 21 01:46:41 no USB com with ttl IO Apr 21 01:46:46 Oh. No. Apr 21 01:46:53 Dang. Apr 21 01:49:08 hmm that could be interesting :D Apr 21 01:49:19 What? Apr 21 01:49:25 What would be interesting? Apr 21 01:50:51 The same adapter you talk to the BBB on serial port? Apr 21 01:51:19 no and similar 5V instead of 3.3V Apr 21 01:51:46 slow down a bit so I can actually show you what I mean. Apr 21 01:52:13 %v volt usb -> serial with pins? Apr 21 01:53:29 Do you need handshaking RTS/ CTS or DCD? Apr 21 01:55:04 Okay. Apr 21 01:55:06 TTL-234X-5V > data sheet https://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf Apr 21 01:55:46 and likely you want to use the hand shaking to switch directions. It's not simple to control it but they have SW on their site for just that. Apr 21 01:56:02 Let me check. Apr 21 01:58:03 Yep. Apr 21 01:58:19 That's got a solid header. Don't you need the pin type? Apr 21 01:58:20 I got one of those and another one w/ only four pins. Apr 21 01:58:50 So, i have the six pin and the four pin. Apr 21 01:58:58 set_ yes but is it 5v? Apr 21 01:59:06 No. Apr 21 01:59:09 3.3v. Apr 21 01:59:32 right that's why I specified 5V. their is no level shifter that's in a dip package available Apr 21 02:00:06