Hello,
lurking in the forum's topics I found that many of you are using an App in the Apple phones to create horizon data to feed to Ekos. I find it really useful so I'd like to do it too to have my backyard horizon well traced. Could you suggest some way to do it using tools commonly found in normal houses? (maybe a compass, at top) ?

Thanks

Luca

Read More...

Thanks knro for your answer.

Setting this value manually to 100.000 seems to be inconsistent as i'm unable to input values bigger than 60000 in kstars's focus panel and I'm unable to set values bigger than 60000 on the preset tab. Plus (and this is strange) focusing module seems to ignore this limit when i hit "focus in" button (which does a steps +=100) and goes on to 65535 steps.

I edited the xml file and can confirm that the value has been saved:
<newNumberVector device="MoonLite" name="FOCUS_MAX">
<oneNumber name="FOCUS_MAX_VALUE">
1000000
</oneNumber>
</newNumberVector>

But I see that what seems to be related to this value is commented out in the code (moonlite.cpp, lines 100-102 @ master).
Is there any other common interface (and arduino code) that should be used in DIY projects instead of the moonlight's one ?

Thanks Again.

Luca

Read More...

Hi and thank you for your answer.
Your reply suggested that it has nothing to do with ekos/kstars so i took the code from github and...it seems that the absolute max position is hardcoded to 60000:

bool MoonLite::initProperties()
{
    INDI::Focuser::initProperties();
   /* removed some lines */
    FocusAbsPosN[0].min   = 0.;
    FocusAbsPosN[0].max   = 60000.;
    FocusAbsPosN[0].value = 0;
    FocusAbsPosN[0].step  = 1000;

    setDefaultPollingPeriod(500);
    addDebugControl();

    return true;

So it seems it was a bad idea leverage moonlight's driver for my diy focuser :(

Modifying the max travel in the indi interface doesn't seems to solve the problem.

Read More...

Hi,
I have built a dit focuser using a nema17 + planetary gear with a ratio of 29, having roughly a 0.00041 mm per step. I'm using the moonlight driver. With this setup, i reach focus at ~ 70500 steps (~ 20.11mm focuser outward). I found that It's impossible to use such a number in ekos/kstars as it has an hard limit on 65535 steps and an interface limit to 60000 (strange number tho...).
I'm not proficient enough to create a pyindi interface and test if the problem is in the driver itself or in the kstars/ekos interface. What do you suggest? At the moment i'm moving to 50000, then set position as 0 and then move again, but this is not a good solution imho.
FYI:
Kstars 3.0.0 and indi 1.7.6

Thanks
Luca

Read More...

Hi!
I have a strange issue lately with my NEQ6 (indi_eqmod). It seems that, even if i (supposedly) correctly polar aligned it, my mount is not "tracking" as I expect it would.
My stars are strips even at 30 seconds exposures and when I try higher exposures, i got this: on astrometry .
I suspect I have something badly configured on kstars and or indi_eqmod.
May you please point me to some debug information or hints?

Thanks
Luca

Read More...

Thank you for your fast answer. I think i'm going to go for the 183MM.
Thanks again.

Read More...

Hello,
i'm valuating a camera which works "well" on indilib and matches both my budget and my expectations. I'm leaving my crappy Qhy 183C (countless nights spent having to reboot after each frame) to either:
* ASI 1600 MM Pro
* ASI 183MM Pro

I'd prefer the 1600 MM Pro as the sensor and pixel size is bigger (4/3" vs 1"). But please, give me advises :)

Thanks
Luca

Read More...

Luca Gervasi replied to the topic 'Re:QHY183M not detected' in the forum. 3 years ago

I was just thinking about buying the same camera. Lucky me got to search in the forum :)

Thanks for sharing your experience!

Inviato dal mio BLA-L09 utilizzando Tapatalk

Read More...

I was not aware of that. Actually I have a udev rule that fxloads the firmware :(
I'll remove it and try right this night (if the sky is available :( )
Thanks!

Read More...