Hi Jasem,

Yes, I understand this process, so the warning is only issued when the device is already taken.
What I also see is failure to synchronize with the NEQ6 controller via the serial interface, I suppose this message is issued only after obtaining access to the serial device?
In that case, the warning might be caused by me hitting the Connect button, while the EQMod driver was still in the process of synchronization with the controller: I should leave it alone...

My conclusion therefore is that there are actually HW issues, since sometimes the connect actually succeeds: time to get my oscilloscope out.

Thanks,
Arjan

Read More...

I experience the same problem, intermittently. I am using a direct serial interface on the Pi board, UART5 to be precise, mapped to ttyAMA1. This port is hardwired to the NEQ6 controller board, through level converters. Another port, UART0, is used for GPS and is mapped to ttyAMA0.

The error I get is: "Port /dev/ttyAMA1 is already used by another driver or process."

What I would like to know to help me debugging is what exactly is causing the software to output this message?

The problem may be HW related, but could equally well be an Ubuntu/Raspberry driver issue.

Thanks,
Arjan

Read More...

Alex,

Are you still getting the Ubuntu hack from the James Chambers source?
I saw on the Ubuntu site ( ubuntu.com/download/raspberry-pi ) that regular 32bit and 64bit server builds (18.04.04) for Pi4 are up for download.

Cheers,
Arjan

Read More...

Remove the netplan stuff, it is in the way when you just want to use ifupdown and /dev/network/interfaces to control your networking.

I did it like I described here: http://atm.udjat.nl/stepper/Remote%20Control%20-%20EN.pdf

Read More...

Thanks!

As you know, the Pi4 has reshuffled the connectors, so I had to print a new front for this box. I will include the correct images when I make the final version, after testing full functionality.
On AliB you can find many step-down converters. The one I used is sealed and converts 8-52 down to 5V at 3A. For the Pi4 it is plenty, but I'm not sure about the USB peripherals.
For the Canon I found a battery adapter. When empty it has plenty space to add electronics to convert the 12V down to 7.2 or so.
I really should add some fuses to the 12V outlets, especially for the case I use a battery instead of net power supply.

I attach the box with velcro to the RA housing of my NEQ6, all that is left routing off-mount is one power cable!

Cheers,
Arjan

Read More...

For those who want to install the whole setup on a Pi 4, I have updated my step-by-step description:

No, I wasusing 2.9.8 from the latest stable build....
Could it be that this has the same issue?

Read More...

Thanks, I will try in the weekend.

Read More...

Just reinstalled my EKOS/KStars/INDI on Ubuntu on RPi3 according to this , but when I start my photo session and want to preview what's actually in view, often the FITS viewer crashes and brings down KStars and INDI as well.
What can this problem be? I doubt it is a memory problem since I have many 100s of MB left over.
Closing the preview window (if it hasn't crashed yet) also takes a long time, tens of seconds.

Possibly related question: When INDI is started from KStars, should I use local, client or both for image storage? I remember there was a -m 200 option needed for the comms to the (Canon) camera driver, is this still the case?

Cheers,
Arjan

Read More...

Not sure if it is related, but when I close the CCD preview window, EKOS/KStars/Indiserver crash.
This happens after I updated everything yesterday, presumably including the new driver...
I am running everything on a Pi3, did not get to viewing the post mortem logs.

Read More...

Not sure what I am dong wrong, this used to work fine before...

Setup is EKOS/KStars/Indi running on a Pi3 (Ubuntu 16.10); EQMod mount (NEQ6) and a Joystick.
When all is tracking nicely I get to the eyepiece and fine tune where it is pointing with the joystick. Doing this, the tracking stops immediately and I can only slew.
Looking in the EKOS EQMod tab, I see that Tracking indeed is switched off.

Is there a setting I accidentally hit, that determines this behavior?
If not, what else can be causing this?

Thanks,
Arjan

Read More...