wireless communication sparatic/dangerous

[Greg McKaskle]

On the other issues.

Sorry for using the acronym -- DS. That stands for driver station. People also use it to refer to the computer and HW elements that the driver station application runs on.

The default NI code had game autonomous added to it at the last minute, and the digital inputs for the IR sensors are used in autonomous independent VI, but are not opened and stored in Begin. If the errors refer to that, you can correct it by opening and storing using the same names. An update will be released shortly to fix some issues not found in WPILib and in in the framework template code.

As for how to check the CPU usage on VXWorks if not running LV -- you can use the netConsole or serial connection via null-modem cable and look at the commands at this URL http://touro.ligo-la.caltech.edu/~cp..._commands.html. I don't have the WindRiver tools with me, but it may be that "i" gives you the info I was thinking of. If not, ask on the WindRiver forum or google a bit.

Greg McKaskle

Greg McKaskle

[Coach#3536]

My one issue with switching to 5 MHz is that the classmate does not communicate with any above 2.5 MHz so that in itself is an issue.

The 1 light flickers constantly while the power light is on a strong. The AP light is a steady 1 second flash.

I completely removed the Labview from my laptop today and installed it again in hopes to have clean code. I also reformmated the the cRio as well as the D-link.

Not to be a downer but this is getting a little tough on a rookie team. Every coach I have talked to locally appears not to be writting code or deep in this. And the kids are busy writting thier robot code right now. This is not what I expected.

[Greg McKaskle]

Have the symptoms changed in any way? If you turn on the robot and DS and leave the robot disabled, what happens? Be sure to pay attention to the LEDs on the router and cRIO as sometimes a reboot or power outage can appear to be a comms issue.

Post back with the latest observations and consider phoning the NI support number.

Greg McKaskle

[Mark McLeod]

The sporadic response may be a symptom of longer transmit times.
The D-Link status lights sound correct.

Rather than being broken, the wireless might just be adding more delay to the communication between the Driver Station and the cRIO and tripping the Safety for longer periods than the wired operation.
The wired operation may be surer and quicker.

So you might be suffering more from those error 44061's that you're also seeing, than from flakey wireless.

To explore that possibility, lets disable that error as a debug step.
In LabVIEW:

• Go to the Begin.vi block diagram (picture 1 below)
• Double-click on the Drive Open 2 Motor icon and then open the block digram for that
• In the middle you'll see "enabled" feeding a Sfety vi icon
• Change that to "disabled" (picture 2 below)
• Build and Run as startup (if you haven't done this we can walk you through it)
• See how the robot behaves both wired and wireless

As you test the wireless, with sporadic dropouts, watch the Driver Station Diagnostic tab, in addition to what Greg told you to watch. Tell us about any red lights.

[mbone206]

Did you get this working, I have same problem... Connected from driver station to bridge, bridge to crio -- then OK..

Set lap top ip to 10.2.23.5, sub net same as bridge, 255.0.0.0

Does Gateway need to be set? set it to 10.2.23.4....???

One thing, setting up bride, asked for Pre-shae key, put what was in instructions, change team name: 0223WPAKEY -- not sure if leading '0' needed

we are still not communicating wireless, appreciate support

[Alan Anderson]

Originally Posted by mbone206

Does Gateway need to be set? set it to 10.2.23.4....???

The Default Gateway for your PC should be the address of the D-Link Access Point (10.2.23.1). Since the subnet mask puts the cRIO (10.2.23.2) on the same subnet, however, the Default Gateway will not matter.

One thing, setting up bride, asked for Pre-shae key, put what was in instructions, change team name: 0223WPAKEY -- not sure if leading '0' needed

Your SSID should be set to "223" with no leading zero. If you are using wireless security, the key can be whatever you want it to be, as long as you enter that key on every device that needs to connect to the DAP.

And just to make sure everyone is on the same page, I'm referring to pages 6-9 of the How to Configure Your Radio guide. The DAP-1522 will be put in Access Point mode, not in Bridge mode.

[mbone206]

tahnk you Alan, will try taking out leading '0' tonight

[Coach#3536]

UPDATE!!

Just found out the issue is in our classmate!

The wireless in our teams classmate has a huge latency in the communication with the router from the wireless card. I spent a total of about 30 hours fighting this thing and here is what I got. Our new classmate....Rookies only....PINGS from 100ms to 1623ms....Opened it up and the wire on the antenna is connected well. Per request of CTL tech, I loaded the new driver in it from CTLcorp FTP and the issue still occurs.

I loaded the driver station into my VIAO and I had a 1ms to 2ms PING return.

So here is the bad news. If you PING the router and have this kind of response the issue may be in the classmate itself. Mine will be going back to CTL for review/repair.

I suggest if you are having this issue Ping the router and check your return rates. If you have the slow speeds you need to load the driver station onto a separate laptop and check if you have the same condition. Hope this helps before pulling anymore hair out.