-
Notifications
You must be signed in to change notification settings - Fork 6
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
Nefit EcomLine HR43 not correctly detecting the bus signal #13
Labels
question
Further information is requested
Comments
Thank you.
|
I also had an idea to move the interface to the place where thermostat currently is, is that good? |
@iamceph Just give it a try. I also have the interface around 5 a 6 meters from the boiler. I think it will improve the signal because there will be more voltage drop across the wires. |
Tried it, with same result sadly :/ |
Did you try tx_mode 4 with the thermostat connected ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@iamceph I moved the issues to this detect because it is a different setup then the original issue.
If I look at the first data you posted (in tx_mode 4):
(00:04:55.494) irt_rawTelegram: 01: 00
(00:04:56.674) irt_rawTelegram: 18: 01 01 FC 07 FF 00 FF F2 07 29 45 58 73 52 25 43 78 07 FF A1 82 00 91 F4
This look like it almost detected the correct signal but it is missing some bits. So my first question is, what thermostat are you using and what is the length between the thermostat and the boiler. This may be resolved by increasing the 1,5 MOhm resistor to a higher value.
The second test you did, with tx_mode 5, is a bit strange. Because I can see the boiler sending the polling messages (the 00, 01, 02 and 03) data. But I do not see the interface transmitting anything. Because it logs the msg to transmit before sending it. What interface board are you using ? A pre-modified board or did you build it yourself ?
The third test you did, tx_mode 5 and the thermostat connected will not work, because the iRT cannot handle two active devices.
The text was updated successfully, but these errors were encountered: