Title: Issue with Modbus SINT16 Decoding Showing as UINT16 #2024
-
|
Body: I encountered an issue while debugging Modbus serial communication. I set the data type in my decoder to SINT16, but the UI still interprets the data as UINT16. For example, the data I transmit is 0x88FF. Normally, with signed interpretation, it should be -120, but the UI shows 65416. I’m not sure if this is due to a configuration error. Could anyone advise on what might be wrong? Thank you for your help. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hm. Your screenshots don't add up. You use MODBUS function 2 on channel 4 in your first screenshot which will never result in 65416 as it is a bit operation. If I put function 3 which you might have intended, decoding as uInt16 delivers 65416 as in your screenshot and if decoded as sInt16 the expected -120 for me (on the just released Artisan v3.4). Which Artisan version are you using? |
Beta Was this translation helpful? Give feedback.
-
|
You are right, it is now displaying correctly. Thank you very much; I had mistaken the function code. My version is 3.2.0 |
Beta Was this translation helpful? Give feedback.
-
|
Upgrade! |
Beta Was this translation helpful? Give feedback.
Hm. Your screenshots don't add up. You use MODBUS function 2 on channel 4 in your first screenshot which will never result in 65416 as it is a bit operation. If I put function 3 which you might have intended, decoding as uInt16 delivers 65416 as in your screenshot and if decoded as sInt16 the expected -120 for me (on the just released Artisan v3.4). Which Artisan version are you using?