Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   General Forum (http://www.chiefdelphi.com/forums/forumdisplay.php?f=16)
-   -   Al's Annual Inspection Thread 2015 (http://www.chiefdelphi.com/forums/showthread.php?t=134226)

Ether 10-02-2015 09:52

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by notmattlythgoe (Post 1441185)
There was actually a QA about it.

Link please.



notmattlythgoe 10-02-2015 09:58

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Ether (Post 1441188)
Link please.



Apologies, I must have misread something. G21 prohibits any indirect interaction with the robot.

This would then be illegal.

Thank you for the check Ether.

JamesCH95 10-02-2015 10:46

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by JamesBrown (Post 1441182)
Come on, This is pretty ridiculous. Every robot that uses vision would be capable of receiving communication from drivers in this manner. Surely you would not be suspicious of every team that has a camera. Unless you have specific reason to believe that a team is actively controlling their robot illegally during autonomous then I would hope you would not be considering penalties or cards. You are grasping at straws. If a team wanted to communicate in autonomous there are many more reliable, and more discrete ways than a remote control in autonomous. Unless you are equally suspicious of every team that has a camera that even instantaneously looks at the drivers station area, then you are being extremely unnecessarily judgmental here.

I would bet that an IR remote is a lot easier to implement than gesture recognition from a camera located on the robot, viewing through the player station or picking out someone in the crowd.

Viewed a different way - an IR remote has no functional value to any team at competition whereas a camera does. With a camera the risk of cheating is worth the added functionality that many teams gain, whereas the risk of cheating with an IR remote is not worth the ability to turn decorative LEDs on and off.

To take your hyperbole-ridden example even further: wifi security is never 100% secure! We should make all of the robots drive around on tethered connections. Obviously this is totally impractical, at some point we must assume some risk because it is worth the reward. I can very clearly see why an IR remote would be disallowed and why cameras are allowed.

Sperkowsky 10-02-2015 11:14

Quote:

Originally Posted by Drakxii (Post 1441173)
I would cut the receiver cable in half and crimp on quick disconnect connectors on each end. This way once the lights are set you can remove the receiver and so no commutation can happen mid game.

Now quick question, if you power down the LEDs do they remember their color? If not, I wouldn't recommend this method as you will burn battery while in line just for your lights.

Also if the goal is just alliance colors, you can just hard wire the black(power) wire of the LEDs to the PDB and then wire the blue and red wires (grounds) to a switch and then the switch to PDB. So the lights would be red or blue based on the switch.

Quick release as in a pwm style connector.

Al Skierkiewicz 10-02-2015 12:26

Re: Al's Annual Inspection Thread 2015
 
OK,
Here it is...
I screwed up. As people have pointed out earlier in this thread, objects that fit within the 28" x 42" x 78" high size limitation are legally within the TRANSPORT CONFIGURATION even when the team intends to attach those parts to the robot on the field. Inspection will likely check your TRANSPORT CONFIGURATION as defined in T6 & R3, when checking that all of your robot (and additional mechanisms) is weighed.
To remind everyone, bumpers are not BUMPERS and only 2015 rules apply. As such B&T and withholding are affected as well.
I am very sorry for any additional ulceration this may have caused.

Al Skierkiewicz 10-02-2015 12:30

Re: Al's Annual Inspection Thread 2015
 
As to IR devices on the robot, this seems to be the defining rule.

R52 No form of wireless communication shall be used to communicate to, from, or within the ROBOT, except those required per R46 and R51 (e.g. radio modems from previous FIRST competitions and Bluetooth devices are not permitted on the ROBOT during competition).

Foster 10-02-2015 12:43

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Al Skierkiewicz (Post 1441250)
OK,
Here it is...
I screwed up.

I am very sorry for any additional ulceration this may have caused.

No problem, all of the East Coast people were looking for a scapegoat for all the snow. West Coast was looking for one for all the rain. Thanks for stepping up and checking, it takes a big CRI to say they were wrong. :)

AustinShalit 10-02-2015 12:45

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Foster (Post 1441261)
West Coast was looking for one for all the rain

Or Sunny and 80°... :cool:

