| ??? 12/03/09 15:18 Read: times Msg Score: +1 +1 Good Answer/Helpful |
#171439 - Comparison with something known working Responding to: ???'s previous message |
That was one of the reasons why you should either compare your data with that of the PLC that was able to communicate, or with an existing Modbus-capable program. Comparing what works with something that doesn't work can quickly help narrowing down the difference. Just sitting and looking at a packet can have you staring for days and days without noticing the error. |
| Topic | Author | Date |
| Modbus | 01/01/70 00:00 | |
| What testing have you done? | 01/01/70 00:00 | |
| Don't use hyperterminal | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| Still lots of debugging left | 01/01/70 00:00 | |
| Modbus | 01/01/70 00:00 | |
| Not very helpful | 01/01/70 00:00 | |
| Modbus | 01/01/70 00:00 | |
| Still need to break the problem down into smaller steps | 01/01/70 00:00 | |
| Modbus | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| Parity | 01/01/70 00:00 | |
| Oscilloscope results? | 01/01/70 00:00 | |
| open source | 01/01/70 00:00 | |
| Also RTU Framing | 01/01/70 00:00 | |
| Framing, addressing etc has been discussed | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| Bad CRC order!! | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
| Don't know why, | 01/01/70 00:00 | |
| Comparison with something known working | 01/01/70 00:00 | |
| what device address | 01/01/70 00:00 | |
| modbus | 01/01/70 00:00 | |
I would do this... | 01/01/70 00:00 |