Public Support

Dear Mr Roth,

thank you for that information. Yes, you are right, we are talking about ADTF2.

So I understand your feedback as there is no limitation, It does not matter how the harddisk recorder is configured (memory, file based etc., cont. or triggered), in all situation is possible to stop a running recording programmatically, right?

Thank you and best regards,

Christian Scheunemann

Hi Christian,

So I understand your feedback as there is no limitation, It does not matter how the harddisk recorder is configured (memory, file based etc., cont. or triggered), in all situation is possible to stop a running recording programmatically, right?

Yes !
The only limitation regarding recording mode is linked to splitting, see Usermanual (chapter 6.1.1 Harddisk Recorder - Modes of Operation)

Thank you. The ticket can be closed.

Best regards,

Christian

Hello again,

we have shortly checked how ADTF responds when key stop events are initiated, we saw the following:

· (1) Queue Mode – File Based Queue, when a recording is active (history e.g. 5s and follow time e.g. 30s) and the stop event (‘a’) is created the log system provides information (“Stop Recording received but already stopping!”) but is does not stop right after the key event, it stopps when the follow-time is expired, which is not our intention, we want to stop before reaching the end of the follow-time.

· (2) Queue Mode – Memory Based Queue, when a recording is active (history e.g. 5s and follow time e.g. 30s) and the stop event (‘a’) is created, the recording is stopped but the data from the memory removed or at least there is no dat file created (content not flushed to file). It is also interesting the log system does not provide any information here.

Due to technical reasons we are using way (1), so (2) is not relevant for us we just used it to check how it responds.

One more question just for clarification: The key event (stop recording) results in EC_StopRecording?

Sorry, so the ticket has to be reopened if it has been already closed.

Thank you, best regards,

Christian

Hi Christian,

"File Based Queue" mode is just a special case of the "File Based Continuous" mode where a start event also triggers a simultaneous stop event, essentially eliminating the continuous part of the recording

The follow-time timeout is triggered by the stop recording event, thus you receive the “Stop Recording received but already stopping!” message.

So unfortunately, no there is no possibility to cancel the recording before the follow-timeout has expired.

The get your desired behavior switch to the File Based Continuous mode with no follow time, and send the stop event at the instant you want to stop the recording. In this case you always need to send a stop event manually, but you have complete control over the timeout.

Hope this is feasible, regards,

Martin

Dear Martin,

I see, yes it is, thank you for the feedback.

Has this use case been considered for ADTF 3, I mean in some situations it would be very useful to stop a triggered recording before it reaches the follow-time (having more control).

Br,

Christian

Hi Christian,

no, currently the behavior is exactly the same in ADTF3. If you want a variable follow time, it's best to control it yourself. It's hard for us to handle specific stop-conditions in a common manner, so the option to not use the built-in follow timer is what we will advise also for ADTF3.

Out of curiosity, can you please explain your specific use-case for canceling the follow timer (which most of the time is a rather short period of time).

Thanks,

Martin