Yes it was reading it into an unsigned short instead of integer, that should be fixed now. Regarding the 0 to 60000 and back, I don't think it is related to the change. I need to test the driver with my actual moonlite focuser in a couple of days to make sure it didn't break anything.

Hello again.
I've tried the latest version and now it works fine, no negative step values reported.

The other problem I had was probably because the focuser bottomed out before reaching 60000 steps.
When looking a bit closer, my setup has ha max travel around 50000-55000 steps. So it was most likely not software/driver related.

Regards
Daniel

Hello !

hello, I saw a video on the Arduino driver for moonlite has a temperature display. But how should we use it?

Hello all,
As the weather is ugly and waiting for a twinkle of the stars I am working on my motorized focuser.
I based it on the cheapest hardware. I wil upgrade to a higher level hardware if I finally can't make it run.
stepper 28BYJ-48-5
ULN2003A
But for the moment I will try my best to make it run.
I have used the arduino driver proposed here but got a bad result.
For now it doesn't.
First, I need to connect twice because it doesn't work at first.
I obtained this
2016-02-16T21:15:41: Error retreiving data from MoonLite, please ensure MoonLite controller is powered and the port is correct.
2016-02-16T21:15:41: updatePostion error: Timeout error.

Second time I get the control back and connect but after some messages as the following in the terminal:
"Trying to convert empty KLocalizedString to QString."
Kstars crashes.

Got also an unexpected result with a position continuously increasing before crashing on the same previous message.

Have you suggestions ?

Thanks

Hello !

At home it is also ugly. I do not use this driver because it does not manage the temperature and it is not detected properly on Windows by ASCOM drivers.

But I found another:

sourceforge.net/projects/arduinomoonlite...ne/?source=directory

The designer is going a step further and can emulate all the functions of MoonlightFocuser. It would be interesting to see if it is compatible with INDI !

I just understood that the component ULN2003A is different from the one used in the code provided here. So I went to the code you propose dragonlost. I find it before but thought it was too complicated. I tested it as it comes but got bad results so I switch to the one proposed here, with the result I explained.
I am working on a version of the sourceforge (from blackdragon72) after removing the temperature part.
I guess that a modification of the length of the optic system take long (I mean more than an hour) to compromise the focusing. So is the temperature control useful, a focusing sequence wouldn't it be enough between two shots ?
But is this possible with EKOS ?

Hello,
Find here my first adaptation of the ArduinoMoonliteFocuserClone.
It works fine with kstars control panel but make ekos then kstar crash when I switch to the focus tab of ekos.
My components are arduino nano a ULN2003A controller and the 28BYJ-48 stepper motor.
Can you give me ideas for where I have to look at to try to fix this problem ?

Well, make sure you have kstars debug installed.

If it crashes, type bt to get the back-trace and post it here. Also, enable logging

This is the trace back of the crash. Examining this I understand where the problem is. If there is no ccd connected switching to the focuser tab of ekos crash all. Wouldn't be better to have a warning message instead of a crash ?
The other problem is that the connect action fail at first try and succeed at second one.

2016-02-18T10:28:48: Error retreiving data from MoonLite, please ensure MoonLite controller is powered and the port is correct.
2016-02-18T10:28:48: updatePostion error: Timeout error.

A question, if the port is not ttyUSB0 how is it possible to set it to another one when using a remote indiserver ? (I ask it because I note it when unplugging and re-plugging the arduino device increase the number of USB)

TRACE BACK
#0 ISD::CCD::getChip (this=0x0, cType=cType@entry=ISD::CCDChip::PRIMARY_CCD)
at ../../kstars/indi/indiccd.cpp:1426
#1 0x000000000073aa22 in Ekos::Focus::checkCCD (this=0x6536f10,
ccdNum=<optimized out>, ccdNum@entry=-1) at ../../kstars/ekos/focus.cpp:255
#2 0x0000000000711e8a in EkosManager::processTabChange (this=0x5dc0df0)
at ../../kstars/ekos/ekosmanager.cpp:2135
#3 0x0000000000666e4d in EkosManager::qt_static_metacall (_o=0x0,
_c=QMetaObject::InvokeMetaMethod, _id=-200200176, _a=0x0)
at moc_ekosmanager.cpp:276
#4 0x00007ffff406b9c9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffff528aabe in QTabWidget::currentChanged(int) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6 0x00007ffff528ba4f in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7 0x00007ffff406b9c9 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007ffff527bc5e in QTabBar::currentChanged(int) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9 0x00007ffff5281f80 in QTabBar::setCurrentIndex(int) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007ffff5284740 in QTabBar::mousePressEvent(QMouseEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
---Type <return> to continue, or q <return> to quit---
#11 0x00007ffff511e89f in QWidget::event(QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff5288443 in QTabBar::event(QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff50dab2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007ffff50e08eb in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ffff403ac2b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff50df3da in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007ffff5136cc0 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007ffff5138e33 in ?? ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007ffff50dab2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007ffff50e0000 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007ffff403ac2b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
---Type <return> to continue, or q <return> to quit---
#22 0x00007ffff4b1df82 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#23 0x00007ffff4b1fb45 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#24 0x00007ffff4b0434f in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#25 0x00007fffe67d7590 in ?? ()
from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#26 0x00007fffef8a1c3d in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fffef8a1f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007fffef8a1fcc in g_main_context_iteration ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007ffff4093c57 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x00007ffff40383e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007ffff404002c in QCoreApplication::exec() ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x00000000005485e2 in main (argc=1, argv=<optimized out>)
---Type <return> to continue, or q <return> to quit---
at ../../kstars/main.cpp:240

Can you tell me how you start Ekos? what CCD are you selecting? It's not connected when you use the Focus module?

Regarding the port, you can set it and save it under Options tab --> Save Config. But this is also unreliable as the ttyUSBX changes as you noted, I'm writing an article now on how to achieve persistent port mappings.

EDIT: Now fixed in GIT. You can connect focuser only and it will not crash

Good morning Jasem,

I start ekos from tools in kstars. I use either an asi ccd or simulator for testing. And yes in my first tries the cam wasn't in unconnected state.
Thank you for the mod to avoid ekos crash. So it will become more and more robust.

CS
Patrick

I modified the header of the arduino software because it is not fair to tell I am the author. The author is blackdragon72 and I just improved it to make it works with my setup and indi. So this is the modified version.