Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Path to String function oddity

OK, maybe I'm missing something simple here or just don't understand something basic about RT paths, but this seems a bit strange to me.
 
If I run the code shown below, the string created by the Path to String function does not match the input path to the function.
 
 
 
Is this expected or is something going on that shouldn't be?
 
This is running on a cRIO-9012, LV 8.2.1, LVRT 8.2.1
 
Ed

Message Edited by Ed Dickens on 08-03-2007 09:24 AM



Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Download All
0 Kudos
Message 1 of 3
(4,817 Views)
Ed,
 
The reason for that is that the cRIO-9012 is running VxWorks as the underlying RTOS. For the LabVIEW RT user the differences between using a VxWorks and an ETS RT target are pretty minimal but there are a few difference. In order to keep the experience on VxWorks targets the same; Windows/ETS style paths are used in LabVIEW RT and under the hood they are converted to Unix paths. However, as you found the 'Path to String' and 'String to Path' primitives do not convert from Unix to Windows paths. Other difference can be found in KB 44HDTKQ0: "Frequently Asked Questions (FAQ) for NI cRIO-9012".
 
-JRA
0 Kudos
Message 2 of 3
(4,808 Views)
Thanks JR.
 
I was actually more surprised to see the Current VI's Path function return a Windows style path. I guess it's just something I never looked at before for some reason. But them it seemed if it returns a Windows path, it should stay a Windows path.
 
Ed


Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
0 Kudos
Message 3 of 3
(4,347 Views)