8000 Error when using Stream as Data Source with External triggering · Issue #8 · areaDetector/ADEiger · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Error when using Stream as Data Source with External triggering #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rcjwoods opened this issue Aug 31, 2017 · 2 comments
Closed

Error when using Stream as Data Source with External triggering #8

rcjwoods opened this issue Aug 31, 2017 · 2 comments

Comments

@rcjwoods
Copy link

Hi Bruno,
I've noticed that when I set the Data Source to Stream, and acquire a series of images with external triggering (either External Series, or External Enable), I have to press Stop to end the 'Collecting' status. This changes the Acquire Status to 'Done', and the Detector State returns 'Aborted'. The next acquisition causes an ioc error, "StreamApi::readToken: unable to find 'header_detail' token" and "eigerDetector::streamTask: failed to get header packet".

This is different from using Internal triggering. After acquiring an internally triggered series, again using Stream, I press the 'Stop' button, and the Detector State reports 'Idle'. No errors are produced by the next acquisition. So one work-around solution I have is to acquire an Internal Series at the end of each External Series to (in some sense) reset the detector state or clear the ioc error.

I've also found that when using the FileWriter as the Data Source, after sending 'Stop', the Detector State reports 'Aborted', but no errors are produced by the next acquisition, so maybe the Detector State reported is not so relevant to this question.

I hope that makes sense!
Thanks,
Russ

ps. I'm using the up-to-date ADEiger-dev branch.
@brunoseivam
Copy link
Member

Hi Russ,

I can't reproduce it here. If I had to guess, I'd say that at the beginning of the acquisition streamTask is probably getting a stray packet indicating the end of the previous acquisition. Here's a patch that makes getHeaderignore unexpected packets. Could you try it and see if it solves your issue?

https://gist.github.com/brunoseivam/2cdac5d63a7d856a95c0d05b0ae61164

Regarding the "Aborted" vs "Idle", if streamTask doesn't get the last packet indicating the end of the acquisition, then it will report that it didn't complete and the driver will say "Aborted" (even if you got all frames). I think a future improvement that could be made is to make streamTask aware of the expected number of frames.

External triggers are currently tricky because there's no way to tell when the detector is done. Dectris implemented a wait command that doesn't quite work in the current firmware version, but they promised it would be fixed by next version.

@rcjwoods
Copy link
Author

Hi Bruno

Thanks so much for the patch - that fixes my problem!
The ioc now reports "eigerDetector::streamTask: got stray packet, ignoring" at the beginning of an external trigger acquisition, but it does not prevent subsequent acquisitions.

Russ

brunoseivam pushed a commit that referenced this issue Aug 31, 2017
Stream: ignore non-header packets at the start of the stream. Fixes #8
abdcd48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brunoseivam @rcjwoods
0