Dear all,

I am trying to set-up the indi_duino driver along with an arduino uno. To make it short, it works perfectly, but... Only when I am using the IDE to compile firmware for arduino.
When I try to compile StandardFirmata and push it to the arduino with my own scripts, it looks like something is going wrong, but I cannot understand what. (my upload script works perfectly with the firmware generated by the IDE, so it must be something related to compilation).
The bizarre thing is that, apart from firmata all my other firmware are working well (They are much more simple however. but can use serial without problem)
I was wondering if it was possible to understand from the indi_duino logs if there was an option/compile time variable that the IDE was setting and that I would be missing.
I there a chance that it is something related to the behaviour of reset on serial connexion ? that I am setting in my scripts ?

Thank you in advance for your help, here are my indi_duino logs:

<code> CONNECT='On'
2019-06-21T08:19:29: Driver indi_duino: queuing responsible for <newSwitchVector device='Arduino' name='CONNECTION'>
2019-06-21T08:19:29: Client 0: queuing <newSwitchVector device='Arduino' name='CONNECTION'>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<newSwitchVector device="Arduino" name="CONNECTION">
<oneSwitch name="CONNECT">
On
</oneSwitch>
</newSwitchVector>

2019-06-21T08:19:29: Driver indi_duino: sending msg copy 1 nq 1:
<newSwitchVector device="Arduino" name="CONNECTION">
<oneSwitch name="CONNECT">
On
</oneSwitch>
</newSwitchVector>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] State 0 is on'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Connecting to /dev/ttyACM0 @ 57600'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] State 0 is on"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] State 0 is on"/>

2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Connecting to /dev/ttyACM0 @ 57600"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Connecting to /dev/ttyACM0 @ 57600"/>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Port FD 4'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Connection successful, attempting handshake...'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Port FD 4"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Port FD 4"/>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Connection successful, attempting handshake..."/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 2:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Connection successful, attempting handshake..."/>

2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:29: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:29: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:29: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:29" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:30: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:30: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:30: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:30: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:30: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:30: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:30: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:30" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:31: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:31: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:31: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:31: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:31: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:31: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:31: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:31" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:32: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:32: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:32: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:32: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:32: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:32: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:32: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:32" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:33: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:33: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:33: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:33: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:33: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:33: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:33" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:34: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:34: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:34: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:34: Driver indi_duino: read message Arduino '[DEBUG] Sending REPORT_FIRMWARE'
2019-06-21T08:19:34: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:34: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Sending REPORT_FIRMWARE"/>

2019-06-21T08:19:34: Driver indi_duino: read message Arduino '[DEBUG] Handshake failed.'
2019-06-21T08:19:34: Client 0: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 5: queuing <message device='Arduino' name=''>
2019-06-21T08:19:34: Client 0: sending msg copy 2 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Handshake failed."/>

2019-06-21T08:19:34: Client 5: sending msg copy 1 nq 1:
<message device="Arduino" timestamp="2019-06-21T08:19:34" message="[DEBUG] Handshake failed."/>

2019-06-21T08:19:34: Driver indi_duino: read setSwitchVector Arduino CONNECTION Alert
CONNECT='Off'
DISCONNECT='On'
2019-06-21T08:19:34: Client 0: queuing <setSwitchVector device='Arduino' name='CONNECTION'>
2019-06-21T08:19:34: Client 5: queuing <setSwitchVector device='Arduino' name='CONNECTION'>
2019-06-21T08:19:34: Client 0: sending msg copy 2 nq 1:
<setSwitchVector device="Arduino" name="CONNECTION" state="Alert" timeout="60" timestamp="2019-06-21T08:19:34">
<oneSwitch name="CONNECT">
Off
</oneSwitch>
<oneSwitch name="DISCONNECT">
On
</oneSwitch>
</setSwitchVector>

2019-06-21T08:19:34: Client 5: sending msg copy 1 nq 1:
<setSwitchVector device="Arduino" name="CONNECTION" state="Alert" timeout="60" timestamp="2019-06-21T08:19:34">
<oneSwitch name="CONNECT">
Off
</oneSwitch>
<oneSwitch name="DISCONNECT">
On
</oneSwitch>
</setSwitchVector></code>

I have installed the stellarmate on raspberry one week ago and I tested the ekos and kstar tools. I have a focuser developed with the Arduino and Motorshield board to control the stepper in the ASCOM environment. Now I would like to move this in the INDI. I have read some indi drivers are available, but I am not understand where I can retrieve the correspondent Arduino code for the specific indi driver (for example moonlite, etc.. ). Can you help and suggest me a solution, please?

