If you have a digital scope, here are a few things to try: 1. In your controller, add a few lines of code to wiggle a spare I/O pin when the controller gets reset. Then use this to trigger your scope; if noise is causing your controller to restart, your scope will catch it. I've done this, and similar, on other designs to trigger my logic analyzer or dump a text-message to stdout. 2. If #1 above is what is happening, use a second scope channel to monitor potential aggressor signals, such as the power supply. It will be clear from the captured trace if a power glitch caused, or was the result-of, a restart. 3. If #1 is not happening, trigger your scope when the HV supply drops, for example negative-edge trigger at 130 volts. Then use the other channel(s) to probe power supplies, or signals to the smart-socket.
-- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/ccd5b333-4af8-453f-a8a6-48a21b3dae73%40googlegroups.com.
