Closed brentk7 closed 1 month ago
Does anybody have any pointers on what I can do to troubleshoot or help fix this issue?
I will try to get to it later this week. Unfortunately, I do not have one of these boards so I need to see if Sequent changed the registers for the inputs in their code.
Much appreciated - please let me know if you need any info, logs or testing.
Update your relayEquipmentManager. I checked all the registers and the registers seem to match the 4rel4in from the Sequent codebase. It should be reading the correct i2c registers.
I have just pulled the latest version from github and am still getting the same error
Have you installed the cli from sequent to see if it works?
Yes - works fine from sequent cli and from sequent Node Red
I don't know why I was thinking that it was not able to retrieve the values from the device. As it turns out even your log shows a successful read of the register. However, the caught exception below reflects that it was not able to find the channel value for the input. I realized this last night and let it run all night pulling mock values.
Update your REM and let me know if it is doing its thing with the hardware.
Thanks that has fixed it. Just a note that the reaction with this is very slow (I have to hold the button in for at least a second). I assume this is due to some polling delays by REM?
I have a Sequent 4rel4in v4 card and have tried to configure the inputs to toggle service mode in njsPC. As soon as I enable the feed, I start getting errors in the log as shown below. I have tried using both inDigital1.value and plain inDigital1 as I am not sure what the difference is between them - but they both give the same error.![image](https://github.com/rstrouse/relayEquipmentManager/assets/25597360/8b56ee94-fba4-43a5-b072-c83c8c9d5e5f)