controlx-io / logic-prover-support Goto Github PK

Hi,
I wanted to try using it on my spare computer with Debian 9 and had an issue. When I double clicked the downloaded file plc-logic-prover-linux-0.1.8.AppImage it opens "Open With" dialog.
How can I install it?

Thanks,
Shane

To replicate the error:

• Click Duplicate Action Unit
• In the same Action Unit click Move to
• Change Name
• Click Save button

Result:

• No changes saved on Save button click

Expectation:

• No error and change saved on Save button click

Workaround:
After Duplicate and Move To click on another Action Unit. Come back to the duplicated Action Unit and Save it after changes.

I have been using your application for some testing and would like to make some changes to how the application works. Could you provide the application files as open source?

I plan to use this for a CODESYS project for testing.

Any actions that check for the value of a tag are looking for an exact value from the read or the test fails. I am especially interested in the case of a Unit test when I can only test for a exact value to be reached in an exact amount of time. As the test exists now, I don't believe I can test a PID loop easily to ensure that it is correctly configured for normal or reverse acting. When I am testing or training operators I have a PIDE simulator that just allows me to tell it the EU range and whether it should simulate direct or reverse acting control. It then uses 2nd or filtering to move a simulated PV toward the SP. I don't want to change the actual PID constants in the loop so I just take a stab at deadtime and 2nd order filter time in my simulator to ensure I capture whether or not the loop is responding in the correct direction
If I could could configure a test that says:

reaches a value of xx.xx or greater (rather than an exact value) within x seconds (rather than getting to the value in a precise amount of time) I could then test to see that the PID loop is configured correctly or not.

It would be beneficial if there can be provision of defining macro variables. It would help in similar tests but with a different tag name. For example if I have 50 temperature sensors, each having a value, warning setpoint, interlock setpoint, warning status, interlock status, interlock latch, interlock bypass, then creating 50 separate unit tests is some work. Instead if I can define $Sensor in a unit tests, then I can copy 50 instances of those unit test and just change $Sensor.

App version: 0.1.10
Occurrence: Constant presence on VMs with Windows 7 and Windows 10. However no issues on a computer with Windows 10 and on MacOS 10.15.4.

Description:
When running the test on VM it fails randomly with TIMEOUT errors and sometimes shows negative values on action duration. Running the same Project on a computer passes all the actions and tests.

To replicate the issues:

• Create PLC rung as below
  
• In Unit Test set Define input actions to DI_PUMP1_TOL_OK = 0
• Expected output change to LS1_o_Healthy expect 0 after 0.05 second
• In Post execution parameters add DI_Reset_RQ toggle to 1 for 1 sec

The unit test will PASS but doesn't reset to initial state.

Suggestion:

• Define input actions need to be reset to initial state prior executing Post execution code

Workaround:

• Add Set Tag Value and Reset Tag Value after the Unit Test where set DI_PUMP1_TOL_OK to 1 and toggle DI_Reset_RQ, respectively.
• Cons: it becomes too messy.