WRITE ANALOG OUTPUTS THROUGH PROCESS IMAGE NOT WORKING

[LEOMENA]

I have my Revpi Connect + write values to the Analog outputs of my AIO, but I don't measure any voltage or current. My Analog Inputs are working fine though but in 4-20 mA & 0-10 VDC.

My configuration is as follows:

2021-10-15 (1).png (465.93 KiB) Viewed 4745 times

2021-10-15 (2).png (467.33 KiB) Viewed 4745 times

I am forcing writes using piTest - w Out1_HPUSetPt, 500 for example to my Analog Output 1, but nothing takes effect (No voltage at the output configured as 0-10VDC). In Fact when I read the recently written image value with: piTest - r Out1_HPUSetPt ... all I get is zero.

Again my Inputs are working fine and I can read them through the process image, also using piTest.

I do have a RED LED FLASHING on my my AIO IN status Led, I think you should know.. I am not sure if that is causing the problem. In the documentation I found that this light means that there is a Range Error. A too high a voltage or too high a power supply at one or more inputs. Check the input status in the process image.

My configuration is (Left to Right): DIO + AIO + CONNECT(+)

Please help me know what's wrong.
Thanks

[nicolaiB]

Hi LEOMENA,

Are there any other processes which are writing to the process image (like nodered)?

Nicolai

[LEOMENA]

Hi Nicolai, No processes (made by me) are running, I am only using piTest to force the changes..

[LEOMENA]

Nicolai,

To clarify, Nodered is active (on the Pictory Config) because I plan to develop a program on Nodered later on. But I did not code anything yet...

[nicolaiB]

Hi LEOMENA,

you please try if the analog outputs are still unresponsive, when you stop the revpi nodered backend daemon (sudo systemctl stop noderedrevpinodes-server.service)?

Nicolai

[LEOMENA]

Nicolai,
as it turns out, this morning I tried again, before running the command that you requested me to run, and the Analog Outputs were responding fine. Only difference is last night I shutdown the whole setup after being on for a few days and restarted today.
I need to find out why this is happening, my project involves handling high pressures in hoses (> 2000 psi) and cannot afford my outputs to go unresponsive for personnel-safety reasons. I am guessing the memory got trashed somehow.. your thoughts?

Any recommendations will be helpful.

PS. BTW, I have another topic pending (also with you) regarding Modbus Communications, whenever possible and at your earliest convenience, please reply..

Again Thank you.

[nicolaiB]

Hi LEOMENA,

as metioned in your other thread: please share the log files (/var/log/kern.log) before and after the issue. Also make sure that the system is up to date.

Nicolai