#linuxcnc-devel Logs

Mar 22 2023

12:29 AM -!- #linuxcnc-devel mode set to +v by ChanServ
04:37 AM andypugh: pcw-home: Yes, figured that out, fill the data FIFO with both sets of data, then set the two frame sizes. That’s going to need a change to the pktuart driver
04:38 AM andypugh: (Which I have already done locally)
05:04 AM -!- #linuxcnc-devel mode set to +v by ChanServ
06:54 AM -!- #linuxcnc-devel mode set to +v by ChanServ
08:05 AM -!- #linuxcnc-devel mode set to +v by ChanServ
12:56 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:43 PM -!- #linuxcnc-devel mode set to +v by ChanServ
03:47 PM -!- #linuxcnc-devel mode set to +v by ChanServ
07:24 PM andypugh: pcw--home: Still struggling.
07:26 PM andypugh: https://paste.debian.net/1274963/
07:27 PM andypugh: (Note that it consistently gets 994 bytes, but that is limited to 40 in the return array)
07:28 PM andypugh: The scope trace looks OK.
07:28 PM andypugh: https://photos.app.goo.gl/GfNc4PfnfXyrfJRN9
07:29 PM andypugh: Left side is 7i96 send, data 01 01 00 00 00 08 3D CC
07:29 PM andypugh: Followed by the response, something like 01 01 01 0F <checksum> <schecksum>
07:31 PM andypugh: I don’t know where the 20 in the returned data comes from, I don’t think that there is a 20 in the packets.
07:32 PM andypugh: Using the USB/Serial and a serial terminal (cutecom) I get valid responses to the commands, so the relay board does work.
07:32 PM andypugh: An ideas? Termination network needed?
08:01 PM andypugh: pcw--home: An additonal data point is that the date read back is exactly the same if I unplug the header on the 7i96 board…
08:49 PM andypugh: Looking at the data in some detail, I can’t see a stop bit onthe last byte either. I agree with the UART on that point.
10:43 PM pcw--home: I would guess bias/termination (and or wrong RX baudrate)
10:45 PM pcw--home: "You might try adding bias resistors (300-600 Ohm from +5 to RX-,TX-, 300-600 Ohm from GND to RX+,TX+)"