That is the same error I have been seeing. It seems to happen when I am all set up, tracking and in the main sequence of doing exposures. That may be a coincidence though, as that is where I am spending the most time in INDI/Ekos, of course. I have not been able to find another correlation yet. I was wondering before, when this started happening if there was something being returned from the mount that could be output other than displaying "unknown error"? Even if it is the raw error.

My running INDI drivers:

eqmod
gpsd
zwo ccd (1600MM and 290 mini)
moonlite
astrometry
wunderground
flipflat
asi efw

Can you compile from Github and see if this is perhaps another build issue?

I can try, though this is on the Fedora build, and has been happening for the last few builds, not just the latest one. Petarm is using Ubuntu, so would be yet another build.

I tested EQMod for the last half hour in my observatory and no issues. Another user ALSO had this problem as well, so it is more common but I can't find the source of the issue yet.

I am not able to discern a pattern. I have had it work fine for hours, and then fail 2x in 20 minutes. It looks like I may have some clear nights coming up this week, so will try to better recall what is going on when it happens.

I have seen this happen, but I couldn't be sure if it was my cables or whatnot. I haven't had enough time up and running lately to notice any pattern.

Ok I'd like to know what leading to this. All the logs I got so far either include the error in a separate file (with no history before it) or do not include the error at all. I need logs that are OK until this starts happening.

HI knro. Me too.

I have a funny feeling it's not software rather power supply. I ran off battery with no issues. Then I tried off mains power with one of my 12VDC 2A power supplies. Again no issue. Then I tried another mains power supply and the mount wouldn't connect with the same error.

I just completed a brand new power supply from a computer psu. This should give me the cleanest 12VDC @ 17A. So plenty to run everything cleanly.

If the weather is fine over the weekend I'll log everything from start to finish and send through all my logs if I have any problems with anything.

Will see what happens.

Keep up the awesome work.

Regards

Hi,
the errors look a bit similar to the ones I had about a year ago:
www.indilib.org/forum/mounts/1614-eqmod-...or.html?limitstart=0
I attached a verbose driver log of a full test session back then, maybe that helps:
www.indilib.org/media/kunena/attachments/3593/eqmod_driver.txt
I have not tried it again since then but when I find some time I will check it again and record some logs.

Cheers,
Adam

It looks clear tonight. I will have logging on from the start.

So far, tonight, I have captured >150 frames at 15s Lum, and now 60s Red with guiding the whole time. No issues. This is how it goes.

-- added hours later. A great night. Not a single offline incident the whole evening, tracking, dithering, OAG guiding with the 290MM mini, etc...
The only thing I did different that I can think of is I had full debug logging enabled for the mount/EQmod !

I'll take it. Going to leave the logging on and see if I can get it next time.

Jim

hi krno, so I had some time to try the setup with my new clean power supply. The last time i powered up all my gear everything worked flawlessly and I suggested that all the issues were probably due to poor power supply. Unfortunately i dont think this is true.

Ill summaries the issues i encountered and ill attach all the log files.

So i have not updated my PC or RPi3 indiserver from the previous session when everything worked. My laptop (running ubuntu 16.04LTS) and RPi3 (running ubuntu mate 16.04LTS) dont see the internet at all and are purely dedicated to kstars/astro. I only update these devices when i see you have push updates and new features. I use the offline astrometry solver.

I just set up and started everything as i normally do.

The first issue i encountered was my Shoestring BT dongle would not bind to my laptop, wher ein the past it bound straight away. So I had to remove, re-pair and re-trust it again using blueman. And then it still would not bind. So i used bluetoothctl to pair and trust and it worked. Then when i tried to pair it with the blue-man applet it still would not bind. So i open a terminal and used the following: sudo rfcomm bind 0 XX:16:11:08:57:YY 1 to achieve a bluetooth bind. Finally everything connected ok.

I was able to slew to objects etc and the mount and all the other devices connected via rpi indiserver.

I then went to park the mount and it ended up slewing to China, not back to the South Celestial Pole from there it started. Once i unparked the mount it disconnected and threw the same tty cannot connect error i posted before and the bluetooth disconnected. So i had to shut everything down and start from scratch.

And the same thing as above happened again so i packed up to send this report.

anyway i hope the logs flag what the issue may be.

regards