Simulate I/O reaction without S800
Hello,
Current Situation: I have a System A (AC 800M and TB820/ S800) on which I want to test an application software. Therefore the digital In/Outputs shall react in simple logics. E.g. Digital Output sends a Heater On Command. The digital Input shall receive a Heater is On Feedback with a time delay t. Normally I do this, using the force function in the Hardware tree. Since I exceeded the number of signals I can handle by hand I would like to have a counter part.
Goal: Having a System B (AC 800M) which is directly connecting fibre optic channel to system A. The software running on system B shall than emulate variable S800 Cluster set ups. Where in the software behind I would be able to implement any logic in ST.
Does anyone have an Idea? Is there a way of connecting two AC800M? Or any coupling Hardware?
Current Situation: I have a System A (AC 800M and TB820/ S800) on which I want to test an application software. Therefore the digital In/Outputs shall react in simple logics. E.g. Digital Output sends a Heater On Command. The digital Input shall receive a Heater is On Feedback with a time delay t. Normally I do this, using the force function in the Hardware tree. Since I exceeded the number of signals I can handle by hand I would like to have a counter part.
Goal: Having a System B (AC 800M) which is directly connecting fibre optic channel to system A. The software running on system B shall than emulate variable S800 Cluster set ups. Where in the software behind I would be able to implement any logic in ST.
Does anyone have an Idea? Is there a way of connecting two AC800M? Or any coupling Hardware?
Asked 10 months ago
Answers
0
If it is just to simulate , you can create an simulation application for your process and connect the simulation application with actual apllication using access variable.
Answered 10 months ago
1
The secret is ... don't assign the IO variables to the hardware channels. You should only do this at the LAST stage of the project.
Run everything in a soft controller (s) and write a simulation program. The soft controller needs almost zero CPU and it doesn't cost anything. Transfer the application to the physical controller and assign the IO only when project software testing is completed.
Run everything in a soft controller (s) and write a simulation program. The soft controller needs almost zero CPU and it doesn't cost anything. Transfer the application to the physical controller and assign the IO only when project software testing is completed.
Answered 10 months ago
Add new comment