Ftc dout 2 not working with tcp cmd

Hello, I am using an FTC305 with firmware 3.7.0-rc.22. DOUT1 works correctly via TCP using “setdigout 0” and “setdigout 1”.

However, DOUT2 does not work. When I send “setdigout ?0” or “setdigout ?1”, the device responds with “DOUT1:IGNORED” and DOUT2 does not change state.

Is DOUT2 supported by this firmware, and what is the exact TCP/GPRS command syntax to control it?

Hello,

command logic you are using is fine.

It is likely that DOUT2 is being used by other scenarios that has been configured, since there are priorities and setdigout is the least prioritized, it will not override the scenario settings

All DOUT control functionalities now have their own priority (non-configurable). Depending on priority DOUT control may be overtaken by higher priority functionality without finishing the previous scenario.
DOUT control scenarios and functionalities by priority:

  • Immobilizer (highest priority)

  • DOUT control via call

  • Green Driving

  • Jamming

  • Overspeeding

  • Towing

  • Idling

  • DOUT control via SMS (lowest priority)

For example, if jamming will be detected during Overspeeding, then Jamming functionality will control DOUT.

Important Note: Immobilizer cannot be used with any other feature with same DOUT as it takes full control of the DOUT.