04-29-2009 04:36 AM
I've been developing a new application with labview and any time I try to probe it, the error -142016 appears. Does anyone know what it refers to? Or at least, any clue to solve it. Thanks for all.
Here is more information, (although I don`t know if it's useful). The nxt -laptop are paired and connected; problems appear in any .vi related with bluetooth.
Solved! Go to Solution.
04-29-2009 12:01 PM
04-30-2009 01:45 AM
Thanks , James, for answering so fast.
For the first question: When I connect NXT to laptop, the bluetooth serial port is the one numbered COM11, and when the connection is in the other way, the serial port is COM17. I don't really know if you are asking for these. If not, tell me how can I search for the information of the connection between NXT driver and NXT's Bluetooth "channel".
Answering the second question I have to say that I don't Create NXT vi, I use the Scan for NXT and then, as I only using one, the obtained string is the one I use as resource string for the rest.
04-30-2009 10:34 AM
Yes, those are the serial ports I was asking about. If a virtual serial port doesn't exist, Fantom (the NXT driver) won't be able to connect to the NXT. So it's good that you have that information.
If you're trying to connect to an NXT, you must be calling CreateNXT somewhere. Please look through your block diagram again and determine the name of the VI that you're using to open a connection to the NXT. Also, can you probe the resource string at various points on your block diagram while the VI is running, and post the value(s) here? A screenshot of your VI would also be helpful.
05-07-2009 02:08 AM
Thanks James.
As I previous said, the vi that I use, scanNXT finds all NXT devices, and gives its resource string. Having it, I connect to createNXT.vi, and then, the rest.
As your suggest, I probe the resource string on my blocks, but as the first scanNXT fails, the rest are empty.
In the following reply, I will put the screenshot.( I'm not able,yet)
05-07-2009 02:14 AM
05-07-2009 11:35 AM
Ah, so the Scan NXTs VI is the one that is returning an error code in this case. Sometimes when the Bluetooth driver creates the virtual serial ports, it doesn't properly register them in the system registry. As far as I know, nobody has been able to pin this problem down, but several people have seen it at random times. The workaround that seems to work the best is to delete the pairing from the operating system and the NXT, reboot both, and try again.
I'm sorry I don't have a better explanation to offer.
05-08-2009 12:11 AM
Thanks James.
You are right. I don't know the reason but it works.
05-08-2009 06:09 AM
Hello James and everyone!
Perhaps you can help me again. Solving the previous problem in the same vi, appears the error -142024 in createNXT. This means that the connection to NXT can't be done. I think that this is not the real problem, because, it, previously, scans correctly. Could you give me any suggestion? Thanks for everything.
05-08-2009 10:26 AM
Hmm... the more we talk about this, the more it sounds like a problem I've heard before. A few searches didn't turn up the exact topic and description I was thinking of, but I did find a good description of how someone else resolved this problem.
Good luck!