Has anyone seen this cold-boot persistence issue on an Advantech ADAM-6717 with integrated Node-RED?
Firmware: A1.01 B027. Web portal: V4.1.3. Two 4–20 mA analog sensors are connected to AI0 and AI1.
AI0 remains enabled and working. AI1 keeps its 4–20 mA range, but its enable bit returns from 1 to 0 after physically removing and restoring the 24 V supply. Selecting AI1 → Channel Mask → Enable → Submit restores normal measurements temporarily.
To test persistence:
- Using the manufacturer-supported whole-I/O configuration export/import, we cloned an export and changed only AI1 in
ai_enable:[1,0,0,0,0,0,0,0]→[1,1,0,0,0,0,0,0]. - Import succeeded. Both channels measured normally, and the mask survived the import's automatic software restart. A subsequent export confirmed the configuration matched.
- After physically removing/restoring 24 V, AI1 returned to
En=0, and a subsequent export again showedai_enable: [1,0,0,0,0,0,0,0].
All 25 Node-RED flow objects remained unchanged, with no known configuration-writing flow. This question concerns the device's analog-input enable configuration, not Node-RED context persistence. We have not established the root cause.
Manufacturer support has already been contacted. Has anyone experienced this exact difference between the import-triggered software restart and a cold boot? Is there a documented persistence/commit step, a startup service that restores the analog enable mask, or a compatible firmware fix?
Thanks for any documented pointers or firsthand experience.