I have experience with ASCOM and I am beginner on stellar mate. In ASCOM the user can generate a stars model so that when the telescope is switched on, at the first pointing the object is more or less in the CCD FOV. With stellarmate I have to perform the star alignment every time in different nights because the first telescope pointing error is always quite relevant. I am wondering if there is stellarmate a mechanism like ASCOM stars model or if this is my poor knowledge and I don't apply some flags or procedure.

Hi,

I've seen it already several times, but wasn't sure if I did something weird. For sure I didn't yesterday. This is what happened:
I had created a sequence in the camera tab of EKOS (+ button) that was supposed to take 120 frames of 30s each.
After a while I thought I'll go for a refocus and wanted to pause the sequence. So I pressed the pause button below the sequence table display. What now happened perplexed me:
It would finish the current exposure.
Then the activity display (text next to the exposure) told me 'Aligning'. From the beep I gather it did a (successful) plate solve. Why? After that, it <strong>continued</strong> to take frames.
The two buttons (stop and pause during a running sequence) had changed to play and pause, with pause greyed out and inactive. Pressing play <strong>aborted</strong> the sequence.
Looking at the log file, after pausing it executed a meridian flip! The target (Coat Hanger Asterism) was many hours before being even close to the meridian!? (rise 20:50, transit 3:37, time of the event 22:32). I had not even activated any automatic meridian flip activity... What's going on there?

My steps to get Kstars/Ekos running on an <strong>Odroid-N2</strong>. I hope this might be useful to someone else. My apologies in advance if I lead you astray.

First of all, a thanks to spartacus for all his help in getting to this point.

I probably have left out some steps, but this approach appeared to work for me. The only thing I’m missing is creating a stand alone wi-fi AP access point in lieu of my local wi-fi network (and the automatic selection of that network, if no local network is found).

The Odroid-N2 is <em>fast</em> (6 cores) with <em>lots</em> of RAM ( I chose the 4 G RAM model). This has solved my apparent problems with my RPi3B+. Stellarmate on the other hand is much easier to get going.

http://hardkernel.com/Hardkernel.com odroid official release ubuntu-18.04.2-4.9-mate-odroid-n2-20190325.img.xzubuntu-18.04.2-4.9-mate-odroid-n2-20190325.img.xz
I wrote this to a 32G eemc card using balenaEtcher.

Power on, wait until it stops blinking, unplug, power on again with keyboard, mouse, HDMI.

<code>sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
</code>
I installed synaptic, but of course it’s optional.
<code>sudo apt-get install synaptic
</code>
<code>sudo apt-get install indi-full
sudo apt-get install kstars-bleeding</code>

<strong>Wi-FI Installation</strong>
For the USB wi-fi adapter I chose (listed below) and as described in ubuntuforums.org/showthread.php?t=2394372&page=3

<code>export ARCH=arm64
sudo apt update
sudo apt install -y git
git clone github.com/EntropicEffect/rtl8822bu.git
cd rtl8822bu
make
sudo make install
sudo modprobe 88x2bu
</code>
Note that when Update Manager offers a newer kernel version you must recompile after the requested reboot:
<code>cd rtl8822bu
make clean
git pull
make
sudo make install
sudo modprobe 88x2bu
</code>
<strong>autologin</strong>
It appears we must enable autologin to enable remote login via NoMachine before remote desktop access.
<code>sudo nano /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[Seat:*]
greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session
autologin-user=odroid
</code>

<strong>NoMachine Remote Access</strong>
I had a problem with VNC tightvnc keyboard mapping, and install issues with TeamViewer. NoMachine worked nicely. Use the V8 ARM version if you want to give it a go. www.nomachine.com/download/linux&id=30&s=ARMwww.nomachine.com/download/linux&id=30&s=ARM

<strong>Bonjour discovery</strong>
sudo apt-get install avahi-daemon avahi-autoipd

<strong>SAMBA sharing via SMS</strong>
Follow this guideline if you would like to configure simple desktop network access to the odroid.
www.computerbeginnersguides.com/blog/201...18-04-bionic-beaver/

<strong>GPSD</strong>
I have this GPS unit
Stratux Vk-162 Remote Mount USB GPS

<code>sudo apt-get install gpsd
</code>
I downloaded this script (thank you Rob Lancaste)
https://github.com/rlancaste/AstroPi3/blob/master/udevRuleScript.shhttps://github.com/rlancaste/AstroPi3/blob/master/udevRuleScript.sh
<code>chmod +x udevRuleScript.sh
# execute the script to identify the GPS device
./udevRuleScript.sh
</code>I chose to leave out the serial number in the ID.

