• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problems with the communication of the RS485 interface
#8
I mean the python software driver you are using right now.

And yes I expected it will work in rtu-buffered mode only ... this is exactly what I was writing in one of my previous posts where I was analysing what exactly this buffered node.js code is doing.

And my result after examination was that based on the code I see the "buffered" software waits for a complete Modbus RTU receive message and is buffering it while it is incomplete and only sends back a complete message back to the application. And this was the reason for me asking you if python does it the same. You answered "No, probably not.". I share your opinion without looking into the python coding.

Does the the ModbusClient() function you are calling has more than just the "timeout" value as parameter, for examplean "inter-character-timeout" that usually defines how long to wait between the single characters in a stream after a start character has been detected? I can't answer since I don't know the API.

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Messages In This Thread
RE: Problems with the communication of the RS485 interface - by Armin@netPI - April-28th-2020, 12:53 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  NPIX-RS485 with auto direction control now available Armin@netPI 11 8,836 May-15th-2020, 10:46 PM
Last Post: EnergyKonnex
  connecting Mitsubishi via RS485 COswald 11 8,812 January-14th-2020, 10:58 AM
Last Post: Armin@netPI
  Dual RS485 Ports primmer 2 3,173 September-25th-2019, 09:43 AM
Last Post: primmer
  Is there a demand for a RS422 interface? Armin@netPI 0 1,797 April-29th-2019, 10:58 AM
Last Post: Armin@netPI
  Communication between BCM2837 and netX51 on netPI RTE 3 Armin@netPI 0 2,091 December-3rd-2017, 01:19 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)