Re: [beagleboard] Re: UART4 RS485 (RTS) not working

Yes, Dont solder Rx-serial to Rx-CAN-bus. The email/posts above are concerning the RTS pin and allocating another BeagleBone to it: the DMA one and not GPIO one On Thu, Apr 18, 2019 at 6:46 PM wrote: > Hello > may be there is wrong hardware design with Waveshare RS485/CAN Cape. I > don't think

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

Did you come right? Sorry, this account-email is not read frequently On Tue, Nov 21, 2017 at 5:25 PM Jeff Andich wrote: > Thank you! > > ?? Are you saying that lib modbus (which we haven't tried) has issues > with reliably toggling the RTS line?? > > One clarification with what I meant by

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

Thank you! ?? Are you saying that lib modbus (which we haven't tried) has issues with reliably toggling the RTS line?? One clarification with what I meant by "manual toggling of the RTS line." By manual software toggling, we specifically mean toggling the RTS line in the protocol as follows:

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

Hi, With RS485-modbus-converters the timing of the RTS pin is CRUCIAL. Software toggling (GPIO toggling) of this pin (in the RS485/libmodbus library someone added this capability) have shown (on oscilloscope) to not be repeatable or works 1 in 30 attempts. I think we used the stock standard

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

dont forget to remove jumper that bypasses RTS pin and grounds/raises it for sending/receiving only. can't remember the order On Tue, Nov 21, 2017 at 11:46 AM Rnd Mpt wrote: > Hi, > > With RS485-modbus-converters the timing of the RTS pin is CRUCIAL. > Software toggling (GPIO

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

A couple of things you may want to investigate before you use the OMAP driver vs. the 8250: 1) According to an older Wiki from TI, the OMAP serial driver doesn't use DMA in serial transfer, but 8250 does. Not sure if this is still the case??

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

I'm fairly confident the answer to my question about whether the 8250 driver implements "partial 485 capability", (allowing Python or a C#/.net application to manually control the RTS line for a given UART via the driver) is NO. But the OMAP driver DOES appear to allow this. When I toggle

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

Hi, Will the 8250 driver still allow "manual" control of the RTS line for a given UART from an application like Python or C# (where the application toggles the state of the RTS line, rather than driver, after sending a request message in order to toggle the 485 XCVR), or is the OMAP driver (in

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

We used the rs485 version/branch of the modbus on github. Sorry i meant to say rts instead of cts. I used my github as notes. Follow readmes and see if it helps. Its been a while since we did this. Let me know if more help is needed https://github.com/rwdutoit/beaglebone?files=1 On Mon, 13 Nov

[beagleboard] Re: UART4 RS485 (RTS) not working

https://github.com/RobertCNelson/bb-kernel/issues/38 2017. november 10., péntek 20:33:49 UTC+1 időpontban dmezz...@gmail.com a következőt írta: > > Did you ever get this to work > > I am using the Nelson yakbuild kernel 4.9.45 and disabled the 8250 and > enabled omap serial in kernel

[beagleboard] Re: UART4 RS485 (RTS) not working

Hi Mat, I have the same issue: any response yet? On Tuesday, March 28, 2017 at 2:52:07 PM UTC+2, Matthew Bezuidenhout wrote: > > Hi all, > > For days now, I've been attempting to get the Waveshare RS485/CAN Cape to > work on Beaglebone black. > > I've used kernels 4.4.x and 4.9.x-ti mainline,