<strong>Astrometry.net</strong>
<code>sudo apt-get install astrometry.net</code>
I transferred the data files from the Mac manually onto the Odroid, as I had problems with file permission using the built-in index file loaded inside kstars.

<strong>Device used for wi-fi USB</strong>
Realtek RTL8812BU USB WiFi Adapter 1200 Mbps 5dBi Antenna AC1200 Dual Band 5.8GHz 2.4GHz WiFi Dongle IEEE 802.11 a b g n ac for Laptop Desktop PC USB 3.0 Network Adapter Support Windows 10/8/7 Mac
www.amazon.ca/Realtek-RTL8192AU-Wireless...ntenna/dp/B078NSSM7W

<strong>Network for USB 2</strong>
Micro usb 4 port hub used on the OTG micro port to amerliorate issues with USB 2/3 on the built-in ports.
www.amazon.ca/gp/product/B01JL837X8/ref=...00_s00?ie=UTF8&psc=1

Cheers

Hi, I am a beginner on EKOS-KSTAR, but I know ASCOM. After the alignment task, I would like to know if stellarmate saves the alignment points in the star model like ASCOM, because each time I switch on the telescope, I have not the searched star into my CCD FOV, but I have always to start the alignment procedure. Can you explain me, please?

Hi everyone - because pictures are always better than descriptions, I'll be brief and ask for advice on the solution:


Stellarmate said that it is possible with the USB Serial Adapter to control the goto of the Star Navigator NG 125 with the PC or Stellarmate.
So far I have not even been near such a possibility. Enclosed you can also see my results in the other pictures:

So I've connected the cable to the hand box (Tip from Astroshop) but no matter what you set as the Stellarmate, it does not move at all

in the meantime I do not bother anymore because nothing really works anybody some ideas?

I’m running Kstars version 3.2.2 on my Macbook (macOS Mojave 10.14.5) that is connected to a Stellarmate, running on a Raspberry Pi.

The Raspberry Pi is connected to my Star Watcher EQ6-Pro mount through a USB/D-sub 9 pin cable bought at a specialized store.

Setup:
- mount is polar aligned, usual observation site coordinates: 48.767122, 1.539318,
- mount is set to the home position.

Preliminary tests:
- While operated through the SynScan handheld control provided with the mount, once the initial setup is done (coordinate, time, etc.), I’m able to 3-star align the mount and to goto to various objects afterwards, with only small corrections needed.

- While operated using Kstars on the Macbook through the Raspberry Pi, after having set the geographical position accordingly and checked the date & time, I’m able to slew the mount from Kstars.

Issue:
When the mount is connected to the Raspberry Pi, there is no way I can goto any object. Any object that I select will make the scope pointing to a completely different position. I explored a possible date and time mismatch, but this is not the cause for the scope will point in a direction where the target object cannot be. For instance, when instructed to goto the Moon, it would point a direction that is definitely not on Moon’s path, no matter the date.

The mount will go back to the home position if the Park button is pressed on Kstars.

I considered the possibility of a geographical coordinates mismatch, but the location selected in Kstars matches the current position of the mount. I have tried to select the city of Paris that is 50 kilometers straight east, which shouldn’t make a huge difference, but with no avail.

I’m at my wit’s end here and I wonder if someone may have some pointers for me…

Back in my Meade DSI CCD imaging days, the Meade software featured automatic live still-frame stacking (as well as saving the individual frames). It was magical how a faint DSO would slowly grow and appear on my laptop screen while sitting outside shooting and it inspired me to keep shooting more frames, adding more time. It REALLY added interest and fun to what can otherwise be a rather boring process of capturing still frames. I think it would be a fantastic addition if live stacking were added!

I forgot to log, but the SkyWatcher AltAz driver did not work with the new version.
(Connected via a direct cable.)

There is no problem with the connection, but it can not be operated from Ekos's mount controller, nor can Slew.

The same was true with the EQMod driver.

It works when you change to an older version of the image.

Since the driver itself does not seem to change, updating Ekos may be a problem.

Would be great to get the information about pier side from the iEQ driver. The mount seems to have it (at least my CEM60EC).
It really is sad having such a quite high-level mount and still have to flip calibration in PHD2 manually

