Tips and Tricks
This is where you can post items of interest that are not covered by other forum sections.
83 topics in this forum
-
- 1 reply
- 3.2k views
-
- 6 replies
- 3.5k views
-
- 2 replies
- 16.5k views
-
- 0 replies
- 3.4k views
-
- 3 replies
- 3.3k views
-
- 1 reply
- 3.7k views
-
- 4 replies
- 4.4k views
-
- 4 replies
- 3.5k views
-
Member Statistics
9,138
Total Members1,206
Most Online
-
Topics
-
-
Who's Online (See full list)
-
Posts
-
Just noticed something in your Modscan screenshot. You are communicating to ID 1. Yet in your PLC ask you are trying to reach ID2. You need to change your sensor's ID, using Modscan to set the sensor's ID to 2 (or higher). Many Modbus devices default to ID1, and building your plc program to allow the plc to change the parameter, and also not have conflicts in addressing, is a good idea. For instance, I often make the PLC ID 10. This is purely abitrary, but it is NOT 1. So any new modbus device can be put on the line, and the plc can set it appropriately using built in coding. cheers, Aus -
By Gabriel Franco · Posted
According with Modscan results, you must modify Modbus block: - Slave ID: 1 - Slave start of vector: 8193 - Vector length: 10 -
After looking in detail at your screenshot again, I've just realised what Kratmel was saying earlier. You are actually asking for too much in the RHR, as the function block already knows the type of register. Kratmel rightly suggested changing the D# to 8192. I initially thought he was referring again to the offset I had spoken of. I think this is the hiccouph. Change it to just 8192 and you should be able to do consective reads, and then pick out what you want. cheers, Aus
-
Annnddddd, what about the connections etc?
-
Dear Ausman and Sgull, thanks for your support. I dropped the length of the vector to 1 yet, it dd not read. Find attached image of the values I got when using ModScan64 with my laptop
-
-
Blog Entries
-
