Ematch not always open after firing

MagicSmokeFireworks / magic-smoke-cloud

This is the local server instance that drives the Magic Smoke client photons.

1 stars 0 forks source link

Ematch not always open after firing #7

Closed viomonger closed 7 years ago

viomonger commented 8 years ago

During Greg's retest on 3 July 2016, channel 3 fired, but was still reading low. Reading with multimeter confirmed a 31 Ohm resistance of the burned ematch. So a low-ohm reading after a successful burn is possible (although seemingly not particularly common). Have to be careful about assumptions made in the server-side control related to low-ohm readings after fire commands.

viomonger commented 7 years ago

Combine ohm readings with the fire command counters. See: MagicSmokeFireworks/magic-smoke-firmware#4

viomonger commented 7 years ago

Show page indicates fire status based on fire command count in telemetry, not based on resistance reading. Status page will indicate the unexpected low resistance alongside the acknowledged fire command.