-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write doesn't work anymore #25
Comments
Can you post your configuration for that please? |
"type","topic","col2","col3","col4","col5","col6" poll,mc6,16,0,22,holding_register,15 poll,mc6,16,60,27,holding_register,15 |
I'm having errors on 61, 62, 63, 64. Only writing, reading works good as always |
Well it seems like your device does not support function code 6 (preset single register). Unfortunately Modbus is very often not thoroughly implemented. I have seen a couple of devices that do not support function code 16 (write multiple registers) when writing only one register. Since that seemed to be common I changed spiciermodbus2mqtt to always use function 6 when writing only one register: 687b9a9 A device that only supports function code 16 that is a new quirk. I will add a a command line option to exclude specific function codes. |
Wow, Indeed modbus implementations are a mess. I roll back temporarily to version 0.65 and it's working. Thanks so much for the debug, and for the project, is being working very well. |
Please use the command line option --avoid-fc6 |
Hello,
I was using the spiciermodbus2mqtt from some time, and was always working.
I updated the other day the raspbian to bookworm, and update the spiciermodbus2mqtt to the latest version (i'm not completely sure which version i was at) and now i cannot write anymore.
Any ideas of what could go wrong?
MQTT LOG:Received PUBLISH (d0, q0, r1, m0), 'mc6_music_teste/mc6/set/SetTemperature', ... (3 bytes)
Writing to device mc6, Slave-ID=16 at Reference=64 using function code 6 FAILED! (Devices responded with errorcode IllegalFunction. Maybe bad configuration?)
The text was updated successfully, but these errors were encountered: