IO-Warrior output

[da-andy]

Hello,

currently we've some problems using outputs on an io-warrior device.

we'd like to set single output pins on different events using the exec_send_iowarrior command.

by now we've got working outputs only a hexadecimal value which sets all pins at once and doesn't
take care on which outputs were active before.

is there a way to set only single pins without changing all other pins?
if yes, could you give us an example?

--
thanks a lot!

[radio42]

OKi, guess I need to send you a debug version then to see what is going wrong!

[radio42]

You might actually use the "EXEC_SEND_IOWARRIOR" control command on 2 ways:
a) EXEC_SEND_IOWARRIOR <bytes>
or
b) EXEC_SEND_IOWARRIOR <pin>|<state>

The <bytes> string must be a HEX string (prefixed with 0x) which will be sent to the output or the output pin(1..50) and state(true, false) is directly used.
a) might be used to set the state of all pins; while b) might be used to set the state of a single pin.

Example:
EXEC_SEND_IOWARRIOR 1|true
EXEC_SEND_IOWARRIOR 7|false

[da-andy]

Hello,

the commands you described are not working in our environment.
we're currently using the demo version (3.0.12.1).

are there limitations in the demo?
if yes, is there anything else we have to consider during the evaluation of your software?

--
thanks

[radio42]

No there are actually no such limits in the demo.
How do you test things?
And which IOWarrior product and version are you using in your test ?

May be I need to send you a test version to see where your issue is exactly...

[da-andy]

we've tested in this order:

- enable io-warrior in GPIO/Remoting settings
- open monitor and do some inputs - works
- go to events/commands and set exec_send_iowarrior 24|false or 24|true (iowarrior40)
- test the command - nothing happens, output does not respond
- go back to GPIO/Remoting settings and open monitor again
- Propfrexx hangs and does not respond anymore, needs to be killed via task manager

the system is a win7 pro x64 and a iowarrior40, also tested with iowarrior56.

[radio42]

This issue is now being fixed in v3.0.12.4.