Is there a way to get a IO Variable that is hosted on a RT target and bound to a localhost Variable to log in Citadel?
As per the video, the Variable stops logging when it is bound and starts logging when it is not.
(Note: the localhost Variable it is bound to a Variable on the RT which acts as an interface for that target. That variable is actually bound to an IO Variable, this was a design decision so that the target could be reconfigured whilst maintaining an interface).
The current value is always displayed in the DSM though.
I can't find the link at the moment but I remember reading an NI KB that said Enable Timestamp has to be ticked.which it is, but its not working.
(It is greyed out because of the above - it is bound to an IO Variable).
One thing you might keep in mind is that when you bind a PC hosted NSV to a cRIO NSV you will inherit the timestamp of the cRIO. Unless you are running 1588 PTP then the cRIO system time will most likely not be sync'd to the PC clock. The DSM x axis is driven by the windows system time and if your incoming data has timestamp outside of the x axis window then you will not see it on the historical chart.
One thing you might keep in mind is that when you bind a PC hosted NSV to a cRIO NSV you will inherit the timestamp of the cRIO. Unless you are running 1588 PTP then the cRIO system time will most likely not be sync'd to the PC clock. The DSM x axis is driven by the windows system time and if your incoming data has timestamp outside of the x axis window then you will not see it on the historical chart.
Another thing to check is that the NSV logging properties for Value Resolution and Value Deadband are set to 0 or a low enough to capture your data changes. Just for reference, I am doing the same thing as you except I am bound to a NSV on the cRIO which in turn is derived from an IO variable. I use citadel logging and it has worked flawlessly 24/7 for the past year.
