2025-11-04 4:22 PM
Hi - I have an application running a 1 kW 500VDC to 25V DC supply for a klystron filament heater. I am using a 3 phase forward converter - each phase driven by a FET half bridge to a transformer primary returning to input mid-point. I drive the six gate drives using six HRTIM pins.
I have programmed this so that each of the gate drive pulses is turned on at a fixed time in the master cycle, and turned off by one of two things: either a timer counter (thus setting duty cycle %) or an event connected to an internal comparator. The comparators use an internal DAC for the -IN reference, and are pinned out to a rectified current transformer on the primary. This then gives me both duty cycle and peak current control for continually adjusting providing regulation.
What I would like is a continual running diagnostic where I can read the status from the HRTIM and determine what caused the most recent commutation off (i.e. counter compare or comparator event). Right now I have to infer that indirectly by calculations and settings, and it would be nice to confirm this directly. I see no control registers for the HRTIM that would give me this sort of status, but there are a large number of control registers so I may have missed this. It may also be possible to hack some clever parallel connection such as separately (in parallel) counting events of comparator triggers, which I could compare to the total number of off-commutations for an interval.
Any ideas? Thanks! Jeff Casey
2025-11-18 5:12 AM
Hello,
There is no straightforward solution to find what caused the reset event, however you can make a capture on the event of comparator, so if the timer counter is over without getting this event, the capture status does not rise. Capture status could be found in this register HRTIM_CPT1xCR.
Best regards.