FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Our team has been trying to debug a strange autonomous issue which only appeared to occur during some recent matches. In particular, at chezychamps, our autonomous would just sit there, but would work splendidly off the field (and also at the regular competitions).

To wit, I've been trying to help the team get rudimentary chezy-arena running.
We've found the most helpful thread at https://www.chiefdelphi.com/forums/s...light=fms+lite - and our IP setup mirrors that discussion.

We're having some trouble getting the Dlink (configured as fms-lite) to bridge - but I think we will get through that.

In the meantime, I would like to ask somebody to confirm that if we choose to configure the rio as static IP (say at 10.TE.AM.9) and the driver station as static IP (10.TE.AM.6), cheezy-arena machine as static IP (10.0.100.5) and connect them all through a switch (no Dlink), we would expect to see something other than grey displayed in the match_play under the DS/R/B tabs, and be able to start a match with only 1 team (ours) once we bypass the other 5.

Am I missing something here?

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

(I am not a mod, but...) Your original post was likely deleted because

1. It's been submitted by what appears to be an anonymous account solely for the purpose of this thread, which is against the forum rules (there are other threads around if you want to debate this)
2. It's posted without citation, and I don't know that I've seen people express that opinion before about the FMS, even though it does have flaws.
3. It adds nothing to the discussion and doesn't help the user asking the question, and will only serve to distract from the discussion and questions that Mark has about why his software did not run as expected.

As our discussion is only further distracting from the original intent of this post, please PM if you want to talk to me further about this.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Quick question - were your autonomous issues somehow related to the e-stop bug we had intermittently?

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Your post was deleted because you're anonymously taking pot shots at people and not offering anything useful or constructive to the dialogue.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Also, Mark, please post some screenshots of your DS Log graph during failure matches.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Reply sent via PM

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

One of the most common issues when setting static IPs is not having the subnet mask configured correctly. How do you have that configured right now?

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Let me start by helping correct a couple issues I see with your setup.
When using a static IP on the DS, always use 10.TE.AM.5 with a subnet mask of 255.0.0.0.

The static address for the RoboRio should be 10.TE.AM.2 with a subnet mask of 255.255.255.0.

The FMS (FMS Lite/Cheesy Arena) should also always be at 10.0.100.5.

Here is the slightly tricky part. If you intend to use the security settings in CA, you really should be using the hardware they have called out.
That said, I believe it might still be possible to use CA without it, but don't quote me on that.
To flash the robot radio to use a specific SSID and WPA, you can use the Radio imaging tool from the KOP, but make sure to use it in "FMS Lite" mode.

I hope this helps a bit.
BTW, I wish you had asked for help at Chezy Champs, I was FTAA there.

Can you provide so more detail as to what exactly your Auto routine does and how you had your components configured? (IP's etc.)

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

A more clear answer (in the interest of transparency): You just got disabled for trolling. Feel free to return with your normal account (unlike this one, which is clearly in violation of the forum rules), if you have something productive to contribute to the conversation.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Thank you for the helpful comments. I re-checked the settings this evening and I think the answer to my earlier question is likely 'confirmed, it should work'.

Some responses to questions asked in the thread:
1. We did indeed have Dlink related drops at the competition which looked, I think, like the 'e-stop bug'. The issues with autonomous were after this (once we replaced the flaky dlink) - thanks to the Qualcomm ref and also to Mike from 971 that helped identify that!

2. In response to billbo911 - FWIW - the Rio cannot be configured with a netmask of 255.255.255.0 if the IP is 10.TE.AM.2 and the GW is 10.0.100.1 - so I configured the netmask to 255.0.0.0, and the other settings per your post (.5 for the chezy-arena host and .5 for the DS).

3. As for the DS failure log during matches. One of our team might be able to dig this up from one of the laptops.

Note, again, that the Dlink is not in play in this setup. Everything is going through a single switch (DS, Rio and Chezy-champs), pending our resolution of the bridging problem with the Dlink.

So.. there is some progress this evening - I got the message on the DS saying 'begin FMS control'. However, when we click on this, the chezy-champs crashes per the below (chezy-champs running on a mac, leaving the GUI as attached):
http://imgur.com/a/lffFd

2016/10/03 21:35:00 Rejecting connection from Team 5026, who is not in the current match.
2016/10/03 21:35:02 Accepting connection from Team 5026 in station B1.
2016/10/03 21:35:02 Driver station for Team 5026 connected from 10.50.26.5
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4010f25]

