04-17-2018 12:01 PM
I have a write to measurement file that collects data from a "set dynamic data attributes". The problem is that it doesn't update all the signal name but only the last in the iteration. I really do not want to use a shift register to correct this problem as the shift register causes an error "2553" after a long period of data collection, along with stopping problems.
I have attached the section of the VI so you can see what i am talking about. Again, I would appreciate a fix that doesn't involve the shift register. Note also, all other parts of the code are functioning correctly.
Solved! Go to Solution.
04-17-2018 01:25 PM - edited 04-17-2018 01:25 PM
What is the exact error you get when using the shift registers ? How do you determine that it comes from the shift registers ? Because I looked up the description of error 2553 and it is more likely to me that this error is related to writing to your file.
Everything works just fine with shift registers on my computer.
04-17-2018 01:30 PM
The issue is that for every iteration of the for loop, it passes the original combined signal (with no names). So all you get is the last iteration. Have you tried setting the attributes of the individual waveforms prior to merging them using the Set Waveform Attribute vi?
04-17-2018 01:36 PM
Or you can try the VIs located here : C:\Program Files (x86)\National Instruments\LabVIEW XXXX\vi.lib\express\express shared\transition.llb. They are shipped with LabVIEW but are not on the palette. Yet they should be stable.
Solution originally from LAVA.
04-17-2018 02:29 PM
Thanks ML927. The error does come from the write to measurement file but originates from the shift register. When i replace the shift register to tunnel, the error does not occur. In addition, when i stop the while loop, with the tunnel, the stop is activated immediately, while with the shift register, it can take up to 20 mins.
I'll like to mention that both problems arise when data is being collected for an extended period of time ( 2 hours + ). For this reason, i'll like a fix that does not involve the shift register.
04-17-2018 02:35 PM
Are you streaming all the data (for 2 hours +) and then writing it all to the measurement file at the very end?
04-17-2018 02:47 PM - edited 04-17-2018 02:55 PM
I understand that and yet I have no clue about what could be causing the problem... Sounds weirds to me that the shift registers might be the cause, but well... Instead of changing the name in the while loop, have you tried to edit your TDM file to change the channel name after you are done acquiring data ?
04-17-2018 02:48 PM
04-17-2018 02:56 PM
If you let the "test problem.vi" run for a long time with shift register, do you see the same behavior? or only in your original?
04-17-2018 03:00 PM
Hi jbledlow ,
I have not run the test data for an extended period, but since the shift register does not work for my code, i do not think there will be much point pursuing that for the test data.