cannonpm Posted September 14, 2010 Share Posted September 14, 2010 I am using one LabJack U6, but have plans to add another possibly within a few months. Therefore, I assigned the LJ a unique local ID (I arbitrarily went with 7) in the LJ_ControlPanel. When I am setting up my channels in the DAQFactory, it asks for the DeviceNumber which is this local ID. If I leave it at the default (0 -- which means the first found LabJack) then all works fine. If I change it to the value of 7, it will intermittently work and not work. About 3/4 of the time I get an error from DAQFactory saying it cannot find Device #7. The other 1/4 of the time it will find it and all is well. I have tried using D# 6, thinking it is zero-based, but that did not work. If I change it back to 0, then all is fine. Any idea what may be happening? Thanks. Link to comment Share on other sites More sharing options...
AzeoTech Posted September 16, 2010 Share Posted September 16, 2010 I think you need to choose one or the other. Once you use 0, if you want to change it to 7 (or 6 or anything else), you need to make the changes, save the document, then restart. But, as I've said before, DAQFactory basically calls the LabJack UD directly with these parameters so the issue is in the UD, not DAQFactory, so perhaps the LabJack folks will have a comment. The only thing DAQFactory does is make 0 mean first found. Link to comment Share on other sites More sharing options...
LabJackSupport Posted September 16, 2010 Share Posted September 16, 2010 There shouldn't be an issue with using that number, as long as you are consistent. Something else to try might be using the serial number instead of the local ID. The LabJack UD does accept a serial number so you should be able to pass it in from DAQFactory. Link to comment Share on other sites More sharing options...
AzeoTech Posted September 16, 2010 Share Posted September 16, 2010 The number certainly isn't an issue. I believe, however, that once you open a device using first found, you can't then open it again using the direct ID. This creates two connections which conflict with each other. Only by restarting DAQFactory or loading a different document do you close the connection, so if you change from specifying 0 to specifying 7 you have to restart. Link to comment Share on other sites More sharing options...
cannonpm Posted September 18, 2010 Author Share Posted September 18, 2010 Thank you for the input. Using it, I found out what was causing the problem. When closing DF, I have to wait perhaps 5 seconds or so until the program completely closes out. If I tried to re-open it sooner than that, the old process still had exclusive control over the device at that local ID so the new process could not find it! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.