RichardEberhard

Thank you for your answers. Unfortuantely both solutions have disatvantages: 1.) This is a bit risky. Handling "the current state" of the outlet in the application can cause a lot of problems. The saved state in the application and the actually state of the outlet can become asynchronous very easily. There are many componentes that can have bugs. (My Program, sispmctl, the usb driver,...) and also someone else (user/program) can also trigger the outlet excidently. This will cause my software to not...

I made a patch file.

I just answered my question: see: https://sourceforge.net/p/sispmctl/bugs/23/

sispm_switch_on should check outlet state

Hello, I have a program like this: While true{ A=check_condition() If(A) Execute_bash_cmd(" sudo sispmctl -o 1") Else Execute_bash_cmd(" sudo sispmctl -f 1") Sleep(16sec) } So if A doesn't change, the same command is called again and again. Can this harm the relay(powerboard) in anyway? (Damage/wear the relay)? Is it save todo so or would it better to check the state of the relay before performing the Action? Thank You

Hello, I have a program like this: While true{ A=check_condition() If(A) Execute_bash_cmd(" sudo sispmctl -o 1") Else Execute_bash_cmd(" sudo sispmctl -f 1") Sleep(16sec) } Next So if A doesn't change, the same command is called again and again. Can this harm the relay(powerboard) in anyway? (Damage/wear the relay)? Is it save todo so or would it better to check the state of the relay before performing the Action? Thank You

Hello, I have a program like this: While true A=check_condition() If(A) Execute_bash_cmd(" sudo sispmctl -o 1") Else Execute_bash_cmd(" sudo sispmctl -f 1") Sleep(16sec) Next So if A doesn't change, the same command is called again and again. Can this harm the relay(powerboard) in anyway? (Damage/wear the relay)? Is it save todo so or would it better to check the state of the relay before performing the Action? Thank You

This isn't a question it's a bug. If the tcpdf lib isn't working properly on some...