-
Notifications
You must be signed in to change notification settings - Fork 3
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
Startup fails reading coil 51 #105
Comments
If getDeviceInformation is replaced with setting static device info, the first MQTT messages are published, and process continues but stops again at coil 52.
|
When also getSettings is replaced with hardcoded values, the program starts normally.
As a conclusion, this particular Pandion hardware cannot return parameters for getDeviceInformation or getSettings from coils 51 and 52. Also all the write operations appear to fail as well.
|
Can you try an older version like 2.5.0? |
That fixed the device and setting recognition, thanks! However, the writing of anything still fails. But this could be some kind of hardware limitation with this device as also some of the features like "away" and "long away" don't appear to activate through the EDA wall panel.
|
Okay, I'll try to fix the startup issue. #104 (comment) here version 2.01 is referred to as "wanha" (😅), and apparently these really refuse to answer to undocumented registers. Very strange that the unit is read-only, I have not encountered that before. Can you verify that the device is configured to use Modbus address 1, not 0 (see https://github.com/Jalle19/eda-modbus-bridge/blob/master/docs/CONNECTION.md#troubleshooting)? |
FWIW, in an e-mail conversation I had with Enervent we tried solving the same problem you're having (modes cannot be changed via Modbus) and in that case the problem was the Modbus address was set to 0, both on the unit itself and by specifying |
Nevermind, I see in your logs that you're using slave 1:
|
I have sent an email to Enervent, asking what could cause the read-only behaviour and if firmware upgrade would be possible. |
Removing my earlier comment due to error in mboll logics. Apologies again for confusion. |
@Jalle19 sorry for the confusion earlier. Regardless of the mistakes earlier, I think I have found the reason for issues with this legacy device. It doesn't appear to handle reading or writing single coil correctly, but if you do it for multiple, it works:
Even the coil 51 can be read if I read all the 72 coils in one go:
|
Confirmed: writing for this device is possible if all the coils [0...n] are written in one command. So, the only way I have found how toggle manual boost on is to read values of 11 first coils, inverting value of coil 11 and writing all 11 immediatelly. Not elegant but works:
|
Very strange. I would still try another RS-485 adapter, could be that it behaves differently. I've had great success with Waveshare. |
Yes, perhaps they have implemented incorrectly the single registry read/write function on this one: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC However, good to recognize that someone on Älykoti-facebook group mentioned that some of these devices don't accept single entries. |
This is what Home Assistant says about mine |
The same manufacturer and even the same model. Either my device is faulty, or my Enervent device is just very picky in functions that it accepts. At least the mode settings (which are in the first coils) could be implemented with the logic I wrote, but as temperature setting is in holding register #136 it is a bit extreme to write all values before that. |
New finding! The reading can be done in segments, probably writing as well. Just like the individual reading was possible for coils 1, 9, 17, 25... I can also read multiple if I start from those - but not in between!
|
Looks like on my Pandion eco EDE (MB v1.97, display v2.01) the program fails to start as it gets stuck reading coil 51.
The device is originally from 2009 but the EDA board was replaced in 2019. If I understand the older Enervent documentation, this coil 51 is not documented.
The text was updated successfully, but these errors were encountered: