02-15-2010 02:52 PM
I have a WLS-9163 device. I ran through the initial set up stage, and set a static IP for the wired config, and chose a DHCP for the wireless. WHen I plug in the device, after some time both the wired and wireless connect. I then disconnect the LAN line, and the wireless stays connected. Now, if I power cycle the device, it will not boot up with the wireless connection. I cannot see it in MAX and the WLS LINK light never comes on. The only way to get it to be wireless is to connect through a LAN again and reset it that way. Why can't this wireless device boot up wirelessly?
Thanks,
herm
02-16-2010 04:31 PM
Hello Herm,
So did you follow the steps outlined in the NI 9163 Web Configuration Help File? Also, what module are you using in the 9163, and when you say power cycle the device are you referring to rebooting the computer or just powering down the 9163? Do you set it to obtain an IP address automatically?
Regards,
02-18-2010 04:07 PM
Hi Brandon,
I did follow the steps listed in the Web Configuration Help File (with the exception that I did it through MAX, not a web browser page). I am using module NI 9234 in the device. I set the wireless IP address to obtain automatically, and when I shut off the device and power it back up, it will not start in wireless or find any wireless AP. I cannot see the device unless I plug it in with a Cat5 cable. I wonder why the device wont start up in wireless mode?
Thanks,
Herm
02-26-2010 01:25 PM
Hi there,
I am having the same issue. I am using a WLS9163 with a digital IO card. I configured the 9163 thorugh MAX to use a wired DHCP server and a static wireless address with a WPA-PSK key with a password. I have been able to connect normally (the wls link light is on) and unplug the ethernet cable and self test so I know its working on wireless. When I reboot the 9163 using the reboot button in MAX the wireless signal eventually returns (after about 1 min) no major issue there. But when I power off the 9163 and power it back on the wireless does not return. After I plug in the ethernet cable again the wireless only seems to reappear if i Save the settings to the device again via MAX. Was thinking this may be something to do with the persistence of the password, but not really sure.
For my application this issue renders the device fairly useless so any idea how to fix it will be much appreciated!!!
Dinnoc
03-01-2010 04:06 PM
Hello Herm,
So what version of the DAQmx driver are you using, and what version of the 9163 firmware do you have (click the "Update Firmware" button in MAX to see this)? Take a look at the accepted solution in this forum post for information on how to upgrade the firmware if necessary. I hope this helps and please let me know if you are still experiencing problems.
Regards,
03-02-2010 02:27 AM
Hi there. I upgraded the firm ware and everything seems to be working fine now. For information I was talking about powering off the WLS-9163 when i was talking about power cycle and the unit I am using is the NI9421.
One question, why does the latest model not ship with the most up to date firmware? I only had this delivered this week but the post regarding updating firm ware is over a year old?
Cheers
James
03-03-2010 05:02 PM
Hello James,
I'm not sure why the firmware on your 9163 wasn't updated, but I have brought this to the attention of our R&D department. I'm sure they will look into this to determine what could've happened, but the good thing is that your device is now working properly.
Regards,
03-10-2010 03:01 PM
I am still experiencing the same problems. I have DAQmx version 8.9.5 and the 9163 device has the firmware 1.1.0f2. My device will work wirelessly if I connect through the LAN cable and then unplug it. But, if I unplug the device power and then plug it back in, the wireless mode never boots up. It just sits there. Any other advice? Does my AP need to have a certain setting applied? (I am using a Cisco Aironet 350 series Wireless Bridge).
Like Dinnoc, the device is useless unless I can reboot in wireless mode.
Thanks,
Herm
04-30-2010 04:18 PM
Hello Herm,
Are you still experiencing this problem? I'm not too sure about the settings, but I could take a look into that. In the meantime, would you mind updating to the latest DAQmx driver so that we can make sure you are up to date.
Thanks,