Thanks. Sorry to bother you. I actually hooked tis up to Windows nd used Optec's control panel and the results are the same. Something is wrong in the device.

Kurt

Read More...

Here is the log. Hopefully I enabled what you need.


 

File Attachment:

File Name: AlnitakLog.rtf
File Size: 17 KB



Kurt

Read More...

I have an Optec Alnitek automatic aperture cover. The Park/Un-Park Open/Closed state are reversed from what the cover is actually is doing. When the cover is commanded Unparked it displays Open but is actually closed. Likewise when it displays closed it is open.

Kurt

Read More...

Kurt Lanes created a new topic ' Problems with ASI294C' in the forum. 3 months ago

I purchased a ASI294C camera to replace my ASI244C. The 244 was working fine but my OAG is a Sagitta and it has a 12x12mm pickoff and the ASI244 is too small to exploit this. This new camera has been giving me fits. I start EKOS and connect to all the devices..This first issue is if INDI is running and you answer yes to the restart INDI both Kstars versions 3.5.6 and 3.5.7 crash (running the MAC version). This is just a annoyance but I thought I would note it here. After everything connects and is verified ok then I start PHD2 and connect the camera and mount. As soon as looping is started PHD2 repeatedly disconnects from the camera and you cannot get an exposure at all because each exposure disconnects the camera. If I change the profile to use the internal guider to try and get something working Kstars crashes as soon as EKOS is started. If I select the Lin guider in the profile it never can get an exposure. If I modify the profile to remove the guide camera then PHD2 connects and works correctly and furthermore when the scheduler starts a new job it has no problem starting the guiding in PHD2 even though there is no guide camera in the profile.

I have also has a problem that when I load a sequencer job I get the INDI is running popup and if I click no I get two copies of every device in INDI and the sequence won't run because it detects that it cannot connects to the second version of each device. If I click yes to restart INDI Kstars crashes.

Any thoughts.

Kurt

Read More...

I have checked this several times. My sequencer runs always have the plate solving set for each task. When the flip occurs the current capture is aborted and restarted by no plate solve occurs. It has never done a plate solve after the flip.

Kurt

Read More...

Thanks Hy. That was very helpful and I was able to get it working better.

Kurt

Read More...

Due to atmospheric conditions or thermal conditions sometimes best focus has a fairly large HFR. This is also aggravated by the small 3.6 um pixels in my camera. This cause the align module to not detect any stars. How can I adjust the detection parameters so I can align. It is not possible to bin 2x2 since this is a DSLR.

Here is an example where the HFR is 6.1 pixels and the alignment fails.
 



Thanks

Kurt

Read More...

Kurt Lanes replied to the topic 'DSLR INDI crash (EKOS Debugger)' in the forum. 3 months ago

I've been having a similar problem using a Sony camera running on Mac. The most common manifestation is when a sequence starts and on the first camera collection, that is after the focus and plate solve, the system hangs when the first exposer starts downloading.. I haven't noticed problems in focus or align but it seems like the current version 3.5.7 crashes more ofter than 3.5.6.

Kurt

Read More...

I use a Sony A7R4 and I have a problem that I think the darks I collected in the Camera tab. When I do an alignment and select to use Darks as soon as the image is downloaded the Darks box is deselected. I loaded the darks and a camera raw in PIXINSIGHT. The stored Dark in the .fits file is  16-bit integers, 3 channel(s), 9504x6336 pixels but the camera raw file is w=9600 h=6376 Image geometry .... x=0 y=0 w=9568 h=6376. I think this geometry mismatch causes EKOS to discard the darks but I am just guessing.

This difference also causes  a geometry mismatch if I try and collect Flats in EKOS and use them to calibrate the camera raw files. If I try to collect everything as fits files I cannot collect flats because Kstars crashes if you take an  exposure under 1 second.



 

/Volumes/Astrophotography/darks/darkframe_2021-08-24T18-33-09.fits** Warning: Deprecated format: FITS52 FITS keywords extracted.Reading FITS image: 16-bit integers, 3 channel(s), 9504x6336 pixels: 68% Reading 1 image(s):/Volumes/Astrophotography/darks/darkframe_2021-11-30T19-47-32.fits** Warning: Deprecated format: FITS52 FITS keywords extracted.Reading FITS image: 16-bit integers, 3 channel(s), 9504x6336 pixels: done Reading 1 image(s):/Volumes/Astrophotography/FinishedCollections/M_33_Triangulum/Jan-22-2022_Neodymium/SESSION_Jan-22-2022_Triangulum_M_33_Light_600_secs_2022-01-22T20-34-22_005.arwReading metadata: done Camera ............ Sony ILCE-7RM4Timestamp ......... 2022-01-23T10:17:06ZTime offset ....... -06:00Exposure .......... 1/10sISO speed ......... 500Author ............ Kurt R LanesCFA pattern ....... Bayer RGGBRaw dimensions .... w=9600 h=6376Image geometry .... x=0 y=0 w=9568 h=6376

