cDAQ-9191 with 9237 module

[Pilebuck]

A newly purchased cDAQ-9191 unit will not maintain communications with the 9237 module! 

Initial wireless configuration of the DAQ-9191 will establish driver communications with the 9237 Mod1 after a 'self test' and maintain communications as long as the laptop is operating. The required environment is a wireless AdHoc network between a laptop running MAX and the cDAQ-9191. When the laptop is shut down, the communications is lost (module has red "x") and must be reset in MAX at the next test location. 

Is there any option to 'save' the configuration so that is does NOT require getting into MAX to reset the configuration each and every time? Our user community is NOT familiar with MAX and this was not a problem with the 9163 carrier (now being phased out) and 9237 module. 

[Tom_W_[DE]]

Hi Pilebuck:

I think you're probably running into an issue like the one I describe here:  http://forums.ni.com/t5/Multifunction-DAQ/Can-t-communicate-with-DAQ-until-after-Self-Test/m-p/18127...

I might offer a couple of suggestions:

You can programmatically Device Reset or Self Test the chassis at its assigned DAQmx Device Name.  This avoids the need for your users to visit MAX to make that operation.

You could choose a static IP addressing scheme instead of link-local with ad-hoc.  This will make it more likely that the host and chassis are routable to each other quickly after the system boots.  This may increase the odds that the host will automatically re-establish Reservation with the chassis as it loads the DAQmx driver for the chassis during boot.

Hopefully this helps-

[Pilebuck]

THANK YOU Tom! I would like to try your first suggestion to "programmatically Device Reset or Self Test the chassis". Is there documentation on the NI support site that can guide me through the process?   

[Tom_W_[DE]]

Hey Pilebuck-

It should be simple, actually.  I'm not sure if you are using LabVIEW or some other environment, but each of the DAQmx APIs has an entrypoint for both DAQmx Reset Device and DAQmx Self Test.

If you are in LabVIEW you can find these on the DAQmx Advanced palette or by searching in LabVIEW.  For the various C/C++/.NET APIs, I would recommend searching for 'SelfTest' or 'ResetDevice' in the appropriate API documentation.

Let me know if you need more clarification on how to approach this.