Crashes with more than one Color sensor block

[Pandas]

Problem Description :
when using two or more color sensor blocks Labview crashes.

When using only one color sensor block Labview works and does not crash.

We run Labview 2012 and are using an NXT color sensor.

Any idea anyone?

[HunterSeeker · Accepted solution]

NI R&D have confirmed this issue and it has been documented as CAR 436939 in our internal system.

For now here is a workaround that will allow you to work in the mean time.

Open the Color Sensor VI

      C:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\NXT\Remote Library\NXT Color Sensor\NXT_ColorSensor.vi

Go to File>VI Properties>Execution and turn off reentrant execution.

[Philbot]

Hi

Is there a list of these "Known errors" for LVLM somewhere were we can peruse it?

I'm chasing another "glitch" that I can't nail down the cause, but seeing a list of knon problems could help me not loose my mind

In my case having two single MoveMotors in the same vi is causing a file error crash on the NXT. 

Combining them into one dual MoveMotors works.  Doesn't seem like a reasonable limitation.

Phil.

[adityasm20]

hueter,

     I followed exactly what you said but for me the options are dimmed out and i am not able to access them. What should i do ??

[mathterizer]

I found where Hueter was pointing us to and nothing was greyed out for me:

Went to the directory specified and opened the Color Sensor VI.

Tools - Choose Environment - LabVIEW (native)

File - I was able to change the execution properties and checked the 'non-reentrant execution' bubble. Okay - it took. But, when it came to 'SAVE'...

The folder containing this VI is 'read only' - so to save it I would have to give myself 'permissions' to do so. Would it be better to create a copy of this VI with a slightly different name, and then store it in the project, and call out to it instead?

What would be the recommendation here?

(Note: regarding the 'greyed out' - I know that I had to manually activate my 'Full Development System' block in the LabVIEW Components tree by right clicking and 'activate' -ing it (from the Help menu). Could this have anything to do with it?)

[HunterSeeker]

This method is only a temporary work around, we plan to fix this in a future patch release. You can change the folder options to read/write, but I would recomend saving a copy with a new name. This will prevent any confusion if you move the code to another machine.

note: you will need to do the same on all computers you work on.