may it be, that there is some other routine after the "CheckIfDCMotor" which causes the handshake to fail ? Pls. let me know, whether you need more log-output.
Many thanks & kind regards
Dirk

Read More...

@geehalel: I finally succeeded in building your modification of the skywatcherAPI into my system (don´t ask why it took so long...). Surprisingly, my mount still refuses to connect. The handshake still seems to fail at or after the "isDCMotor" routine. Here is the output of the logfile:
[2021-01-28T15:15:10.954 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] Toggle Debug Level -- Scope Verbose "
[2021-01-28T15:15:22.107 W. Europe Standard Time INFO ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[INFO] Scan complete. Found 1 port(s). "
[2021-01-28T15:15:26.432 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] ProcessTextProperties - name(DEVICE_PORT) "
[2021-01-28T15:15:27.616 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] ProcessTextProperties - name(DEVICE_PORT) "
[2021-01-28T15:15:34.933 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] Connecting to /dev/ttyUSB0 @ 115200 "
[2021-01-28T15:15:34.985 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] Port FD 3 "
[2021-01-28T15:15:34.997 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] Connection successful, attempting handshake... "
[2021-01-28T15:15:35.008 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[SCOPE] SkywatcherAPIMount::Handshake "
[2021-01-28T15:15:35.019 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[SCOPE] InitMount "
[2021-01-28T15:15:35.030 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[SCOPE] CheckIfDCMotor "
[2021-01-28T15:15:36.948 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[SCOPE] SkywatcherAPIMount::Handshake - Result: 0 "
[2021-01-28T15:15:37.000 W. Europe Standard Time DEBG ][ org.kde.kstars.indi] - Skywatcher Alt-Az : "[DEBUG] Handshake failed. "
[2021-01-28T15:15:37.054 W. Europe Standard Time DEBG ][ org.kde.kstars.ekos] - "Skywatcher Alt-Az" is disconnected.
[2021-01-28T15:15:37.066 W. Europe Standard Time INFO ][ org.kde.kstars.ekos] - "Skywatcher Alt-Az is disconnected."

Read More...

I'm so sorry....

about "When you choose the driver in ekos, I only get the SVBONY or the SVBONY CCD305 (or something similar) . Are there someone more specifics coming out of the 305PRO? Or does the 305's INDI driver already detect whether or not it has tracking? Because I get, in the INDI panel, the guidance menu."

I confirm that I have the "SVBONY 305PRO 0" version, I understand that detect automaticaly the version of the camera you are connected.

Thanks,

Pep

Read More...

Hi,

I have the same problem. Pi4 running fresh 1.5.6 with the StellarMate Android app, is there any solution for this?

Read More...

office-product-key.com/

Office.com/setup - Enter Product Key - www.office.com/setup

Office.com/setup - Get started Office by download and install. You need 25-digits product key for activation. Get Office setup from www.office.com/setup.

webrootcom.com/

ukwebroot.com/

Can you check StellarMate OS Beta channel? This should have KStars with the fix applied.

Read More...

That should be the "Tolerance" setting in the "Process" tab.
However, judging from your screen shot, the process had still been in the first stage (at full size steps). It will never stop there. It tries to locate the minimum at the initial step size resolution, only then starts a second scan at half that step size, and there it will stop if the value can be confirmed within the tolerance.
With LINEAR you should also always try to start (very) close to the proper focus.

Read More...

I looked further into the code, although I do not really understand, how it does work. I made a local clone of the indi core and want to change the skywatcherAPI.cpp so it will return the "IsDCMotor" variable as "false" (without even checking; so just plain setting of the variable). I also noticed that in the code of the skywatcherAPI.h the MountType for the Az-Eq 6 is missing. From looking into the code of the eqmod driver I understand the MountType for the AZEQ6 should be "0x05". So could I just enter a line under enum MountType (eg 271) reading "AZEQ6 = 0x05," ?
Any help is very much appreciated !

Read More...

AstroNerd wrote: FYI, the Altair Astro cameras are also identical to those too, and are just a rebrand, and use the same driver apart from a couple of changes....

Maybe add that (IMO) you should mostly ignore the maximum value. It's usually from hot/warm pixels anyhow (unless you're really overexposed).

ASIStudio has it's own default settings, as Max says, and tweaks the white balance. That is a definite no-go for proper astro processing as the ZWO driver/library changes the raw values in the FITS file if your WB isn't 50/50. So (in EKOS) verify you're at 50/50, then look at the mean/median in the channels. Those of your example do look fine, this is normal.
Maybe also switch the saturation display on (red dot button) and verify that the maxima are just single pixels and not extended areas.

Read More...

Dear Alberto,

Did you try to remove the Force Bulb setting on the Indi setting.. ?

I use a XT-4 and I have to turn off the Force Bulb, if on, no chance to work with.

Read More...

Euripides wrote: FYI, I've just had a communication with astroshop.eu and they've informed me that :

The INDI driver for this camera is included in the regular INDI library. You should see the selection for ToupCam and/or Omegon Camera in Ekos when selecting a camera in the profile editor.
(ToupTek and Omegon Cameras are identical, they share the same driver: www.indilib.org/ccds/toupcam-cameras.html )

In addition to that, the same person informed me that he actually uses this camera with a Raspberry PI and Stellarmate with no issues.

So those are good news

My guess is that ASIStudio viewer ignores the white balance (WB) values in ASI camera drivers. Ekos should too but it doesn't. This is actually an issue which must be fixed.
ASI default WB_R=52 WB_B=95 produces twice as much blue in Ekos (and not only in Ekos).
When set to WB_R=50 WB_B=50, the histogram looks as it should (in Ekos).
ZWO software also ignores the offset value (they use some fixed number depending on the camera).

Read More...

Hi folks,

<JonCarleton>

Thanks for sharing your experience .... I have a USB2 powered Hub, but I don't know if I will have the USB3 speed transfer if I use this hub. I'll try it though.

<ThX8411>

When you choose the driver in ekos, I only get the SVBONY or the SVBONY CCD305 (or something similar) . Are there someone more specifics coming out of the 305PRO? Or does the 305's INDI driver already detect whether or not it has tracking? Because I get, in the INDI panel, the guidance menu.

As for the USB2 powered Hub, I have one and I can connect it to USB3 or USB2 but I have a Raspi4.

By the way, the exposure time from 0.001s to 1800s, is it already implemented in any update? And to update only the library and the driver in particular, not the rest of the system , how to do it? (I don't know at all)


I try to do the tests and I'll tell you ...

In the meantime if there is anything else let me know.

Pep

Read More...

Many thanks!
Some settings were missing but now it works fine.

Read More...