Thank you, I opened the ticket.

Read More...

Here is the log from the EKOS debugger. When I start the profile using the debugger the dome driver did not crash. I think this is because the connection to the dome was not established. I then connected a remote kstars installation to the running indiserver and tried to establish the dome connection in the indi driver panel by clicking connect which forced the driver to crash and as I would guess from the different PID of the indiserver before and after the test, the indi server crashed, too.

Thank you,
Gorden

File Attachment:

File Name: indi_logs_23-08-21T09-02-26.zip
File Size: 5 KB


Read More...

Hi All,
After two years successfully using the stellarmate OS with my configuration I have increasing problems with connecting to my ScopeDome Arduino card (FW version 6.1)
I'm using the LAN interface of the dome and sometimes it needed a couple of attempts to connect which did not concern me that much since it always worked sooner or later.
After I've updated to Stellarmate OS 1.7.8 (indi version 2.0.3) I get a connection only sporadically. The behavior is kind of erratic, sometimes it just works, sometimes the driver crashes immediately and sometimes kstars crashes as well. In some cases the driver stays up but the connection cannot be established and the driver crashes after like 3 or 4 attempts to connect.
I've attached three logs: one succesful connection, one with both driver and kstars crash. One with crashing driver after three connection attempts.
I really love stallarmate and don't want to go back to Windows; any help would be highly appreciated.

CS,
Gorden

File Attachment:

File Name: log_18-41-33_driver_and_kstars_crash.txt
File Size: 73 KB

File Attachment:

File Name: log_17-44-22_driver_crash.txt
File Size: 26 KB

File Attachment:

File Name: log_18-44-56_success.txt
File Size: 298 KB


Read More...

Merry Christmas!
I used some bad weather period to update my StellarMate to INDI server 1.9.3. which worked without any issues. However, after the update I was unable to get the ASI camera to work and I found that the driver is failed to start as soon as the camera (ASI294MM Pro) is connected via USB. It starts okay if I disconnect the camera. The error message is:

2021-12-25T11:06:10: Driver indi_asi_ccd: indi_asi_ccd: malloc.c:4028: _int_malloc: Assertion `(unsigned long) (size) >= (unsigned long) (nb)' failed.
2021-12-25T11:06:10: Driver indi_asi_ccd: stderr EOF
2021-12-25T11:06:10: Driver indi_asi_ccd: restart #1
2021-12-25T11:06:10: Driver indi_asi_ccd: pid=3963 rfd=0 wfd=6 efd=7
2021-12-25T11:06:10: Driver indi_asi_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

This is what I get when I try tu run indiserver -vvv indi_asi_ccd

Can somebody please explain what this message means and what the root cause might be? Is my attempt  to start the driver manually correct at all? And finally, is there a way to fall back to 1.9.2 or replace the driver with the old one?

Any hint would be highly appreciated, thank you.

Cheers,
​​​​​​​Gorden

Read More...

Hi Eric,

I would be grateful for a graphic display of the position of the shutter and the scope similar to the display in the windows driver from Scopedome.
If you need somebody for testing, please let me know.

Best,
Gorden

Read More...

This afternoon I tested the version Jarno pushed on Friday. To cut a long story short: Everything works perfectly now. Parking, slaving, finding home, shutter control...everything works.

Jarno, you did an awesome job. Thank you so much!

Eric, how does it look for you now?

Cheers,
Gorden

Read More...

I had the same behavior yesterday. But when I wanted to repeat the tests with the improved log capability from Jarno's latest push I found everything working okay today. Nobody could could have been more surprised than me.

Gorden

Read More...

Hi,

I have the same behavior when trying to enable slaving or moving to an absolute position. Jarno is working on it already.

Sometimes (not every time) after updating the INDI server I had the same with saving the config. Once I got the message that there was no config even though saving the config was reported to be successful.
What worked for me in these cases:
- disconnect everything and stop the server
- delete (or rename) the config (not the default config) from .indi folder
- start the INDI server, the driver config file is created from the default config.
- connect and repeat the settings, save the config file

Next time the driver is connecting the settings should be applied correctly.

Cheers.

Gorden

Read More...

Eric,

how about movements to absolute positions? Is that working for you? And how about parking and slaving to the mount?

Cheers,
Gorden

Read More...

I've tested the home sensor functionality as well as the shutter successfully last night. Board firmware was 5.7, Scopedome 3M.
Thank you, Jarno for your restless support.

Best,
Gorden

Read More...

Hi Astronerd,
Thank you for this hint. Interesting approach, I didn’t think of that but I will definitely give it a try. Does the direction matter?

Thanks,
Gorden

Read More...

Hi, community.
I recently got an EQ8 and plan to run it with two side-by-side scopes. Due to the double mount, the DEC axis has an offset of 90 degrees. In the hand controller, I can enter that offset after the home position is found. Is there a similar setting in the INDI EQMOD driver? Has that to be considered at all?

Thank you for helping me with that.
Best,
Gorden

Read More...