I have a theory that modemmanager, although to a lesser degree than with Bluetooth, also interferes randomly with com ports. I haven't had a chance to see if my cable interface is more stable since removing it. But it's worth a shot.

Indeed, I took the step to remove ModemManager from the system about 2 weeks ago when this started happening. Unfortunately, it did not seem to make a difference. I still need to check some connections and voltages to the mount, but am running good wiring and a 10A 12v regulated supply.

Sure go ahead.

I dont know if this is the same issue, but indi_eqmod (Version: 0.4~201802281610~ubuntu16.04.1) is behaving very badly. I have checked all my wiring, power supply is working properly.

See error log below.

regards

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