06-11-2018 02:42 PM
MCDUFF... Thanks a lot this is really next level stuff for me and a great way to learn from an advanced user. I can kinda see how it works and am interested in testing it. I'm not sure if I understand enough of it to troubleshoot it and maintain it though, going to have to spend some time with it to fully understand it.
06-11-2018 03:15 PM
My advice to you is to play around with it, using probes, highlight execution etc to see how things work. Once you get a basic idea, then add simple things. For example, make an event where the file name changes and bundle that name in the cluster. Learn how event programing works. Then make a state for data processing.
Good luck
mcduff
06-12-2018 02:57 PM
ok the code i posted is very close i have one hang up in it. Since i added the event structure its executing the consumer loop twice and generating (2) data files. I can't figure out why it's dong this does anyone have an idea?
06-12-2018 03:07 PM
A guess here:
mcduff
06-13-2018 07:29 AM
I replaced the Event structure with a case structure, new problem. There is significant lag between when the trigger event happens and when it is being registered from the queue to the lower loop, talking seconds of time. It also lags to turn it off, there is something weird about the queue.
Is everything being stored on the queue and then read FIFO? If that is the case then i need to dump that, the system sits idle for ~45minutes between trigger events.
06-13-2018 09:13 AM
You need to start think about data flow.
In your first case with the event structure, the top loop would run then WAIT at the Event Structure until an event occurred. Now the loop is running every ~1ms, which means sending data to the queue. I imagine your queue is becoming backlogged.
Try the following modification that is attached, check for errors, I have a meeting and rushed this together.
mcduff