{actor} created a new topic '...

Hi all

I just purchased a Sesto Senso 2 autofocuser. I reviewed a lengthy thread detailing the development process of the driver and to my knowledge version 1.4 (which I have) should support it - although it was not mentioned in the original thread if this was for the first or second gen of the SS focuser.

Upon connecting to the Pi I saw in dmesg that some other process (pps) was picking up the port:

[   11.052246] pps pps0: new PPS source usbserial1
[   11.052377] pps pps0: source "/dev/ttyUSB1" added

In INDI, seemed as though the port was not available and reported that some other process was using the port - I assumed this was due to the above message and did some searching. I found a couple of threads suggesting that gpsd could be grabbing the port (seems pps is a timing service). I tried killing gpsd with:

sudo killall gpsd

dmesg reports:

[ 1106.059726] pps pps0: removed

Thinking I was onto a winner I then go ahead and test the connection using a profile with CCD simulator, Guide Simulator, Telescope Simulator and the Sesto.

indiserver -p 7624 -m 100 -l .indi/logs -vv -f /tmp/indiFIFO indi_sestosenso_focus indi_simulator_ccd indi_simulator_guide indi_simulator_telescope

I am still getting the same error - actually I just checked and the error is slightly different with gpsd disabled: Previously the error stated the port was in use, now it says:

2020-04-18T20:45:29: [WARNING] Communication with /dev/ttyUSB1 @ 9600 failed. Starting Auto Search... 
2020-04-18T20:45:29: [INFO] Error retrieving data from SestoSenso, please ensure SestoSenso controller is powered and the port is correct. 
2020-04-18T20:45:29: [ERROR] Serial read error: Timeout error.

I went further and fully disabled gpsd by editing /etc/default/gpsd as below:

# Default settings for the gpsd init script and the hotplug wrapper.

# Start the gpsd daemon automatically at boot time
START_DAEMON="false"

# Use USB hotplugging to add new USB devices automatically to the daemon
USBAUTO="false"

# Devices gpsd should collect to at boot time.
# They need to be read/writeable, either by user gpsd or the group dialout.
DEVICES=""

# Other options you want to pass to gpsd
GPSD_OPTIONS="-n"

Reboot, check dmesg - pps is still not grabbing the port - retest - same result. I don't know how to find out which process, if any, might be holding the port, or whether the hardware is just not answering as is suggested in the logs attached. What about the name of the hardware - could it be reporting itself differently (being 2nd gen) and being ignored? I'm sure there might be others using 2nd Gen Sesto Senso and I'd like to hear from you please?

Also is there a better way to test the drivers standalone? I thought I read somewhere of a way to start the drivers up in a standalone configuration for testing but I could not find the resource. I am connecting from a Mac client and set the logging up to the highest (bearable) level both on the server (-vv) and the client. Both logs are attached showing the commands being sent and no response. For this test the device was connected to ttyUSB1 and that's the setting that I started the connection with although EKOS hunts the other available ports.

[    4.735511] usb 1-1.3.1.2: cp210x converter now attached to ttyUSB1

I did connect to a windows machine and ran through the calibration (and updated the firmware) - the hardware is functioning as expected on Windoze.

Sorry for the long post - there's alot of information here - I do hope someone can help!

Cheers
Iain

Read More...