Using USER switches and LEDs on cDAQ chassis

[jordani]

I'm trying to access some system hardware properties on a cDaq-9133 chassis which is running Windows 7 Embedded Standard and Labview 2014. I have followed the examle found here: http://digital.ni.com/public.nsf/allkb/75E039282A8B691886257E450049C7B6 and I have also downloaded and ran the VI at the bottom of the article. Unfortunately, I am not able to access the propert. I receive the following error:

I haven't been able to find any solution to this problem searching the forums but I am suspicious that these properties may not be accessible when running on Windows.

[James.M]

Are you getting this error for all System Hardware references that get pulled? Your For loop is iterating through each device found, but the error output only the last value... so you might only be getting that error on the last device and not the one you care about.

Does your SwitchStates array have anything in it?

[Hooovahh]

I suspect James is right.  For a better approach you may want to create a filter so that only the devices you want are returned.  In this case only devices that are not simulated, and are made by NI will return the switch info.  But your filter will likely need to be even tighter because not all NI non-simulated devices can check the Switch States.

[jordani]

Thanks for the idea, I've tried this(on hardware) and I've found that the FOR loop never executes. It's as though the filter is too restrictive; have you got any other thoughts on this?

[jordani]

I've widened the filter criteria to select a chassis and this gives me one result. Although the documentation for the cDaq-9133 indicates that I should have access to the USER1 switch and the USER LEDs I receive the property does not exist error when I try to access the states. Has anybody had success using these proprties on a cDAQ running Windows?

[James.M]

I'm looking at the product page and I don't see any switches on this thing. Have you tried pulling the LED states?

[jordani]

If you zoom in on the front view, you'll see the button below the SD card cover. I have also tried to access the LED states without success.

[James.M]

---

@jordani wrote:

If you zoom in on the front view, you'll see the button below the SD card cover. I have also tried to access the LED states without success.

---

Ah, I was looking for actual switches and overlooked the button. My bad.

It's been a long time since I've worked with Windows Embedded on a cDAQ and I can't think of anything else to try here. Maybe Hooovahh has some other ideas. I would guess it's some sort of access issue with Windows.

[Hooovahh]

---

@jordani wrote:

I've widened the filter criteria to select a chassis and this gives me one result. Although the documentation for the cDaq-9133 indicates that I should have access to the USER1 switch and the USER LEDs I receive the property does not exist error when I try to access the states. Has anybody had success using these proprties on a cDAQ running Windows?

---

Yeah I guess you are right, you probably want to not apply any filter at all until you know your device is being seen.  Then when you know the type of device, you can setup a filter to find just that.

On the VI I showed it returns an array of errors out of the for loop.  Do any of the elements in that array return no error?  Or are they all returning an error?  If you find one that doesn't return an error then that maybe the device.  I may try simulating this device as a test, but these functions may not be implemented in the simulated hardware.

EDIT: Can't simulate the cDAQ-9133 in MAX.

[jordani]

So, I see that the resource with "ProdName" property = NI cDAQ-9133 has no error and lets me access the SwitchStates property. I'm still not able to access the LEDStates property and I can't find a filter that will work. Apparently "ProdName" is not available to filter on. Interestingly, if I filter with IsChassis, the cDAQ gets excluded. This seems broken to me.

I was able to simulate the cDAQ-9133 with no trouble on a development machine. The specific problem I'm having is actually on hardware though.