# Advantech ADAM-6717 AI1 channel enable reverts after power cycle (A1.01 B027)

**URL:** <https://discourse.nodered.org/t/advantech-adam-6717-ai1-channel-enable-reverts-after-power-cycle-a1-01-b027/101973>\
**Category:** Hardware\
**Created:** [22 October 2026 06:52 UTC](https://discourse.nodered.org/t/advantech-adam-6717-ai1-channel-enable-reverts-after-power-cycle-a1-01-b027/101973 "2026-10-22T06:52:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vneville3](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vneville3/32/108687_2.png) [@vneville3](https://discourse.nodered.org/u/vneville3)\
**Post date:** [22 October 2026 06:52 UTC](https://discourse.nodered.org/t/advantech-adam-6717-ai1-channel-enable-reverts-after-power-cycle-a1-01-b027/101973/1 "2026-10-22T06:52:45Z")

</div>

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:

1. 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]`.
2. Import succeeded. Both channels measured normally, and the mask survived the import's automatic software restart. A subsequent export confirmed the configuration matched.
3. After physically removing/restoring 24 V, AI1 returned to `En=0`, and a subsequent export again showed `ai_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.