2015 MRI

[silverD]

3883 and 4607,
Let us know how we can help

[thegnat05]

Originally Posted by Chief Hedgehog

Well, we are attending - but we are in a bit of a pickle. Our robot is severely damaged and not certain if we can get it up and running on time.

Please let us know if it is still not working correctly on the 11th! We have lots of extra parts and would love to help get your robot up and running again! We actually damaged our robot severely during our regional competition (bent the catapult shaft) so I know it can be stressful, but try not to worry too much. I'm confident you will have a working robot to compete with.

[Shrub]

MRI scholarships are UP and due Oct 6! This year they're only open to seniors and are $500 each for two people. There doesn't seem to be an essay question word limit if you fit it all within the page. >: )
Good luck!!!

[jvriezen]

Originally Posted by silverD

3883 and 4607,
Let us know how we can help

CyBears 4859 from Byron will be there, but as of Saturday, there are major issues with the control system. We are looking to borrow replacement cRio, modules, and/or DSC prior to arriving to see if the problem can be resolved. The DSC status light flickers wildly when we enable and motors generally don't turn when commanded to do so... but sometimes they do..

[silverD]

Sorry to hear your team is having troubles. Was there an incident that caused these issues or did they just show up? I'm sure you have checked already, but here are some suggestions:
Make sure the 3 lights on the PDB are green as well as the 3 lights on the DSC. Make sure the cRio is isolated from the chassis and that the ribbon cable to the sidecar is not damaged and seated properly. Verify that the modules are seated in the correct cRio slots and that there are no bent pins. Try systematically unhooking components until normal operation occurs.
The next step would be to swap out components. Please PM me in regards to this.
Nate

[Jon Stratis]

Man, with all these teams with problems, I'm gonna have a busy day at MRI!

For all teams - if you know you have problems and need help fixing them, please find me! I'll be the guy with the yellow hat and black vest... basically, wearing the same getup that I've had on every other time you've seen me the past few years Even if you're getting another team to help and don't specifically need my help, let me know - I'll help coordinate things with the field so you don't have people from queueing over there bugging you every 10 minutes!

[silverD]

Originally Posted by jvriezen

The DSC status light flickers wildly when we enable and motors generally don't turn when commanded to do so... but sometimes they do..

Any progress? Is this wireless or tethered? If wireless, it could be a communication issue with the radio/driver station.
Nate

[cadandcookies]

I checked your website, but there doesn't appear to be a list of attending teams. Echoing the OP, does anyone happen to have a list?

I have:

4607
4778
2052
2175 (and practice bot possibly)
3883
2177 (?)
2531 (?)
2220 (not in this thread, but I know they'll be there)
and of course Firebears.

A question mark just means I'm assuming based on the thread you'll be there, even if it hasn't been explicitly stated.

Anyone else?

[Caleb Sykes]

Originally Posted by cadandcookies

Anyone else?

4536.

[Boe]

Originally Posted by cadandcookies

I checked your website, but there doesn't appear to be a list of attending teams. Echoing the OP, does anyone happen to have a list?

I have:

4607
4778
2052
2175 (and practice bot possibly)
3883
2177 (?)
2531 (?)
2220 (not in this thread, but I know they'll be there)
and of course Firebears.

A question mark just means I'm assuming based on the thread you'll be there, even if it hasn't been explicitly stated.

Anyone else?

3130, 1816, 4859, 4536 and 9001 (our practice bot)

[jvriezen]

Originally Posted by silverD

Any progress? Is this wireless or tethered? If wireless, it could be a communication issue with the radio/driver station.
Nate

A new DSC and ribbon cable is scheduled to arrive Thursday. I think we can borrow a bench setup to help diagnose from 2530, and it has been tethered throughout. There were two DSCs, and one's board has what looks like a fried FET (I'm no expert here, but there was a brown spot and someone more informed than I said it was a FET.

Does anyone know how to dump any cRio internal logging files ? Where are they?

I've also seen a 4-slot cRio freeze up because it ran out of logging space and needed some type of hard reset (we've re-imaged it, not helping)


John.

[bachster]

8052 (summer project) will be there too!

[Caleb Sykes]

Originally Posted by bachster

8052 (summer project) will be there too!

Not Dragonfish I hope.

[Jon Stratis]

2177 will be there, and (hopefully) running with the new control system!

Stop by our pit to check out the RoboRio, PDP, PCM, VRM, and the new Victors!

[Bryan Herbst]

Originally Posted by jvriezen

A new DSC and ribbon cable is scheduled to arrive Thursday. I think we can borrow a bench setup to help diagnose from 2530, and it has been tethered throughout. There were two DSCs, and one's board has what looks like a fried FET (I'm no expert here, but there was a brown spot and someone more informed than I said it was a FET.

Does anyone know how to dump any cRio internal logging files ? Where are they?

I've also seen a 4-slot cRio freeze up because it ran out of logging space and needed some type of hard reset (we've re-imaged it, not helping)


John.

I'm not sure which logs you are looking for (or where they would be), but you can FTP into your cRIO at ftp://10.XX.YY.2, or use netconsole at the same address to access the console.

I don't have a cRIO handy, but if you open up either of those and there's a /var/log directory, I would start there.