alacant

In between frames, stop tracking for (random) 5s and nudge DEC a tiny amount during.

??? So rolling back to the version which worked, doesn't work?!

Build as many versions as you like. Just choose sensible names for the folders you build into.

INDI code is hosted on GitHub. You can choose any version you like.

The OP reports the same problem on a separate NUC with a fresh install.

👍 If it still doesn't work (it should), just use a Prolific cable and set the port as indicated on first plugging the cable.

Hi Nice shot. You can minimise the effect by choosing a more suitable ROI for second and subsequent AutoDevs and/or just kill it using the Denoise module's large scale slider. @jager945will be able to fill you in on the intricacies of the process. Even better, go again. This time, clean the sensor, lose the dark frames, dither between light frames and stack using a clipping algorithm. Siril is the best I've found for the latter. Then you'll really be able to see the StarTools magic:) Cheers

And what messages did you get? Anything different to the ones I posted? You said you'd already tried it. Many times. What did you use?

Mmm. Specifically this post in this thread. HTH

This one.

Well, the method is described in this thread. The next stage is to use a cable from a member of your local astro club which you will have seen working with indi eqmod previously at one of its gatherings. Cheers

Mmm. So you haven't tried removing the kernel module...

I'm trying to find out why. I've only the snippets of information posted here. No logs, no link to the indi discussion... So all I can do is guess. As you have a working system, maybe just use that:)

tail -f /var/log/syslog **I've edited that post with more detail HTH

OK. Try the traditional route: Disconnect everything on usb. Pull the plugs. before ls /dev/ttyUSB0 ls: cannot access '/dev/ttyUSB0': No such file or directory Unload the ftdi module and tail the log as you plug in the cable. Use the old method of communicating. e.g.: Sep 17 19:58:22 g50 kernel: [ 588.552277] usb 2-2: FTDI USB Serial Device converter now at tached to ttyUSB0 and after: ls /dev/ttyUSB0 /dev/ttyUSB0 Enter the port in the INDI panel: Disable autoconnect in your EKOS profile and connect only the mount. Anything?

Is ftdi loaded? e.g. on one of our 20.04s: lsmod | grep ftdi_sio ftdi_sio 61440 0 usbserial 53248 1 ftdi_sio

<guess> All your three eqdir cables have the same serial converter which Ubuntu doesn't like? We have a dead posh brand-name cable which works with NINA but not with INDI, whilst these cheepo ones work fine with all our sw eqs. under any os. </guess> But really, I'd lose the cable anyway if you have BT working. Cheers ** could you post a link to the indi forum discussion?

Hi Lovely shots. Perhaps one of the best would be dedicated astro software such as Siril. It will not only remove your glow but also much of the burden of ps/gimp/dss. Oh, and a big +1 for flat frames:) Cheers

Hi I'm sure the developers would be interested to know. Even on a modest i3, there is good throughput. Ubuntu though;) Cheers

All we have to work with is that moving your setup from one place to another causes it to fail. As you will have already tried the suggestions in the thread, I guessed location and GPS. Cheers

So not that then.

GPS?

Hi everyone Surprised to see this so high at this time of year. A few minutes before the end of astro darkness, we managed 3 frames before EKOS decided to call time on the night shift. Maybe a good one for those nights when you've excellent seeing between clouds. Cheers 700d on gso203, 3 x 120s