I was working on it on Friday and as far as I noticed it had been working fine. I went home for the weekend and came back on Monday and this started to happen.
I can assure you that nothing as far as hardware goes has changed.
Since Friday, there has been a couple updates to the software. I was trying to build an installer to include my application to run on computer without LabVIEW installed. I had to download and install NI-488.2 2.8.1 and NI-XNET 1.3 runtime engines to include them in the installer. I believe the previous versions were NI-488.2 2.7.3 and NI-XNET 1.1.1, but I can't remember for sure.
The only other things that have changes are adjusting constant values within my LabVIEW program. All of which define wait periods, the CAN frame, the CAN port, some TDMS property values, and a VISA address, etc. Earlier in the week, I was having issues with my subVI's communicating properly and so created the entire program without subVI's and it ran perfectly. Then I re-createed my subVI's in a way that worked better for my program. Again everything worked perfectly.
One thing I'd like to point out that I was thinking about today is that my program requires that I hold a button for a specified amount of time and when I left the CAN.TxTime at its default it wouldn't work because the CAN device would see the signal disappear and then reappear. So I have a property node that sets all my signals to these values:
CAN.TimingType = Cyclic Data
CAN.TxTime = 0.001
I think that it might be possible that the TxTime is too high and the device can't keep up, but if I lower it to half that I run into difficulty holding the button again.
If there is anymore information that you need let me know, I appreciate the help.
Also, do you (or anyone) have any thoughts on how I could set up some sort of feedback loop to ensure all data was transfered correctly?