Hello guys!
Thank you very much for your continous efforts that made the Kstars platform the most powerful, in my opinion.
I've to highlight a problem that occurred to me running Ekos with the simulator in my system.
I use Kstars-Ekos with my MacBook Pro (Late 2013) with 2 x 2.6 GHz Intel Core i5 and a 8 GB 1600 MHz DDR3 memory. The OS is Mojave (v. 10.14.4).
Starting to run the Simulator the software crashes. I've not idea if this problem also occurs with my telescopes configurations owing to the fact that I will be far away from home for a long time and I've not the possibility to test this issue.
Any suggestions?

Regards,

F.

Quick background: I don't have a go-to mount but I use KStars/Ekos to visualize where the scope is pointing after a plate solve using Telescope Simulator.

The telescope simulator's icon (bull's eye with cross hairs) syncs after a plate solve but then immediately starts drifting eastward. To stop it I have to click on KStar's menu: Pointing -> Engage Tracking. The annoying thing is I have to Engage Tracking quite a lot. I tried INDI control panel settings but found nothing there that had any effect. There could be some setting in KStars that I am unaware of.

So this was just a minor annoyance until recently when I began doing photometry where AIRMASS (in the FITS header) is important.

I just discovered that when Ekos captures a frame it writes these keywords in the FITS header: OBJCTRA, OBJCTDEC, RA, DEC, and AIRMASS. The problem is that the values are coming from the Telescope Simulator, not the last Plate Solve! That means that if I don't engage tracking in KStars and then start a 10 frame capture sequence, the position of the object changes with each new frame.

Is there a way to permanently turn on tracking?

Thank you.

I've just installed KStars/EKOS v3.3.1 and quickly tried to connect to the "simulators" profile, it immediately crashes. This is consistent in the few attempts I have made to start it. I am running OSX v10.14.3.

Is anyone else seeing this same problem?

I've not had the chance to test v3.3.1 on my full imaging rig yet due to weather.

I had no idea this was to be released this year..up to 4gb and USB 3...
thepihut.com/products/raspberry-pi-4-model-b

Hello,
I recently noticed some odd behavior. When I set the temperature of my QHY8L in Ekos to lets say -20C, the cooler will be started and the temperature will decrease until it display - 19.8C.
As soon as the target temperature +- a margin of 0.2C is reached, everything stops. The driver stays at the cooling level of lets say 45.5%, the displayed temperature stays at 19.8C and nothing is changed for the rest of the night.
But the real temperature of the sensor does change, due to server factors, like changing outside temperature etc.
So if you check some minutes later, maybe by changing the target temperature from e.g -20 to -19, a new measurement is triggered displaying -23C or something else, way off. It will then heat up to -19.2C and then stop again, until the next external trigger occurs.
So the effect is in short: Once the target temperature is reached, all temperature regulation stops and the cooling level stays the same forever.


I assume, that the core of this problem is in the QHY SDK, but the INDI Driver might be able to work around this by checking the desired and actual temperature every minute or so and trigger a new regulation?

Regards

Dirk

Trying to get the most of Jupiter and take as many shots as fast as I can, I had the thought...

Why not same my images to the camera's memory. I have 64gigs there and it's easier to get to the chip to sneaker network to my PC for post work (to get the images off my Pi I have to unplug one of my USB devices to insert a memory stick for transfer). It's should also be much faster since it doesn't have to transfer the image to the Pi.

What are the steps I'm missing?

1. Capture Target: changed to "SD Card"
2. Uploa...tings: Dir: I've tried \DCIM\CANON But no luck and I get: [WARNING] Could not wait for event.

On EKOS
1. Upload: Local (with the above directory with no luck)

I managed to download the image and flash without issues on a MacBook Pro. The iOS app finds the StellarMate, and I plug in my info with license information and Stellarmate website login information. Then it just sits there spinning wheel without ever connecting. However, I can go to the Device tab and see system information for the Stellarmate. I'm able to connect to VNC, and I switched to my home network and tried reconnecting. Same issue where it spins forever and doesn't connect. I've tried removing and reading the Stellarmate device from the iOS app, and it doesn't make a difference. It will still show system information under the Device tab.

I'm able to get in to the device with VNC and see the desktop. KStars is loaded by default. Not sure if it's supposed to do that, as it didn't with prior StellarMate versions. Anyhow, I was able to configure the server, and connect to it from my Mac Desktop using EKOS and tested the simulators. However I'm still unable to access the StellarMate from the iOS app or use EKOS there. When I select EKOS it says that it seems to be offline, and it asks me if I started an equipment profile. Which I can't seem to do from the iOS app.

Atik driver does not fill CCD.FILE_PATH.FILE_PATH after recent update but Simulator does.

cherno