PLUS+1 Software > General controls

One program, but two or more similar machines

<< < (3/3)

FluidPowerTom:
I didn't realize before that you were referring to screens.  No, there's not a way to do screens in GUIDE structured text.  I would say that there's no great reason for you to learn Structured Text unless you have a need for it. 

I'm still not 100% clear on what you're needing to do, but it sounds like it may have more to do with functionality within the screen editor.

Marbek_Elektronik:
There are 3 Softwares which have many common pages and screens.
But this softwares are to different to manage this with parameters.

So, if I change a page in one software, I have to change it in the other softwares too.

But the problem ist the classic screen editor.
I have to  think about it, how to realize this.

oiltronic:
Sounds like you have two parts of the software you want to share between machines that are only a little bit different:  state-machine logic and screen software.  Each are handled in different a way.  And how you do it depends how much of the software is the same and how much is different.
For sharing state-machine code between machines there are two basic options:

* Make separate software applications for each of the 3 machines, and put common state-machine steps into pages that are exported into a personal library and shared.  The shared pages can also have input parameters which select which parts of the state machine are used.
* Use the same application for all 3 machines, then use control logic and boolean switches, along with read-only boolean parameters (or NV parameters set by the Service Tool, or an external input set high or low), to select which sections of the software state machine are enabled.Sharing classic screen software between applications is more difficult:

* Make a new application for each machine by copying an entire application, then make the changes.  (I don't need to make major changes to a screen application after it ships, so this works for me.)
* Make a single application for all 3 machines, and make lots of different screen areas for the different parts that are enabled according to the same parameters or inputs mentioned above.  I've done this for one machine where the operator can select what to display.The Vector-based editor is new to me but I noticed it has import/export capability, which might be nice.

Marbek_Elektronik:
Thanks,
I will try it and will document my way here in the forum.

ZanInno:
I recently did a project that used 2 controllers with the same program.  I used two inputs to identify where the controllers were installed.  If the controller were was installed on the RH side, "input1" was 12V.  If it was on the LH side, "Input 2" was 12V.  By using these inputs, the code set an EEPROM var that would define the Node ID.  This allows the service to connect to each controller.  I also flashed the green controller light in a different sequence depending on the node id.

Now you can use that node ID / Input variable in your logic to have a different function depending on the location of the controller.

Navigation

[0] Message Index

[*] Previous page