goroutine 11 [running]:
panic(0x4620a00, 0xc42000c0d0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
main.ListenForDsUdpPackets()
/Users/pfairban/go/src/github.com/Team254/cheesy-arena/driver_station_connection.go:82 +0x2b5
created by main.main
/Users/pfairban/go/src/github.com/Team254/cheesy-arena/main.go:25 +0x9f
dhcp-157:cheesy-arena.v2016.1.0.osx xxx$ ./cheesy-arena.command
goose: no migrations to run. current version: 20140823193501[/i][/i][/i]

Additionally, we tried running cheesy-arena on a PC. This gave us an error of 'bind: 1160: Only one usage of each socket address is normally permitted'. This was after a fresh reboot on the PC.. so not clear what would be causing this.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Are you using the newest build of Cheesy Arena that was just released yesterday? I believe that SegFault bug was fixed in that release if it's what I think it is.

As for the socket use error, does the PC you are running have FMS Lite installed on it? If so, that starts a service at bootup that uses the socket. Open up the services window, find the 2 FMS services, stop them both and set their startup type to disabled. That should fix that issue.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Hello billbo911,

In terms of our autonomous routine, we had tried several different routines on the field, the simplest being the activation of four motors, which did not work. We are currently using Java command based. The link to the relevant GitHub section can be found here: https://github.com/Iron-Panthers/FRC...5fad8392ccf646

The code can also be pasted here if you would like to see it in more detail. However, I can confirm that off of the competition field, our autonomous works perfectly, and on the field it prints that it has started, but refuses to run at all. I have checked potential motor brownouts, as well as battery voltages, all to no avail.

We do, in fact, have a TrendNet camera setup on 10.50.26.50, connected to our DLink, which (we thought) might have caused a bandwidth issue, but during the match, as well as during official season matches, we did not experience any bandwidth issues and our autonomous worked just fine.
Our DLink was configured by the Bridging Utility at Cheesy Champs, with an IP of 10.50.26.1
Our RoboRio was configured by us (a 971 mentor also confirmed this) to 10.50.26.2
Our DS Computer was configured statically to 10.50.26.5, and we were able to connect to the robot with minimal issues.
I just can't fathom something that causes just our autonomous to break on the field, and as far as I can tell, it is not a coding issue on our part (as it works off the field and at official events).

Thank you for your time,
-Adam N.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Great thanks to the group for the quick replies (and, most recently, Thad) - updating Cheezy-champs fixed it on mac. Will check on PC - but no doubt that post will be helpful to others.

Got a match to work with only one robot. Good enough to make progress on trying the autonomous next.

Now... there's only the remaining issue of getting the dlink to bridge to the router. A battle for another day with a different router.

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

Wohoo! Yea, we found that bug at CC on Friday while trying to run practice matches... Fun times. Nothing like testing code by running a match :) The issue is that cheesy-arena was expecting all 6 teams to be entered when the first team connects.

I wish you guys had come up to us at CC and said something so we could have taken a look at this problem. Next time, please come up earlier!

There was already one discrepancy at CC found between the reported match time remaining in Cheesy-arena and the FIRST FMS, FYI. It is hard to write code that conforms to a standard that isn't published...

Re: FMS-lite / cheezy-arena - having trouble getting driver station to show up
 

One quick question. Why would you want a default gateway at that address (10.0.100.1)? That address only gets you access to the internet. I usually don't even bother adding a default gateway on the RoboRio.

The RoboRio is only communicating with the DS and maybe an off board Vision processor or camera. All of which should be on the same subnet. Thus, 255.255.255.0 would be the correct subnet mask for the RoboRio.
Now, the DS needs to be able to receive and respond to commands from FMS, thus the DS's subnet mask needs to be 255.0.0.0.