01-11-2008 10:35 AM
01-18-2008 08:25 AM
I had the same problem, so here's what I did:
Download the LabVIEW 8.5 NXT toolkit patch to your computer. I put it on my desktop. Browse in the patch to the Labview 8.5 folder. Keep opening folders after the Labview 8.5 folder until you get to the first one with more than one folder in it. You'll have to forgive me, I'm at a different computer right now and cannot be more specific. I think you get down to the "addons" folder. There will be about three folders in there. Copy and paste them into your NXTToolkit folder on your harddrive which I think is at: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\NXTToolkit. I think I then had to mass compile the thing again using the instructions found in the Getting Started Document for the Labview 8.5 toolkit. After that, it worked!
Good Luck!
01-22-2008 08:06 AM
01-22-2008 10:26 AM
01-23-2008 12:59 AM
02-02-2008 03:45 PM
05-15-2008 05:16 AM
05-15-2008 10:21 AM
Hi janus,
@janus wrote:On 18 januari John Smith suggest to download the LV8.5 NXT toolkit patch, to solve the 1003 invoke node error.Can anyone tell me where i can find/download this patch?Thanx for your time, Jos
05-21-2008 02:40 AM
hi...
i make a VI, using the ultrasonic sensor and the movement of the motor, connecting the distance output of the us sensor to the power of the motor, the VI works well in the nxt, but when i compiled the vi, it tooks at least 15 minutes...and this warning appears:
The shared library expected to be at "NXTInputOutput.dll" was loaded from "C:\Archivos de programa\National Instruments\LabVIEW 8.5\vi.lib\addons\NXTToolkit\shared\NXTInputOutput\NXTInputOutput.dll".
its normal that the compile process last that long?
thanks
05-21-2008 08:44 AM
h...but when i compiled the vi, it tooks at least 15 minutes...and this warning appears:
The shared library expected to be at "NXTInputOutput.dll" was loaded from "C:\Archivos de programa\National Instruments\LabVIEW 8.5\vi.lib\addons\NXTToolkit\shared\NXTInputOutput\NXTInputOutput.dll".
its normal that the compile process last that long?