PlanetaryImager
PlanetaryImager copied to clipboard
GuLinux
Zwo ASI 183MM timeouts on macosx
First of all, Planetary Imager is a very nice program and worked fine for me with a Zwo ASI 120MM-S.
Now to my issue: compiled/installed planetary imager from scratch a week ago on macosx 17.7.0 (High Sierra, latest) with Qt 5.10.0. Connected a ZWO ASI183MM camera. Frame grabbing works for a couple of seconds then "crashes" with uncaught timeout... See log further below. Once, I was fast enough to switch to 4x4 binning; after that, the program was running stable. I did set the binning to 4 in a preset file, but the camera control panel after start shows binning of 1. Is there a default preset file (file name?).
Additional silly question (sorry): how can I reset the GUI; the program remembers the last windows etc, but I'd like to restart with the original GUI setup.
Log file attached.
Thank you. Best wishes, Stefan
Crash log: Starting PlanetaryImager - version 0.7.70 (x86_64) Writing full output to logfile: ...Library/Caches/PlanetaryImager/PlanetaryImager.log WARNING - QWidget::setLayout: Attempting to set QLayout "" on QWidget "statsWidget", which already has a layout WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help'
WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' WARNING - QMainWindow::saveState(): 'objectName' not set for QToolBar 0x7f9f0e850f30 'Help' libc++abi.dylib: terminating with uncaught exception of type ZWOException: ASI error TIMEOUT: timeout (code: 11) on Capture frame PlanetaryImager/src/drivers/zwo_asi/asiimagingworker.cpp:87) Error: signal 6: [0]: address: 0x7fff5a294f5a, file: , function: [1]: address: 0x20008, file: , function: [2]: address: 0x7fff5a0321ae, file: , function: [3]: address: 0x7fff57f2ff8f, file: , function: [4]: address: 0x7fff57f30113, file: , function: [5]: address: 0x7fff59371a4f, file: , function: [6]: address: 0x7fff57f4b7c9, file: , function: [7]: address: 0x7fff57f4b843, file: , function: [8]: address: 0x10e644a38, file: , function: [9]: address: 0x7fff5a29e661, file: , function: [10]: address: 0x7fff5a29e50d, file: , function: [11]: address: 0x7fff5a29dbf9, file: , function: Killed
Hi, I just updated the ASI SDK in master, would you like to retry? As for resetting, it might be implemented in a while, as I had some problems with the UI as well (it needs a proper audit, and a reset action) Cheers
Dear Marco,
Thanks for this information.
I tried the updated version today on Ubuntu and it worked while recording full frame (5496x3672 px) ASI 183 images with 16-bit.
Without recording, just displaying the images inside the GUI results in timeouts for full frame 16-bit images.
Binning 2x2 for GUI displays is fine.
As I said above RECORDING works.
Do you want a more detailed log or other infos?
I noticed that auto gain or updated e-/ADU infos depending on programmable gain do NOT work …
I will check the MAC version next week.
Thanks for your great work, let me know whether I can help you with this ASI183 camera implementation …
Best wishes,
Stefan
On 23. May 2019, at 17:37, Marco Gulino [email protected] wrote:
Hi, I just updated the ASI SDK in master, would you like to retry? As for resetting, it might be implemented in a while, as I had some problems with the UI as well (it needs a proper audit, and a reset action) Cheers
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GuLinux/PlanetaryImager/issues/65?email_source=notifications&email_token=AAHLY5ACV5GVUHHTOLVOPZTPW223PA5CNFSM4HGVS6C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCT2IA#issuecomment-495271200, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHLY5EJ657ROFUK26R4GB3PW223PANCNFSM4HGVS6CQ.
Hi, I do have an ASI183MM camera, so I should be able to debug it properly. I didn't see this behaviour on my box, but I suspect it's mainly a performance issue due to the relatively high resolution of the camera (I use a quite high end laptop, with slower CPUs or less RAM it might misbehave). Could you confirm the hardware specs of your platform?
I noticed that firecapture uses much less CPU, but double or triple the RAM, so a possible solution would be to rely more on RAM while acquiring frames.I'll try to have a go and see where this leads me. Cheers, Marco
Hi Marco,
I did run the ASI183MM camera tests on a
Fujitsu ESPRIMO P757/E94+ (Model M16W) with 16 GB RAM.
The machine comes with a 4 core i5-6600 CPU @ 3.30GHz
OS is Ubuntu 18.04.2 LTS.
Let me know if you need more infos.
Best wishes,
Stefan
On 3. Jun 2019, at 20:54, Marco Gulino [email protected] wrote:
Hi, I do have an ASI183MM camera, so I should be able to debug it properly. I didn't see this behaviour on my box, but I suspect it's mainly a performance issue due to the relatively high resolution of the camera (I use a quite high end laptop, with slower CPUs or less RAM it might misbehave). Could you confirm the hardware specs of your platform?
I noticed that firecapture uses much less CPU, but double or triple the RAM, so a possible solution would be to rely more on RAM while acquiring frames.I'll try to have a go and see where this leads me. Cheers, Marco
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GuLinux/PlanetaryImager/issues/65?email_source=notifications&email_token=AAHLY5EJNEGTCOPP5XWSOWDPYVSEJA5CNFSM4HGVS6C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2LDQY#issuecomment-498381251, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHLY5E6GXG5NFIUN447EYTPYVSEJANCNFSM4HGVS6CQ.
Hi, could you please retry with the latest release (https://github.com/GuLinux/PlanetaryImager/releases/tag/v0.7.70_20190613_ci137)? I didn't specifically address your issue (I'm not sure I can reproduce it correctly), but it addresses a couple of problems with the ZWO driver giving a small performance/stability boost