"error... occurred at createNXT.vi:2"

[NXTenergy]

Sorry if this is repetitive, but I haven't been able to hunt down an answer:

I am using the NXT toolkit and it's working great, but for one thing; any direct connect code I write, even the simplest program, gives me an error after running for a short time. I am sticking with USB because I want it stable, but it consistently returns this error:

 

"Error -1073807194 occurred at createNXT.vi:2

Possible reason(s):

VISA: (Hex 0xBFFF00A6) The connection for the given session has been lost.

or

VISA: (Hex 0xBFFF003C) Insufficient system resources to perform necessary memory allocation."

Labview will then give me

"Internal computer driver error.
- Retry the current operation.

- Restart LabVIEW and try again."

So I obey and restart, and everything is good again...till I go back to direct connect commands.

Any help would be great.

Thanks,

Jake

[Nli]

This sounds like a known bug. Which version of the toolkit are you using?

[NXTenergy]

I am using the most recent toolkit (2.0 I believe) along with NXT firmware version 1.26.

[Nli]

Thanks! The current workaround is what you described: restart LV. We'll try to address it in the next release.

[NXTenergy]

there must be a reason...

since this error happens every time without fail I can't really operate anything effectively (hardly a workaround). if I revert to an older version of the toolkit to use the direct commands perhaps that will prove a more effective "workaround"?

thanks for your fast response tho 🙂

[Nli]

So it used to work just fine in 1.0?

If so this is something new. I've thought this bug was there since 1.0, and on my windows XP machine, I've seen it happen after about 10 minutes of direct mode operation, and not always. I'll post you if we find anything or a better workaround.

[NXTenergy]

no, I don't know for sure if it breaks in 1.0 . I too am using XP (SP3 w/ LV 8.6.1) but in 2.0 it breaks after what I'd say was 30-45 seconds on average--without fail. Ah well.