External trigger scan finishes without setting off (FMC) BUSY signal

When performed an external trigger scan (python scan_ext_trigger.py), with the KC705+FMC+SCC + TLU for trigger (LEMO connector, simple handshake mode), development branch (33690f29); when finish, the BUSY signal is still present, therefore the TLU is sending triggers. This is not the expected behaviour as after the scan is finished, the BUSY signal should be down, stopping the TLU triggers (as is in handshake mode). Esther and myself have (provisionally) fixed this behaviour by applying a TLU reset after the scan stop, but we are not sure if this is the proper or better way to do that, so please take a look a let us know. You can find the path in our fork: sifca/bdaq53@874b93ab