Closed grisu-112 closed 10 months ago
Happy new year to you to! :)
There are two surprising issues - the first one is that the log shows, that ESGv! command doesn't reply anything and the second one is that in "ESGvES20A01.1 Release 2021.08.08: ES1A01CB20A01, ESP8266, DST4!" reply is no mount identification. What mount is it?
I'll need to upgrade my PCM-8 to find what's going on :(
Hi,
I was also surprised and a bit overwhelmed as it is my first electronic mount and the feedback on "ESGv!" does not match the feedback given in the Programmer's Reference (DOC-ESPMC8-002 Release 2 2019_March 07).
Sorry! The mount is of type EXOS-II.
The firmware has to be universal now. I assume that e.g. the trace rates can be read out, so that no type would have to be read out via "ESGv!
I hope you can solve this.
To be honest, I think that the new firmware is broken :( The serial port either doesn't work at all or it reboots each time it is connected, that's why it doesn't connect, it needs some time to boot and to eat the splash screen.
Oh, you're right. I haven't noticed that yet. After the splash screen, the version query and further communication seem to be successful. (At least, it looks like that to me.) Could it be a solution to repeat the version query ("ESGv!") after say 10 seconds, without disconnecting after the first failed attempt, before the connection attempt is considered as failed? This should work equally well for both old and new firmware versions.
Yes, I'll do it. I'll also new mount type detection (for firmware 2+) and the possibility to do it manually if needed.
Pls. can you try it now? c90c7565b00e406db9be72fd2926c80002503f69
I made some more changes to handle some slewing inaccuracy...
I apologize for the following question (my programming skills are pretty rusty):
I have installed indigo-sky (SD Image) and now downloaded the source code from github.
Do I now need to run make all
and replace indigo_mount_pmc8 (under /usr/bin) with the version from the build directory (build/drivers)?
Hm, it may be quite complicated on the pre-configured indigo-sky image :(
sudo apt-get install build-essential autoconf autotools-dev libtool cmake libudev-dev libavahi-compat-libdnssd-dev libusb-1.0-0-dev libcurl4-gnutls-dev libz-dev git curl bsdmainutils
systemctl stop
make all
build/bin/indigo_server -vvv
Am I right @rumengb ?
Hello Peter,
Thanks for the tutorial. I was able to start the build and could see the new driver in the indigo control panel now.
But, unfortunately the serial connection still does not work.
By running from staging area I got the following log in the stdout:
18:34:23.066261 indigo_server: indigo_mount_pmc8: Connected to /dev/ttyUSB0
18:34:24.178738 indigo_server: indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
18:34:24.178836 indigo_server: INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
18:34:24.179258 indigo_server: 21 ← { "message": "Retrying connection in 10 seconds..." }
18:34:35.291877 indigo_server: indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
18:34:35.291982 indigo_server: INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
18:34:35.292533 indigo_server: 21 ← { "message": "Retrying connection in 10 seconds..." }
18:34:46.405294 indigo_server: indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
18:34:46.405404 indigo_server: INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
18:34:46.405794 indigo_server: 21 ← { "message": "Retrying connection in 10 seconds..." }
18:34:56.406000 indigo_server: indigo_mount_pmc8[pmc8_open:185, 0xb32b53c0]: Failed to initialize to /dev/ttyUSB0
18:34:56.408734 indigo_server: indigo_mount_pmc8: Disconnected from /dev/ttyUSB0
Does the port really exist?
Hm, sorry, it does, it is connected...
I'll test it on RPi tomorrow...
Hm, just recompiled everything on RPi4 with indigosky image and it just works. I tried to connect and disconnect couple of times. Are you sure the cable is OK? I have similar symptoms with a broken cable, it sometimes worked and sometimes didn't :(
Another possibility is that it is somehow related to EXOS2, I have only iEXOS100.
Hi Peter,
Thanks for your test. I reinstalled my RPI today based on the latest Indigo Sky image and compiled the latest source code on it as well.
Unfortunately the result did not change.
I hope that only the cable is defective and not the PMC-8, although it does surprise me that the communication with both the Serial Monitor of the Arduino IDE (on Ubuntu) and with the programs available at ES (on Windows) worked but did not with other programs like Putty, Microcom or Indigo.
I just ordered other cables and will post my results here (probably not until the weekend).
Just saw that you are using the EXOS-100. This mount has a built-in FTDI (or similar). That means you are using a simple USB cable. The EXOS-2 has a RS-232 interface. Therefore I have to use an adapter cable. So it could possibly be an incompatibility of the chip installed in this adapter cable with some setting used/set by the affected programs. I will report after testing the ordered adapter cables.
I can confirm that my EXOS-2GT also has this problem. I have tried both the latest version of Indigo Sky (2.0.0.3) and Indigo Control Panel (2.0.0.4). Below is the output from Indigo Control Panel.
12:54:59.928 INDIGO Bus: property update
12:54:59.928 'Mount PMC Eight'.'MOUNT_TYPE' SWITCH rw Ok 2.0 0 OneOfMany {
12:54:59.928 'G11' = Off
12:54:59.928 'TITAN' = Off
12:54:59.928 'EXOS-2' = On
12:54:59.928 'iEXOS-100' = Off
12:54:59.928 }
12:55:10.143 INDIGO Bus: property change request
12:55:10.143 'Mount PMC Eight'.'DEVICE_PORT' TEXT UNDEFINED Idle 2.0 0 {
12:55:10.143 'PORT' = '/dev/cu.usbserial-AM6ESVN9'
12:55:10.143 }
12:55:10.143 INDIGO Bus: Change request - Device 'Mount PMC Eight' token 0x0, Proprerty 'DEVICE_PORT' token 0x0
12:55:10.143 24 ← <newTextVector device='Mount PMC Eight' name='DEVICE_PORT'>
12:55:10.143 24 ← <oneText name='PORT'>/dev/cu.usbserial-AM6ESVN9</oneText>
12:55:10.143 24 ← </newTextVector>
12:55:10.143 INDIGO Bus: property update
12:55:10.143 'Mount PMC Eight'.'DEVICE_PORT' TEXT rw Ok 2.0 0 {
12:55:10.143 'PORT' = '/dev/cu.usbserial-AM6ESVN9'
12:55:10.143 }
12:55:16.454 INDIGO Bus: property change request
12:55:16.454 'Mount PMC Eight'.'CONNECTION' SWITCH UNDEFINED Idle 2.0 0 UNDEFINED {
12:55:16.454 'CONNECTED' = On
12:55:16.454 }
12:55:16.454 INDIGO Bus: Change request - Device 'Mount PMC Eight' token 0x0, Proprerty 'CONNECTION' token 0x0
12:55:16.454 INDIGO Bus: property update
12:55:16.454 'Mount PMC Eight'.'CONNECTION' SWITCH rw Busy 2.0 0 OneOfMany {
12:55:16.454 'CONNECTED' = On
12:55:16.454 'DISCONNECTED' = Off
12:55:16.454 }
12:55:16.528 timer #0 (of 1) used for 0s
12:55:16.528 timer callback: 0x113fd4d60 started
12:55:16.528 indigo_mount_pmc8: Connected to /dev/cu.usbserial-AM6ESVN9
12:55:22.007 indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
12:55:22.007 INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
12:55:22.007 Retrying connection in 10 seconds...
12:55:37.562 indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
12:55:37.562 INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
12:55:37.562 Retrying connection in 10 seconds...
12:55:53.114 indigo_mount_pmc8[pmc8_command:246]: Command ESGv! failed
12:55:53.114 INDIGO Bus: message sent 'Retrying connection in 10 seconds...'
12:55:53.122 Retrying connection in 10 seconds...
12:56:03.118 indigo_mount_pmc8[pmc8_open:185, 0x70000d6a5000]: Failed to initialize to /dev/cu.usbserial-AM6ESVN9
12:56:03.118 indigo_mount_pmc8: Disconnected from /dev/cu.usbserial-AM6ESVN9
12:56:03.118 INDIGO Bus: property removal
12:56:03.118 'Mount PMC Eight'.'MOUNT_INFO' TEXT ro Ok 2.0 0 {
12:56:03.118 }
12:56:03.154 INDIGO Bus: property removal
12:56:03.154 'Mount PMC Eight'.'GEOGRAPHIC_COORDINATES' NUMBER rw Ok 2.0 0 {
12:56:03.154 }
12:56:03.177 INDIGO Bus: property removal
12:56:03.177 'Mount PMC Eight'.'MOUNT_LST_TIME' NUMBER ro Ok 2.0 0 {
12:56:03.177 }
12:56:03.197 INDIGO Bus: property removal
12:56:03.197 'Mount PMC Eight'.'MOUNT_PARK' SWITCH rw Ok 2.0 0 OneOfMany {
12:56:03.197 }
12:56:03.232 INDIGO Bus: property removal
12:56:03.232 'Mount PMC Eight'.'MOUNT_SLEW_RATE' SWITCH rw Ok 2.0 0 OneOfMany {
12:56:03.232 }
12:56:03.251 INDIGO Bus: property removal
12:56:03.252 'Mount PMC Eight'.'MOUNT_MOTION_DEC' SWITCH rw Ok 2.0 0 AtMostOne {
12:56:03.252 }
12:56:03.270 INDIGO Bus: property removal
12:56:03.270 'Mount PMC Eight'.'MOUNT_MOTION_RA' SWITCH rw Ok 2.0 0 AtMostOne {
12:56:03.270 }
12:56:03.289 INDIGO Bus: property removal
12:56:03.289 'Mount PMC Eight'.'MOUNT_TRACK_RATE' SWITCH rw Ok 2.0 0 OneOfMany {
12:56:03.289 }
12:56:03.308 INDIGO Bus: property removal
12:56:03.308 'Mount PMC Eight'.'MOUNT_TRACKING' SWITCH rw Ok 2.0 0 OneOfMany {
12:56:03.308 }
12:56:03.326 INDIGO Bus: property removal
12:56:03.326 'Mount PMC Eight'.'MOUNT_ON_COORDINATES_SET' SWITCH rw Ok 2.0 0 OneOfMany {
12:56:03.326 }
12:56:03.345 INDIGO Bus: property removal
12:56:03.345 'Mount PMC Eight'.'MOUNT_EQUATORIAL_COORDINATES' NUMBER rw Ok 2.0 0 {
12:56:03.345 }
12:56:03.363 INDIGO Bus: property removal
12:56:03.363 'Mount PMC Eight'.'MOUNT_HORIZONTAL_COORDINATES' NUMBER ro Ok 2.0 0 {
12:56:03.363 }
12:56:03.383 INDIGO Bus: property removal
12:56:03.383 'Mount PMC Eight'.'MOUNT_ABORT_MOTION' SWITCH rw Ok 2.0 0 AtMostOne {
12:56:03.383 }
12:56:03.402 INDIGO Bus: property removal
12:56:03.402 'Mount PMC Eight'.'MOUNT_EPOCH' NUMBER ro Ok 2.0 0 {
12:56:03.402 }
12:56:03.421 INDIGO Bus: property removal
12:56:03.422 'Mount PMC Eight'.'MOUNT_SIDE_OF_PIER' SWITCH ro Ok 2.0 0 OneOfMany {
12:56:03.422 }
12:56:03.444 INDIGO Bus: property removal
12:56:03.444 'Mount PMC Eight'.'SNOOP_DEVICES' TEXT rw Ok 2.0 0 {
12:56:03.444 }
12:56:03.465 INDIGO Bus: property update
12:56:03.466 'Mount PMC Eight'.'CONNECTION' SWITCH rw Alert 2.0 0 OneOfMany {
12:56:03.466 'CONNECTED' = Off
12:56:03.466 'DISCONNECTED' = On
12:56:03.466 }
12:56:03.498 timer callback: 0x113fd4d60 finished
12:56:03.499 timer #0 done
While googling about this issue, I found this comment in INDI driver implementation:
I'll try to clear DTR on connect, but the unwanted side effect will be the mount reset :(
Pls. can you try it with this commit f70cdf9b2c923361ec851cc4f989b2a78683427f?
Make sure you set "Connection mode" to "Serial (clear DTR)" before trying to connect with a control panel. If it will work for you, you can make selection persistent with "Configuration control" > "Save".
Finally got around to trying this and it seems to work, as far as I can tell. Once it connects, I get a stream of successful "ESG" commands in Indigo Server.
👍
Wish you a happy new year 2022!
I am trying to connect to a new PMC-8 via serial port.
indigo.log says
indigo_mount_pmc8[pmc8_command:198]: Command ESGv! failed
A connection can be established and the mount controlled via a terminal program. Therefore I assume that the FTDI based USB-RS232 cable is working.
I retrieved the following TTY settings using the console command
stty -a -F /dev/ttyUSB0
Working terminal session:
Non-working INDIGO serial connection attempt:
Used Configuration: INDIGO-SKY (Build downloaded in the last three days) updated to 2.0-166. PMC-8 with newest "Universial Firmware" (ESGv! Result:
ESGvES20A01.1 Release 2021.08.08: ES1A01CB20A01, ESP8266, DST4!
).Full indigo.log (Trace-Level):
My search on the forum and on the search engine were unsuccessful. I am a beginner regarding INDIGO and hope to have given all the important information.
Greetings from Germany. Chris