Dear ixo65,

ixo65

No, that does not work.
You can not write from different places (LOGO and for example App) in the same address of VM Memory.

It is my understanding that vctoon is attempting to build a network of devices that work together. It is best achieved if the same requests and configuration is available to all units in the network.

I have voiced my opinion on how it could be approached in general terms.

You are the expert in implementation. I welcome your ideas on building a network for co-operative devices.

BR

@vctoon:

Please see the attached proposal.

@vctoon:

much-too-complicated-idea to synchronise two numerical values  - - - animate gif attached

Thank you for trying to find a solution!

As I not yet understand the 'easy' way completely, I will stick to this configuration:

• both logo!s configured as master.
• both have their own logic
• I preserve my VB-list (spread over the 2 logo's - none is used twice)
• If I want to read/write a VB, I specify to which logo!.
• for functions that are common for the 2 logo!s, I use 2 VB's. One local (x) and one remote (y), and for the other logo I swap those two, so the local becomes (y) and de local (x). Not easy to explain, but I think it works (see attachement)
• If one logo! fails, I still have the other floor that keeps running.
• One logo is connected to the CMK2000 and is the main hub for the KNX communication, If something needs to be transferred to the other logo, I use an extra network output.

You're right,

but I mentioned some posts earlier that I've ordered a new OBA8 to swap with the OBA7, to make things easier. it hasn't arrived yet, so I can't test for this moment.

vctoon

(other detail: I already ordered a new OBA8 to swap with the OBA7, which is moving to the garage to control the exterior and garage lights).