Drakxii 10-02-2015 13:29

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Sperkowsky (Post 1441227)
Quick release as in a pwm style connector.

Was thinking connectors like this http://www.mcmaster.com/#standard-electrical-wire-terminals/=vundl2 should be able to find some at local store as well. Just makes sure to get the right gauge size.

EricH 10-02-2015 19:52

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by JamesBrown (Post 1441182)
Unless you have specific reason to believe that a team is actively controlling their robot illegally during autonomous then I would hope you would not be considering penalties or cards. You are grasping at straws. If a team wanted to communicate in autonomous there are many more reliable, and more discrete ways than a remote control in autonomous. Unless you are equally suspicious of every team that has a camera that even instantaneously looks at the drivers station area, then you are being extremely unnecessarily judgmental here.

If that team's camera is looking at--and the robot is apparently responding to--a sign the team is holding, in automode, durn right I'm gonna be suspicious!

The rules are simple: NO wireless communication to the robot except via the field wireless (or by signal placards etc. outside of automode, should you choose to use that method--but I call it more trouble than it's worth).


That being said, leaving the remote in the pits would--to me--do the trick, at least as far as on-field activity is concerned. Now the whole "wireless within the robot" part of the deal is another story. So let's see if we can get you running without the wireless, and save the wireless part of the cool factor for demos.

MrRoboSteve 10-02-2015 23:43

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Sperkowsky (Post 1441003)
There's a tiny ir reciever on our robot to control the leds. During matches do you think I will be allowed just to put electric tape over it.

Ever consider controlling the LEDs via the roboRIO? Alliance color is available via API:

DriverStation::Alliance DriverStation::GetAlliance()

Return the alliance that the driver station says it is on.

http://first.wpi.edu/FRC/roborio/rel...72988 3ce9855

Positives: no dispute with inspectors, always tracks color correctly.

Sperkowsky 11-02-2015 07:24

1 Attachment(s)
This was my solution. I just soldered on some pwm connections. This way we can change the leds in the pit by attaching the ir putting on the robot changing the color then taking the ir receiver off. It takes about 11 seconds.


Attachment 18278

Al Skierkiewicz 11-02-2015 07:50

Re: Al's Annual Inspection Thread 2015
 
OK Round 2.
1. With the new control system there will be a need to see all of the components. Please don't hide the RoboRio, PDP and other modules. Inspectors need to see the breakers and the wires that attach to them. Field people need to see all indicators including the radio.
2. Speaking of the radio, if you want reliable operation, be sure to secure the power connector on the radio. A piece of tape works OK but a adhesive backed anchor for a wire tie works best. Either place the anchor on the radio or on your robot near the radio mounting point. If the power connector moves a lot during operation, noise is introduced to the radio power.
3. The radio works best when mounted in the clear on your robot. When you surround the radio with metal it tends to block the antennas inside the box and/or detune them to the point that your connection and bandwidth are affected.
4. The Ethernet connections to your radio should also be secure and mindful of the minimum bend radius of the cable you use. In most cases that is two inches minimum radius. When you bend the cable, bad things happen to bandwidth and the wires can be forced to migrate through their insulation.
5. All teams must connect the CAN buss from RoboRio to the PDP even if you do not use CAN or pneumatics. This connection will be used to log PDP voltage. (R61 & R62)
6. Don't forget the Robot Signal Light. At least one RSL must be mounted on the robot and visible when standing three feet in front of your robot. R54

rich2202 11-02-2015 09:49

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by Al Skierkiewicz (Post 1441685)
1. With the new control system there will be a need to see all of the components. Please don't hide the RoboRio, PDP and other modules. Inspectors need to see the breakers and the wires that attach to them. Field people need to see all indicators including the radio.

My team has most of the wires in wire channels. Will the RI's be following wires, or just see their connections?

Whippet 11-02-2015 09:53

Re: Al's Annual Inspection Thread 2015
 
Quote:

Originally Posted by rich2202 (Post 1441726)
My team has most of the wires in wire channels. Will the RI's be following wires, or just see their connections?

My thoughts are that they are looking for proper gauge wire going to the correct breaker sizes.


All times are GMT -5. The time now is 15:27.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi