08-17-2007 05:03 AM
08-17-2007 05:20 AM - edited 08-17-2007 05:20 AM
Message Edited by TonP on 08-17-2007 12:20 PM
08-17-2007 06:39 AM
Thanks Ton,
this will work - but only if you don't have a folder called "u" on your crio (which is created if you try to access the u:\ drive without a USB drive attached).
So my problem is - if somebody disconnects the drive while the logger is running, it will create this folder and then not be able to detect a missing drive anymore at the next startup.
Regards,
Stefan
08-17-2007 06:43 AM - edited 08-17-2007 06:43 AM
I just found out one more thing:
What Ton proposes works on a Windows Machine - on the VxWorks cRIO controller listing the folders of the Root will list the folders of the Root of the flash drive - which is drive c:\!
So this will not work on the cRIO controller. Any other ideas?
Stefan
Message Edited by StGl on 08-17-2007 01:45 PM
08-17-2007 06:55 AM
08-17-2007 07:36 AM
@StGl wrote:
I just found out one more thing:
What Ton proposes works on a Windows Machine - on the VxWorks cRIO controller listing the folders of the Root will list the folders of the Root of the flash drive - which is drive c:\!
So this will not work on the cRIO controller. Any other ideas?
Stefan
Message Edited by StGl on 08-17-2007 01:45 PM
08-17-2007 09:01 AM - edited 08-17-2007 09:01 AM
Hi Ton,
I used exactly the code you posted - on a Windows machine it outputs an array of drive letters (C,D,E etc.), but on the VxWorks controller, it outputs the root of the flash disk (ni-rt, temp etc.). I guess that's due to the fact that in VxWorks there is no such filesystem root in front of all drives as in Windows ("My Computer"...).
However, trying to get the drive info for the U:\ drive fails if you don't have an U:\ drive - also on VxWorks; so that's a good solution for my initial problem.
Regards,
Stefan
Message Edited by StGl on 08-17-2007 04:02 PM