Was carrying out ground deployment tests for a rocket that my Uni team are planning on launching soon. This rocket has BP charges on both bulkheads of the Avi bay (Apogee charge on lower bulkhead, Main charge on upper bulkhead). We had the Avi Bay fully wired up with BP charges prepped and went to turn the board on to check continuity. All was good but we didn't have continuity on the main channel so we turned the board off to investigate, the e-match was loose so we fixed it and went to turn the board back on again with the screw switch. When we turned the board on again a second time both BP charges went off instantly. Luckily nobody was hurt but it definitely shock us up.
We checked over all the wiring afterwards and everything was as should be, we then decided to try turn on the board again this time with just e-matches in, it's behavior was all normal until we tried to fire the channels remotely, sometimes they would fire, sometimes they wouldn't , overall just strange behavior. We tried this again a couple hours later and everything was suddenly fine.
We've used this Raven before and had no problems, it was recently on a flight that had a hard landing (main parachute didn't fully deploy so came down under drogue only), unsure if this could have damaged it in some way. I checked over the board and all the components and solder joints look fine.
This ground test was a simple setup that we have used many times before, Raven was connected to a terminal expansion board, both charges were wired through the bulkheads to terminal blocks where the e-match was connected into the other side and then placed into our aluminium BP charge cups. We were using a 3s 550 mAh Lipo and the only other thing mounted to the bay at the time was a Telemetrum connected to a 1s. The raven had the latest firmware uploaded.
Interested to hear if anyone else has experienced a similar thing? Attached below is a picture of the bay (minus the body tube and upper bulkhead) just after it blew both charges encase someone can pick up on something.
We checked over all the wiring afterwards and everything was as should be, we then decided to try turn on the board again this time with just e-matches in, it's behavior was all normal until we tried to fire the channels remotely, sometimes they would fire, sometimes they wouldn't , overall just strange behavior. We tried this again a couple hours later and everything was suddenly fine.
We've used this Raven before and had no problems, it was recently on a flight that had a hard landing (main parachute didn't fully deploy so came down under drogue only), unsure if this could have damaged it in some way. I checked over the board and all the components and solder joints look fine.
This ground test was a simple setup that we have used many times before, Raven was connected to a terminal expansion board, both charges were wired through the bulkheads to terminal blocks where the e-match was connected into the other side and then placed into our aluminium BP charge cups. We were using a 3s 550 mAh Lipo and the only other thing mounted to the bay at the time was a Telemetrum connected to a 1s. The raven had the latest firmware uploaded.
Interested to hear if anyone else has experienced a similar thing? Attached below is a picture of the bay (minus the body tube and upper bulkhead) just after it blew both charges encase someone can pick up on something.