Has anyone used modscan32 for debugging?
Thread Content
This post was last edited by hawk1251 on 2019-2-28 at 18:52. I want to test the communication between the motor protector’s smart meter using the modscan32 software; the address, baud rate, even parity, 1 stop bit, and 8 data bits in the software are all set exactly the same as those on the meter. Reading any data always results in a timeout. I would like to ask the experts: are there any other settings that need to be adjusted? Please give me some guidance. Thank you. . . I searched online for many instructions, and they were all more or less the same.
First, determine whether the parameter settings you mentioned are compatible with the instrument, check whether the debugging tool (whether the wiring for converting 485 to 232 is correct and whether it functions properly), and verify that the computer’s serial port settings are accurate. Then, to check whether the software protocol settings are correct, these are the main items to examine.
Check whether the serial port number generated by the serial-to-USB converter is too large; if so, change it to a smaller value, and then set it to the same value in modscan
This post was last edited by xxkhc on 2019-3-4 at 13:53. Your debugging interface image keeps spinning and is not visible; therefore, I can only say that a timeout indicates a lack of connection. Have you chosen the correct protocol, either RTU or ASCII?
There’s no problem with any of this. I was wondering: if the address is incorrect, will it still be possible to establish a connection? I’m able to use the serial port debugging tool without any issues.
If the address is incorrect, it won’t be possible to connect. It’s the same principle as when you go to find someone – if the address is wrong, you won’t be able to find them.