You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Hexitec software is suddenly starting bias refreshing before acquisition is complete. Our acquisition time is set to 3.0 Seconds. Of course, we check the bias voltage box. We're using Hexitec V1.1. We tried acquisition for different times 5 seconds, 10 seconds, 30 seconds, but almost immediately the software gives the message "bias refreshing". It was working fine previously with 3 second acquisition time. Is the problem of the software or the hardware?
Please refer to this screenshot.
The text was updated successfully, but these errors were encountered:
This repository contains the Linux-based software, whereas the Windows version you're using is available here: https://github.com/stfc-detectors/hexitec
I do maintain both repositories though.
With regards to HexitecGigE, the person you are looking for is Matt. You can find his email address through the HexitecGigE software by clicking on Help -> About and his details can be found in prompt there. I have also taken the liberty of forwarding onto Matt W, the email address you use on GitHub (since GitHub has removed the ability to send private messages). Unless I am mistaken, it's a Gmail address so you should hear from him there.
Hope this helps, feel free to reply here if both methods fails to get you in touch with Matt W.
Hello,
Our Hexitec software is suddenly starting bias refreshing before acquisition is complete. Our acquisition time is set to 3.0 Seconds. Of course, we check the bias voltage box. We're using Hexitec V1.1. We tried acquisition for different times 5 seconds, 10 seconds, 30 seconds, but almost immediately the software gives the message "bias refreshing". It was working fine previously with 3 second acquisition time. Is the problem of the software or the hardware?
Please refer to this screenshot.
The text was updated successfully, but these errors were encountered: