Datasockets on Mac OS X LabVIEW 8.0

[OomplexBOompound]

I have not been able to correctly use datasocket write using Mac OS X LabVIEW 8. I made a simple program that should write a dummy dsd file to my desktop, but after the program runs with no error thrown, there is no file on the desktop. I used file:// and then set the path to the desktop using colons as folder separators. Any idea why I'm getting no file written?

[TiTou]

hello,

nothing comes to my mind only from reading your post, having your code could help to point out the problem. Could you upload it ?

[OomplexBOompound]

Attached is my dummy dsd file.

[TiTou]

Sorry... only have LabVIEW 7.1.1... could save it as LV 7.1 or do a screen shot image ?

Thanks

[OomplexBOompound]

okay attached is the LabVIEW 7.1 file along with a screenshot if the 7.1 file doesn't work. Thanks!

[Travis_M.]

Hello,

Not too sure why you don't see an error -- but I think your going to want to open up your datasocket connection before writing to it (I get an error on my PC with your VI).  See the attached example -- this one works just fine with string data on my machine.  Keep us posted on how it goes....

[OomplexBOompound]

OK.... I don't have the DataSocket Select URL vi. Not really sure why not. Does the Mac OS X install not come with this file? Anyways, I don't know if that's the problem, but when I simply type the file destination in a string and wire that in there, the same thing as before happens (no error thrown, but no file exists where I expected). Also I noticed that if I don't specify a file name at all, LabVIEW itself crashes.

[Travis_M.]

Hello,

I apologize, but since I'm away from my desk today I don't have a Mac to test this on.... Maybe you and other community members with Mac machines could try out this example (it’s the same one without the missing VI) and let me know if this one works.  I was unable to get a crash without the URL wired, but this could possibly be a bug that we can look into. 

Another thing that I've failed to ask here is why you wish to write a file with Datasocket.  There are some applications I can think of, but this is a pretty uncommon way to write a file.  If there’s an easier way to achieve your goal I'd be happy to help with that too.

Let me know if this helps --

Message Edited by Travis M. on 02-24-2006 03:46 PM

[OomplexBOompound]

Well, I am using datasocket files because we have a machine posting data to a server and updating the data while I am taking in the data and analyzing it remotely.


Using this new VI, it still doesn't work, and in much the same way that it didn't work before. Here's a summary of what's going on:

1. For the string specifying where the datasocket file will be saved, you have it set to save as a txt file. When I try to use this code, but change it to save on my desktop, I get error code 1179 Possible reason(s):
LabVIEW: Access mode not supported for operation.

2. I changed the filetype from txt to dsd, and once again I experience the same problem that I was having from the start: specifically, no error is thrown and the program seems to run fine, but I look on the desktop and there is no file there.

3. If I leave the filepath and filename string blank, LabVIEW crashes.

Thanks for all your help,
Santiago

[Travis_M.]

Good afternoon Santiago,

I was able to reproduce some of the behavior on a Mac OSX machine with LabVIEW 7.1, and suspect that running it on an 8 machine will do the same (I have reserved some time on it tomorrow).  I noticed that when the file is one that doesn’t exist there is no error, and no file generated.  When the file already exists there is no error, but the existing file is not updated.  I was only able to get it to run without error by changing the Datasocket Open mode to “Write” in “read write” it gives an error.  It is likely that we will need to find another way to write information to the file without using Datasocket.

My understanding is that you have a machine which is gathering data and publishing it to a shared network file.  Is this Mac the reader or the publisher of the data?  I guess this is less important since the Mac needs to write data to a file in either case.  Perhaps, though, you could provide a little more clarification on why this must be done with Datasockets and not the file IO VIs.

I look forward to hearing back from you – let me know if you can clarify any of the points above, or have any new information for us.

Thanks for posting to the Discussion  Forums, have a great day!