Thanks

Kurt

Read More...

Robin

Did you get your problem solved? It came back for me and I think there are two problems. The first one is focus. If the focus isn't top notch the alignment will fail. The other is darks. I see a lot of hot pixels detected even using new darks.

Kurt

Read More...

Any idea on how to make this work. It never solves for me after a flip. It does seem to restart the collection sequence but not the focus, align , or guiding.

Kurt

Read More...

Thanks Fabio. That very well might be the case. I have been right clicking and selecting goto under the iOptron CEM70. Where is the goto for the target Kstars has centered? I assigned a shortcut to the right command.

The other think is that I have seen this problem when I am running the scheduler and I didn't click anything.

Kurt

Read More...

I posted this issue a couple of months ago but I thought I would start fresh. I have been having a problem where a slew to the target arrives at the wrong location as indicated my the CEM70. That is the mount target is not on top of the Kstars target. Yesterday I did a search for M33 and centered and tracked it by double clicking M33 in the search results. I then right click and select "iOptron CEM70" > goto. The coordinates of M33 in Kstars shows RA 1h 35m 4.5s 30deg 46m 25.25s

The log file shows:
 
[2022-01-24T16:54:27.875 MST INFO ][ org.kde.kstars.ekos.align] - Target updated to JNow RA: "01h 35m 38s" DE: " 31° 29' 51\""
[2022-01-24T16:54:27.876 MST DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "01h 35m 38s" ( 1.59385 ) DE: " 31° 29' 51\"" ( 31.4976 )
[2022-01-24T16:54:27.879 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:SRA008606806#> "
[2022-01-24T16:54:27.907 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <1> "
[2022-01-24T16:54:27.908 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:Sd+11339120#> "
[2022-01-24T16:54:27.927 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <1> "
[2022-01-24T16:54:27.927 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:MS1#> "
[2022-01-24T16:54:27.958 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <1> "
[2022-01-24T16:54:27.960 MST INFO ][ org.kde.kstars.indi] - iOptron CEM70 : "[INFO] Slewing to RA: 1:35:38 - DEC: 31:29:51 "
[2022-01-24T16:54:27.960 MST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Tracking" to "Slewing"
[2022-01-24T16:54:27.962 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:GLS#> "
[2022-01-24T16:54:28.008 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <-3839430045030000220511> "
[2022-01-24T16:54:28.008 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] CMD <:GEP#> "
[2022-01-24T16:54:28.022 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] RES <+1107856200850842011> "
[2022-01-24T16:54:29.023 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:GLS#> "
[2022-01-24T16:54:29.063 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <-3839430045030000220511> "
[2022-01-24T16:54:29.063 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] CMD <:GEP#> "
[2022-01-24T16:54:29.119 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] RES <+1108258300851811011> "
[2022-01-24T16:54:29.342 MST DEBG ][ org.kde.kstars.indi] - Image received. Mode: "Guide" Size: 639360
[2022-01-24T16:54:30.112 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] CMD <:GLS#> "
[2022-01-24T16:54:30.151 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[DEBUG] RES <-3839430045030000210511> "
[2022-01-24T16:54:30.152 MST INFO ][ org.kde.kstars.indi] - iOptron CEM70 : "[INFO] Slew complete, tracking... "
[2022-01-24T16:54:30.152 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] CMD <:GEP#> "
[2022-01-24T16:54:30.183 MST DEBG ][ org.kde.kstars.indi] - iOptron CEM70 : "[SCOPE] RES <+1133912200860692511> "
[2022-01-24T16:54:30.185 MST DEBG ][ org.kde.kstars.ekos.mount] - Mount status changed from "Slewing" to "Tracking"

Why didn't the CEM70 get commanded to the coordinates shown in the Observation Planner? Did I do something wrong?

I sent additional goto command and the CEM70 just wanders around M33 but will not go there.

Thanks

Kurt

Read More...

Thanks. The Force re-alignment before starting each job in the EKOS settings for the mount is set but no plate solve is happening on flip.

Kurt

Read More...