Sixteen LV Digital Inputs Testing of Board Acting Strangely with Python and CLI

[jjohannson]

I'm using a Raspberry PI 4 with 4 gigs of memory with Python 3.11.5. I'm trying to test out 3 - 16LV digital input boards. All I'm trying to do is get the input LEDs to turn on. At first try I was able to get nothing to light up and then realized I had to change the LED mode. I then updated the firmware and was able to get LEDs 1,3,5,7 to light up green when using the command:
16inpind 1 ledwr 65535.
If I try to turn a pin on by issuing command:
16inpind 1 ledwr 1 1
It does not turn on and led reads 0

As for Python code I can't get the board lights to do anything. However, the LED statuses read the correct written state.

I did update the firmware and originally the board behaved similarly but with red LED color. I'm not sure if I perhaps I have to do anything with the J2 pins.

 

[alexburcea]

Hi,

Could you tell me the hardware version of the card?
We might have some firmware/drivers bugs in the LED controlled by the commands part. When the LED's are controlled by the inputs, they act correctly?
Give us a few days and we will come up with a new firmware or drivers version if it's the case.

Alex.

 

[jjohannson]

Hello,
Thanks for the speedy response. The cards I have are version 3.0. I did test and verify that the inputs are ready correctly and LEDs are lighting up appropriately, GREEN for the odd channels and RED for the even channels.

This is the first time using these cards and was a little puzzled. One last thing, I downloaded the GIT repository for this card and in the update folder there are the 2 executables update and update64. I'm running bullseye on by Raspberry PI. When trying to run ./update64 0 (I do believe I'm running on 64 bit) I get a . bash: ./update64: No such file or directory . However ./update64 0 works.

Thanks for your time!