In reply to dave_59:
thanks Dave, I’m killing my sequence because something wrong is detected (functionally) and I need to stop it, I’ve used seq.kill() and sequencer.stop_sequences() with both I got the same error message (with sequencer.stop_sequences() the simulator stuck), for the driver state how can I identify it?
Thanks,