On TRB142 device in TRB1_R_00.07.14.3 firmware I set the “Modbus TCP over Serial Gateway server ID” parameter to User defined. Set “Server ID” field to 1.
It doesn’t work.
It sends the server ID received via MODBUS TCP to the serial port as the slave address and not the set address 1.
It seems like the server id Configuration field is not working properly.
My experience, the last good version was TRB1_R_00.07.13.4!
Hello,
From the description, the issue sounds very unclear. Could you:
- Provide a topology of how you have your devices connected, and what data is supposed to be sent from one to another?
- Provide the steps of how you’re testing this exactly.
Any supplementary images would help out as well.
Regards,
M.
Hello,
I have set up a TRB142 device for MODBUS TCP serial gateway function.
I received the messages on the RSR232 port with the YAT terminal program. I sent the MODBUS TCP command 03 Read Holding Registerts to Unit ID 9 with the QModmaster program. I am reading 2 registers. In the TRB142, I have set it to always send the message to modbus node address 1. The TRB1_R_00.07.13.4 firmware works fine, but the TRB1_R_00.07.14.3 or above firmware is already faulty in the modbusgwd program. You can see in the terminal that node address 09 is sent out on the serial port.
The Modbus RTU device must always send node address 1.
The settings are completely identical in both devices!
GOOD firmware TRB1_R_00.07.13.4:
The first byte is 01h!
BAD firmware TRB1_R_00.07.14.3 or above:
The first byte is 09h!
I hope it is now clear what is causing our problem.
Best regards,
Lajos
Hello,
We have tested this setup and were unable to reproduce the issue on the firmware version 7.14.3.
Our testing station was set up this way:
We had YAT run on PC1, while QModMaster was running on PC2 (from it, we sent the data to our PC1):
As you can probably tell, we’re not experiencing the same issue that you are.
To investigate this further, I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is 14647.
Thank you,
M.
Hello,
Unfortunately, I did not receive the form from you.
I would also like to continue the conversation in private.
Best regards,
Lajos
Hello,
Please check again, I’ve resent the form.
Regards,
M.
Hello MatasR,
The previously reported issue also exists with the TRB1_R_00.07.16.1 firmware. When can we expect a fix for this issue?
Best Regards,
Lajos
Hello, Lajos,
No response has been received as of yet. If I have any updates, I’ll reach out to you via e-mail, as I’ve already did.
Regards,
M.
Hello MatasR!
The previously reported issue also exists with the TRB1_R_00.07.13.3 firmware!!!
When can we expect a fix for this issue?
Best Regards,
Lajos
Hello,
This is being actively investigated, but unfortunately, we’re not able to reproduce the issue locally whatsoever. Coming back to our previous conversation for a bit, I remember asking particularly what kind of data is being requested/sent & from where, however, I don’t think you’ve ever mentioned that in your replies, could you perhaps elaborate on that a bit more & tell me?
Regards,
M.
This topic was automatically closed after 60 days. New replies are no longer allowed.
@Lajos ,
I’ve reopened this thread; you should be able to send replies if you were unable to previously.
Thank you,
M.