Troubleshooting FMS Lite

[popo308]

So, working with FMS lite - (http://www.usfirst.org/roboticsprogr....aspx?id=14532) downloaded here.

I have the FMS computer's IP set to 10.0.0.6 subnet of 255.0.0.0
The field router set to 10.0.0.4 subnet of 255.0.0.0
Then just a normal classmate setup to run with the standard team ip of 10.xx.yy.5
Both the cRIO and DS are running the latest software updates.

My problem comes when getting the FMS to recognize the teams classmate and cRIO. The classmate has all 3 green lights on the left and can be enabled in teleop and auton, but the FMS just wont find the cRIO and classmate and take control of them. Under diagnostics on the classmate I have green lights on: Enet Link, DS Radio, Bridge, and Robot. The FMS light is not on. I have tried 3 different FMS computers all with the same results.

On the FMS computer I can also ping the cRIO, robot bridge, and classmate

Can someone tell me what i'm doing wrong perhaps?

Any input would be greatly appreciated, and as always... Thank in advance!

[Mark McLeod]

Team number entered on the FMS screen?

I assume the FMS computer, Classmate and field router are all connected by Ethernet cable, and just the DLink-to-field router are wireless in your setup?

[popo308]

yes I have the team number entered in the FMS. I have the classmate and FMS connected via LAN and the cRIO corrected via the DLink wireless

Now I have the FMS detecting everything properly, but when I enable the field the FMS program crashes...
Has anyone else had similar problems?

[Mark McLeod]

What did you have to do to get FMS to recognize the Driver Station?
All I could think of was if the Driver Station user login wasn't "Driver".

What OS is FMS dying on?

What FMS button(s) and settings did you use in the process of enabling it?
Does it abort immediately or run a bit before the abort?
Does the Status screen show anything unusual?

With the defaults, a full match completely runs by just clicking the Start under Auto. No other buttons need to be clicked.

[linuxboy]

Originally Posted by Mark McLeod

What did you have to do to get FMS to recognize the Driver Station?
All I could think of was if the Driver Station user login wasn't "Driver".

Make sure there aren't two accounts logged in on the Driver Station (Driver and Developer) because having two logged in can screw things up

[popo308]

Originally Posted by Mark McLeod

What did you have to do to get FMS to recognize the Driver Station?
All I could think of was if the Driver Station user login wasn't "Driver".

The reason why it wouldn't recognize the DS was because it was running under developer. It recognizes it fine now that the DS is in the Driver account.

Originally Posted by Mark McLeod

What OS is FMS dying on?

What FMS button(s) and settings did you use in the process of enabling it?
Does it abort immediately or run a bit before the abort?
Does the Status screen show anything unusual?

With the defaults, a full match completely runs by just clicking the Start under Auto. No other buttons need to be clicked.

I have tried the FMS on Win XP (service pack 2) and Win 7 (service pack 1) both have .NET 3.5 installed. Since I am testing with one DS currently I put in the team number in to blue 1 and bypass the remaining slots (blue and red). Then I simply hit Start underneath the auton time setting. After doing this the program freezes and a windows crash report appears saying FMS has crashed. All computers I have run FMS on have had the same end result.

Another quick question, should the 2009 FMS work with the 2011 robots? I can't get the FMS from 09 to recognize any of the Driver Stations but the 2010 one picks them right up... just crashed unfortunately...

Thanks

[Mark McLeod]

.NET 3.5 SP1?

Originally Posted by popo308

...should the 2009 FMS work with the 2011 robots? I can't get the FMS from 09 to recognize any of the Driver Stations but the 2010 one picks them right up... just crashed unfortunately...

FMS Light only comes in the 2009 version, the one you linked to in your original post. It (normally) works fine with later year robots, including 2011. So if it's not connecting then there are other problems (Firewall off?). Being from 2009 it probably needs XP and might not run under Windows 7, but I haven't tested that-maybe later.

There is a hybrid version released in 2010 called FMS Delta that has additional system requirements and will crash like you describe fresh out of the installer without SQL Server 2008 Express. I wouldn't use Delta, it assumes the full field server setup and the complexity goes way up. Could that be the one you are talking about? It's available via a wiki site.

There were also some unreleased intermediate versions judging from mismatches with the corresponding User Guide.

Do you have links to the different versions you've tried, so we can check them out?

Originally Posted by linuxboy

Make sure there aren't two accounts logged in on the Driver Station (Driver and Developer) because having two logged in can screw things up

I've never had problems and usually have both user accounts logged in at the same time so I can monitor some things. Having the Driver Station and Dashboard running in both WILL screw it up though. Not seriously, but only one will win and it'll probably be the one you don't want.

[Mark McLeod]

I just installed onto a Windows 7 PC using your original FMS Light link.

I had the problem you told about where the Driver Station sees and obeys FMS, but FMS doesn't acknowledge the DS.

I noticed that FMS seemed to pull down some updates while it was installing, so I uninstalled FMS, disabled my Internet connection, and reinstalled.
Then FMS worked fine. It probably wasn't the updates, but was just uninstalling/reinstalling.

Without more investigation I wouldn't say what the trouble could have been, but it does work under Windows 7.