Buddy Curtis

I have a RT project on a cRIO that will be using a Class. In this class are several VIs that are Loops (only end when the RT shuts down). Each loop gets its own branch/instance of the LV Class. My idea was to pass some lossy data between some of the loops. I don't really need a producer/consumer and there are several consumers anyways such as the UI loop and a control loop. I am okay with the inherent jitter that using FGV globals would cause. However during testing I noticed some weird behavior which makes me question the architecture. How sound is the method of passing data in an EXE from separate VI Loops with Classes. I can create RT FIFOs for every producer/consumer combo if FGVs arent the way to go but it would greatly increase the complexity. A colleague questione the idea of even passing data via FGV with dynamically launched VIs but I tested on my test computer. However, Development namespace and EXE namespace are different. LabVIEW dev will load everything into memory. The specific behavior is that sometimes the VI wouldn't update but then when I started to debug the RT system like loaded the FGV and watching it, it started working. Sometimes breakpointing would make it start to work. I simplified the structure in a Test VI and got the same behavior sometimes it worked and sometimes not. If I placed the FGV in the same VI removing the subVIs that it seemed to always pass the data