I purpose a messaging overhaul. Right now we use message queue, conditional variables, mutexes and even files to communicate between process and threads.
My main idea is to use ZeroMQ as replacement for above methods.
A main variable server on Zenom gui will handle all variable exchange / communication. Even state and frequency info will be shared via variable server.
User process will connect that server and exchange variable, state .. info with Zenom.
Zenom will become only plotting and variable editing software. User will use zenom provided class to make easy real time applications that can talk main plotting server (Zenom), also bulding blocks like differantiator, integrator etc. will be provided by main Zenom software bundle as cpp classes. This is already used in this way.
With this new technique zenom applications can run anywhere even in Alaska 😄. Also multiple applications can run simultaneously.
Here is a quick diagram:
You can edit this diagram via: link
I purpose a messaging overhaul. Right now we use message queue, conditional variables, mutexes and even files to communicate between process and threads.
My main idea is to use ZeroMQ as replacement for above methods.
A main variable server on Zenom gui will handle all variable exchange / communication. Even state and frequency info will be shared via variable server.
User process will connect that server and exchange variable, state .. info with Zenom.
Zenom will become only plotting and variable editing software. User will use zenom provided class to make easy real time applications that can talk main plotting server (Zenom), also bulding blocks like differantiator, integrator etc. will be provided by main Zenom software bundle as cpp classes. This is already used in this way.
With this new technique zenom applications can run anywhere even in Alaska 😄. Also multiple applications can run simultaneously.
Here is a quick diagram:
You can edit this diagram via: link