![]() |
Re: Fire at Michigan State Champs
Quote:
"No, no, it's not going to spread that much. Let's wait and see if we can find the CO2 extinguisher..." |
Re: Fire at Michigan State Champs
Quote:
|
Re: Fire at Michigan State Champs
Quote:
|
Re: Fire at Michigan State Champs
Quote:
In addition there were some other factors that may or may not have come into play. There may be a suggestion made on additional safety tests in inspection, or a change in wiring rules. I don't want to be more specific in case I am wrong. |
Re: Fire at Michigan State Champs
Thinking about this now, I realize that something like this could have happened to us. We had a almost unmeasurable frame short (later discovered to probably caused by a limit switch wire connected to a Talon SRX), which passed inspection because the resistance was higher than the required limit.
Last night and this morning we fried two Talon SRXes, and after a ton of troubleshooting we discovered that our LED ring power cable was being pinched and sometimes connecting positive to the frame. If the resistance was a little lower, I think the same thing could have happened to us. This appeared to be what destroyed the Talons. |
First the test only requires the resistance across your frame to be above 3k ohms
Secondly from what I've learned from the team the short was caused by an old unused LED controller that became grounded to the already charged chassis, which led to the heat and fire Thirdly the battery had been removed (or disconnected unsure) from the robot before being Taken off of the field after seen smoking on the field And finally it was definitely a dry chemical extinguisher, the residue was swept and vacuumed up immediately following the incident, but multiple fire extinguishers were brought over to aid the fire, the first extinguisher had its safety pin break off when someone attempted to pull it rendering the extinguisher useless increasing the time it took to extinguish the flames. I would like to congratulate the team however on successfully redoing most of their robot as well as getting their shooting back up and rinning! A great turn around for them after an incident like that. Go team! 2012 - member of 2834 2013 - electrical and mechanical function 2014 - driver, mechanical, and drivetrain 2015 - driver, drivetrain, mechanical knot tying 2016 - captain, mechanical, drivetrain |
Re: Fire at Michigan State Champs
Quote:
Quote:
|
Re: Fire at Michigan State Champs
Quote:
|
Re: Fire at Michigan State Champs
I just found another video on YouTube from the field, recorded by YouTube user zenith828: https://m.youtube.com/watch?v=6QyrZZ3zIX4
|
Re: Fire at Michigan State Champs
Quote:
|
Re: Fire at Michigan State Champs
Quote:
|
Prank on team that caught fire
1 Attachment(s)
See pic :)
|
Re: Prank on team that caught fire
Quote:
|
Re: Fire at Michigan State Champs
Quote:
They said they had already found the issue, a loose Anderson connection on the battery as well as cleaned up the VRM input which had a possible whisker. I verified those and was about to leave, but asked the team if this was the first time. They replied they had other drops at other events. I did a frame isolation check and found the positive side grounded to the frame. The team had LEDs, and it was one of the first items I asked about. The team told me they were disconnected*. We then dug through the various areas and found a different item that would clear the frame isolation. Once cleared, I returned to the field. couple hours later, the fire occurred. I do not have first hand details of how the fire was handled as I was covering the other field, and a large group of people were gathered around, and I thought it was some robot with a typical sensor wire or PWM that had been pinched and smoked. After the fire was out, the issue was diagnosed as a power cable that had previously fed the LEDs. It had a barrel connector that was disconnected earlier. We suspect that the positive side frame grounding was intermittent and the barrel connector likely was exposed negative. This lead to the power cable catching fire when both sides grounded to the frame. It was relatively thin wire, so a short caused it to catch fire relatively quickly. The team did an amazing job of keeping a positive attitude. They had a student lead the rebuild, and she did an amazing job of keeping students on task. One of the new Michigan LRIs working the event stayed with them to ensure it was rebuilt properly. After initial teardown, we inspected the remaining components and had the team not only change out most of the electronics, but most of the pneumatics as well. We were quite fortunate no one was injured, and the team only missed 1 match. I know a report was sent in about the fire incident, and I plan to talk some more with other LRIs about possible ways of improving and/or mitigating future incidents. *I missed asking the team exactly how they "disconnected" the LEDs. I did not see the barrel connector, and assumed the disconnection was done properly. I will be adding a more thorough line of questioning when "something is disconnected". |
Re: Fire at Michigan State Champs
As lead engineering mentor for 3656, Dexter Dreadbots, I can confirm events are as Mike and Ike :) say above. I appreciate both of their help in inspecting and troubleshooting our robot.
Our failure analysis indicates that we had two shorts to our frame (usually you can assume that multiple failures won't happen at the same time--but as Ike says, there was foreshadowing, but we didn't catch the root cause). There was a 12V connection and a ground connection, both to the frame, leading to heating of narrow gauge wires and melting of the PVC insulation, and eventually to fire. The ground connection was a no-longer used barrel connector wired on fine-gauge dual-extruded wire connected to a 20A breaker on the PDP (not so smart in hind-sight). The old wiring had not been removed, and the exposed barrel connector with GND external was in the robot, likely tucked away by a well-meaning team member. Excess length of wire was bundled together with a zip tie between the RoboRio and PDP. More on that later. The disconnected LED power that Ike wonders about was our new wiring. The LEDs had been rewired (to another 20A breaker), but with powerpole connectors and GXL or TXL 20awg wire. These were unplugged while troubleshooting the ground fault. Checking wiring it seemed that pushing on the PCM bracket could make the ground fault come and go. A student rewired it, looking for "whiskers". The problem went away without a "smoking gun", and we assumed it was fixed. The unused barrel connector wires passed through the same area, so moving wires likely moved the barrel connector. The 12v source was the battery anderson connector to the main breaker lug. The main breaker was mounted close (~1/4") to a vertical frame element. It is likely that with repeated battery installation and removals and a high impact game, that the lug may has spun slightly and have allowed current to the frame, by splitting the electrical tape or maybe the taping wasn't perfect. Difficult to tell after the fire. We could not recreate the 12v to the frame that Ike had seen, probably because we had unplugged the battery and moved the lug slightly while looking for the ground issue. Strain relief and more flexible wire for battery hookup would both be helpful with this, as well as additional clearance and better insulation. I was confused how both could be happening at the same time, and assumed we were not understanding what Ike was saying. But we could not recreate the faults, and we were called to que. During the match (see MIDC qual 36 video https://youtu.be/TfYDX4_zND8) our robot let out the smoke about 73s into the match. The driver hit the e-stop at 77s, and the FTA turned off the main breaker about 103s in. The robot appears to stop smoking. After the match was completed and the robot was on the cart around 250s after the match started (not on the same video) the video shot by Byting Bulldogs shows the active flames. Our drive coach had noticed that the RSL was back on about this time. This may be due to the 12v from the frame backfeeding into the PDP after all the insulation was burned off the paired wires. It is likely that the short reoccurred after putting the robot on the cart, or that the heat had been slowly building. At some point the heat was enough to melt through a pneumatic line, adding oxygen to the "smoldering" insulation and allowing it to build to a full fire. Most of the fuel for the fire was from the PVC insulation on the LED wiring (coiled up for maximum heating and fuel potential) and pneumatic tubing. The RoboRio contributed some as well. Our standard for wiring is to use GXL or TXL wire, and the insulation on those wires scorched slightly, but it did not burn or melt. Our students were great at repairing the robot. Many teams offered help and parts. We had students who could and did do the work, and had most of the parts ourselves. As a mentor, I was very proud to hand out tools, get spare parts and help clean up, but not to do the rebuilding. We moved the robot and tools outdoors to several tables because we would not all fit in the pit, and to allow the dispersion of the dry chemical residue. We decided to replace all the electronics and wire (not motor controllers though) and had to replace several plastic components and one pneumatic cylinder that may have been damaged. It may look like a lot of time passed before the extinguisher was discharged, but heat damage was not extensive. We now have an extinguisher on our cart, and I am looking into procuring a CO2 one for less collateral damage. We have moved (and further insulated) the main breaker and are looking into designing and 3d printing an insulator box that would offer strain relief as well. After 4 hours of rebuild we were on the practice field with a fully-functional bot having missed only one match, and are now on our way to St Loius! |
| All times are GMT -5. The time now is 17:30. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi