Chris Rowland replied to the topic 'ZWO Camera ASI 120MM Mini Mono with StellarMate?' in the forum. 5 days ago

Same for me, my ZWO ASI120MM Mini just works on both Windows and INDI.

My Altair GPCAM MT9m034M Mono is a different story, it's never worked on INDI and while it used to work on Windows now, with the latest driver updates, it doesn't. This is a rebadged ToupTek camera and neither Altair not Toupteck have shown the slightest interest in sorting this. Rumour has it that it depends on the type of hardware, some work and some don't.
Altair and Touptek have been added to the list of companies I won't buy anything from that uses electricity.

Read More...

Chris Rowland replied to the topic 'myFocuserPro or myFocuserPro2 and INDI' in the forum. 6 days ago

Would it be worth being generous about what is accepted?

Take the string sent, remove the leading ':' and the trailing '#' and parse what is left as a decimal integer.
It could accept :8#, :08#, :008# and so on.
That way the code can be agnostic about the version of the code on the other side.

Chris

Read More...

Chris Rowland replied to the topic 'Celestron CGE Pro - Ekos/Indi Won't Track' in the forum. 6 days ago

Nothing obvious wrong.
One thing that's essential is a log file showing the communication with the mount. Set the driver logging to verbose and to file, save the properties and restart. This should get the communication information to the log.
Also Exactly what HC version are you using? Read from the HC.
Certainly try the NS+ HC.
If you want to try this indoors or when it's light try a quick align. This needs no stars, just the mount set to the align position.

Read More...

Chris Rowland replied to the topic 'Setting developpement environment' in the forum. 1 week ago

I managed to get this going, the problem was that I was using the wrong build directory.
I started by following the console build steps in the Setting Development Environment, slightly modified because of the repository split:

mkdir -p ~/Projects/build/indi
cd ~/Projects/build/indi
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ~/Projects/indi
sudo make install
This worked. I then reviewed the Build Settings in the qtCreator project and set the build directory to /home/chris/Projects/build/indi
And that did the trick, compile and install.

Chris

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 1 week ago

EQMod is for Skywatcher mounts, not Celestron isn't it?

The Skywatcher mounts operate in the same way, an internal bus that connects the HC to the axis motors and only handles low level commands such as axis pposition, move to axis position, move axis at a fixed rate. EqMod communicates directly with this bus, replacing the functionality of the HC.

AFAIK no one has done a version of EqMod that will handle the Celestron mounts but in theory it should be possible. There is also a 3rdParty NexStar Evolution driver that atempts to communicate with the motors directly and handles the mount alignment model. I don't think it has been implemented for equatorial mounts, just Alt Az.

Chris

Read More...

Chris Rowland replied to the topic 'Setting developpement environment' in the forum. 1 week ago

I've also been trying to build indi. This is with a Pi4 running Raspbian and with EKOS etc. installed usug the AstroPi script. This worked, including clonin and building EKOS INDI and 3rdParty.

Installed QTCreator, cloned the sources following the instructions as much as posssibly allowing for QTCreator having changed its UI again and the split of libindi and 3rdParty.

QtCreator sems to run fine but kdesudo doesn't
Messages are:
At the start of the compile process:

10:25:10: Running steps for project libindi...
10:25:10: Persisting CMake state...
10:25:19: Starting: "/usr/bin/cmake" --build . --target all
[1/432 1.1/sec] Building CXX object CMakeFiles/indi_hid_test.dir/libs/indibase/hidtest.cpp.o
[2/432 2.1/sec] Building C object CMakeFiles/indi_eval.dir/eventloop.c.o
[3/432 2.5/sec] Building C object CMakeFiles/indi_eval.dir/base64.c.o
[4/432 2.6/sec] Building C object CMakeFiles/indi_eval.dir/tools/evalINDI.c.o
[5/432 3.2/sec] Building C object CMakeFiles/indi_eval.dir/tools/compiler.c.o
[6/432 3.5/sec] Building C object CMakeFiles/indi_hid_test.dir/libs/indibase/hid_libusb.c.o
[7/432 3.0/sec] Linking CXX executable indi_hid_test
[8/432 3.4/sec] Building CXX object CMakeFiles/indi_openweathermap_weather.dir/drivers/weather/gason.cpp.o
[9/432 3.4/sec] Building C object CMakeFiles/indi_eval.dir/libs/lilxml.c.o
[10/432 2.7/sec] Building CXX object CMakeFiles/indi_weather_safety_proxy.dir/drivers/weather/gason.cpp.o
This continue for some time, then:
[432/432 1.3/sec] Linking CXX executable examples/tutorial_seven/tutorial_seven
10:31:00: The process "/usr/bin/cmake" exited normally.
10:31:00: Starting: "/usr/bin/kdesudo" -c 'make install'
make: *** No rule to make target 'install'.  Stop.
10:31:55: The process "/usr/bin/kdesudo" exited with code 2.
Error while building/deploying project libindi (kit: Desktop)
When executing step "Custom Process Step"
10:31:55: Elapsed time: 06:44.
kdesudo seems to be present and runs make but then there is the no rule error.
Trying your suggestion gives:
chris@AstroPi:~ $ cd Projects/build-indi
chris@AstroPi:~/Projects/build-indi $ sudo make -j8 install
[sudo] password for chris: 
make: *** No rule to make target 'install'.  Stop.
chris@AstroPi:~/Projects/build-indi $ 
I'm not sure how to proceed, could it be an incorrect build directory?

It's not helped by using a new Pi4 with a different OS, a different version of QT and the new split indi repository. Not sure how much more I could have changed :)

Chris

Read More...

Chris Rowland replied to the topic 'Experiences Using SM Beta on RPi 4, 4GB' in the forum. 2 weeks ago

I found the WiFi on the Pi4 using Raspbian and it's default WiFi to be poor, I had to position the Pi4 just so to get it to connect.
But once I had got AstroPi3 to do it's magic, which includes installing a different communication system, it seems much better.

Had to disable the timeout method of setting a hot spot as it started immediately instead of waiting 30 seconds.

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 2 weeks ago

There's nothing more to do until you can provide the data I asked for.

Most of whay you are assuming about hw the various connections work is incorrect.
The AUX and HC ports on the mount are the same, They are connections to the mount internal bus this is RS232 style using TTL signal levels and running at 115000 baud. It uses an internal protocol which we do not use. The USB port on the mount also connects to this AUX bus and it shows as a serial port.

The connector on the base of the HC is a RS232 serial port running at 9600 baud using the published NexStar protocol. If the HC has a USB connector there is a USB to serial adaptor in the HC, if a J type connector then there is a converter to RS232 signal levels in the HC and a Rs232 to USB adaptor will be needed. There is not other difference.

The HC provides a lot of the computing, and provides data such as RA and Dec, slew control, side of pier, location, time etc. There is a passthrough command that allows the HC communicate with devices on the AUX bus to get thing such as axis position and to sent the guide commands to the hour angle axis motor.

The Celestron GPS driver can only connect to the port on the base of the HC. It doesn't matter if it is a RS232 port or a USB port, they are, to the software, they same, a serial port.

There are applicatons that can connect to the AUX bus, Celestron's CPWI for example, but these applications have software that does the work of the HC. The Celestron GPS driver does not do this, it is designed to communicate with the HC.

Anyway, nothing more to do until you can get some log data to me. I'm away from October 12th to 28th so it may be November before much happens.

Chris

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 2 weeks ago

It's possible to set EKOS and the driver to get verbose logging of the startup commands in the driver this is what I did:

Edit the profile so the drivers do not start automatically.
Set the logging in the EKOS setup to verbose and to file for the mount.
Start the INDI Control panel and in the Celestron GPS and Options tab enable logging and check all the debug levels, logging levels and log levels.
Save the configuration.
Only now connect the driver.

The log file will now show the full details from the start mine shows this:
[2019-10-01T07:37:33.432 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Toggle Logging Level -- Scope Verbose "
[2019-10-01T07:37:36.062 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Session log file /home/chris/.indi/logs/2019-10-01/indi_celestron_gps/indi_celestron_gps_06:36:56.log "
[2019-10-01T07:37:51.800 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Connecting to /dev/ttyUSB0 @ 9600 "
[2019-10-01T07:37:51.802 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Port FD 4 "
[2019-10-01T07:37:51.802 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Connection successful, attempting handshake... "
[2019-10-01T07:37:51.802 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Initializing Celestron using Kx CMD... "
[2019-10-01T07:37:51.802 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <Kx> "
[2019-10-01T07:37:56.817 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[ERROR] Serial read error: Timeout error "
[2019-10-01T07:37:56.858 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <Kx> "
[2019-10-01T07:37:56.870 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <x#> "
[2019-10-01T07:37:56.881 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Celestron AVX is online. "
[2019-10-01T07:37:56.882 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved for DEVICE_PORT. "
[2019-10-01T07:37:56.895 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved for DEVICE_BAUD_RATE. "
[2019-10-01T07:37:56.895 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved for CONNECTION_MODE. "
[2019-10-01T07:37:56.896 BST INFO ][ org.kde.kstars.ekos] - Celestron AVX Version: "3.2" Interface: 5 is connected.
[2019-10-01T07:37:56.896 BST DEBG ][ org.kde.kstars.ekos] - 1 devices connected out of 3
[2019-10-01T07:37:57.087 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting controller version... "
[2019-10-01T07:37:57.088 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <V> "
[2019-10-01T07:37:57.091 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <05 1F 23> "
[2019-10-01T07:37:57.101 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Controller version: 5.31 "
[2019-10-01T07:37:57.102 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting controller variant... "
[2019-10-01T07:37:57.102 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <v> "
[2019-10-01T07:37:57.102 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <11 23> "
[2019-10-01T07:37:57.102 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting controller model... "
[2019-10-01T07:37:57.103 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <m> "
[2019-10-01T07:37:57.103 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <14 23> "
[2019-10-01T07:37:57.106 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Mount model: AVX "
[2019-10-01T07:37:57.107 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting RA firmware version... "
[2019-10-01T07:37:57.107 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <50 01 10 FE 00 00 00 02> "
[2019-10-01T07:37:57.107 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <07 0F 23> "
[2019-10-01T07:37:57.107 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting DEC firmware version... "
[2019-10-01T07:37:57.108 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <50 01 11 FE 00 00 00 02> "
[2019-10-01T07:37:57.108 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <07 0F 23> "
[2019-10-01T07:37:57.108 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Getting focuser version... "
[2019-10-01T07:37:57.108 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Does focuser exist... "
[2019-10-01T07:37:57.108 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <50 01 12 FE 00 00 00 04> "
[2019-10-01T07:37:59.366 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Received 6 bytes, expected 5 <00 00 00 00 00 23> "
[2019-10-01T07:37:59.367 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <Kx> "
[2019-10-01T07:37:59.381 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <x#> "
[2019-10-01T07:37:59.382 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] No focuser found, 1 "
[2019-10-01T07:37:59.382 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Firmware Info HC Ver 5.31 model AVX NexStar GEM mount, HW Ver 7.15 "
[2019-10-01T07:37:59.382 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <t> "
[2019-10-01T07:37:59.403 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <02 23> "
[2019-10-01T07:37:59.405 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved. "
[2019-10-01T07:37:59.405 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Celestron mount tracking, mode EQ N "
[2019-10-01T07:37:59.406 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < ON_COORD_SET >
[2019-10-01T07:37:59.407 BST INFO ][ org.kde.kstars.ekos] - "Celestron AVX is online."
[2019-10-01T07:38:00.103 BST INFO ][ org.kde.kstars.ekos.mount] - "Warning: Overriding Oynx configuration."
[2019-10-01T07:38:00.559 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < EQUATORIAL_EOD_COORD >
[2019-10-01T07:38:00.559 BST INFO ][ org.kde.kstars.ekos] - "Celestron AVX is online."
[2019-10-01T07:38:00.563 BST INFO ][ org.kde.kstars.ekos.mount] - "Warning: Overriding Oynx configuration."
[2019-10-01T07:38:00.599 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_ABORT_MOTION >
[2019-10-01T07:38:00.617 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_TRACK_MODE >
[2019-10-01T07:38:00.635 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_TRACK_STATE >
[2019-10-01T07:38:00.653 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_MOTION_NS >
[2019-10-01T07:38:00.678 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_MOTION_WE >
[2019-10-01T07:38:00.689 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_SLEW_RATE >
[2019-10-01T07:38:00.692 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TARGET_EOD_COORD >
[2019-10-01T07:38:00.697 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TIME_UTC >
[2019-10-01T07:38:00.717 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < GEOGRAPHIC_COORD >
[2019-10-01T07:38:00.736 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_PARK >
[2019-10-01T07:38:00.766 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_PARK_POSITION >
[2019-10-01T07:38:00.779 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_PARK_OPTION >
[2019-10-01T07:38:00.781 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_PIER_SIDE >
[2019-10-01T07:38:00.803 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < APPLY_SCOPE_CONFIG >
[2019-10-01T07:38:00.809 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < USEJOYSTICK >
[2019-10-01T07:38:00.812 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < Firmware Info >
[2019-10-01T07:38:00.826 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] InitPark: No Park data in file /home/chris/.indi/ParkData.xml: No such file or directory "
[2019-10-01T07:38:00.831 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Mount is unparked. "
[2019-10-01T07:38:00.832 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Setting Park Axis1 to 0.00 "
[2019-10-01T07:38:00.832 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Setting Park Axis2 to 0.00 "
[2019-10-01T07:38:00.832 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Setting Default Park Axis1 to 0.00 "
[2019-10-01T07:38:00.833 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Setting Default Park Axis2 to 0.00 "
[2019-10-01T07:38:00.833 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < Use Pulse Cmd >
[2019-10-01T07:38:00.872 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_TIMED_GUIDE_NS >
[2019-10-01T07:38:00.925 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < TELESCOPE_TIMED_GUIDE_WE >
[2019-10-01T07:38:00.926 BST INFO ][ org.kde.kstars.ekos] - "Guider port from Celestron AVX is ready."
[2019-10-01T07:38:01.153 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <i> "
[2019-10-01T07:38:01.153 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <07 29 23 0A 01 13 00 01 23> "
[2019-10-01T07:38:01.158 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Mount UTC offset is 0.00. UTC time is 2019-10-01T07:41:35 "
[2019-10-01T07:38:01.159 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <w> "
[2019-10-01T07:38:01.159 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <33 24 29 00 00 2B 11 01 23> "
[2019-10-01T07:38:01.159 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Mount latitude 51.6114 longitude 359.2786 "
[2019-10-01T07:38:01.159 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:01.159 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0C00,40000000#> "
[2019-10-01T07:38:01.160 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:01.160 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:01.160 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:01.160 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:01.161 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <J> "
[2019-10-01T07:38:01.161 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <01 23> "
[2019-10-01T07:38:01.161 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:01.162 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0C00,40000000#> "
[2019-10-01T07:38:01.162 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:01.162 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:01.162 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:01.163 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:01.183 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Loading device configuration... "
[2019-10-01T07:38:01.195 BST DEBG ][ org.kde.kstars.indi] - < Celestron AVX >: < SYSTEM_PORTS >
[2019-10-01T07:38:01.198 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Toggle Debug Level -- Scope Verbose "
[2019-10-01T07:38:01.199 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Toggle Logging Level -- Scope Verbose "[2019-10-01T07:38:01.205 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Session log file /home/chris/.indi/logs/2019-10-01/indi_celestron_gps/indi_celestron_gps_06:36:56.log "
[2019-10-01T07:38:01.205 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Active Snoop, driver: Dome Simulator, property: DOME_PARK "
[2019-10-01T07:38:01.210 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Pulse guiding is enabled. "
[2019-10-01T07:38:01.215 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Device configuration applied. "
[2019-10-01T07:38:01.215 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully loaded. "
[2019-10-01T07:38:01.216 BST INFO ][ org.kde.kstars.ekos.mount] - "Telescope info updated successfully."
[2019-10-01T07:38:01.223 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Saving device configuration... "
[2019-10-01T07:38:01.227 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Device configuration saved. "
[2019-10-01T07:38:01.227 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved. "
[2019-10-01T07:38:01.232 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Saving device configuration... "
[2019-10-01T07:38:01.237 BST INFO ][ org.kde.kstars.indi] - Celestron AVX : "[INFO] Device configuration saved. "
[2019-10-01T07:38:01.237 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] Configuration successfully saved. "
[2019-10-01T07:38:01.237 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:01.238 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0D00,40000000#> "
[2019-10-01T07:38:01.238 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:01.238 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:01.238 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:01.238 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:01.790 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:01.861 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0D00,40000000#> "
[2019-10-01T07:38:01.867 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:01.867 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:01.899 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:01.899 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:02.895 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:02.964 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0B00,40000000#> "
[2019-10-01T07:38:02.965 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:02.966 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:02.995 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:02.996 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:03.997 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:04.068 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0C00,40000000#> "
[2019-10-01T07:38:04.069 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[SCOPE] RA-DEC ( 1:10:57,90:00:00) "
[2019-10-01T07:38:04.070 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <p> "
[2019-10-01T07:38:04.100 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <E#> "
[2019-10-01T07:38:04.100 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] latitude 51.6114, sop E, PierSide W "
[2019-10-01T07:38:05.100 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] CMD <e> "
[2019-10-01T07:38:05.171 BST DEBG ][ org.kde.kstars.indi] - Celestron AVX : "[DEBUG] RES <0C9D0C00,40000000#> "

Can you try this please and send the log. Probably best to set up a test profile. There should be no need to make any other sort of connection or get an alignment, all I did was a quick align

Chris

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 2 weeks ago

It's difficut to say what is happening. The log shows problems with connecting at startup but the lack of logging of what bytes are actually returned is a problem. The message that is giving the incorrect value doesn't in itself communicate with the mount but is relying on messages it has obtained from the mount. No Response messages on the HC indicate some sort of problem with communicating with the mount.

All I can do is try to get information from my AVX mount to see if there's a way I can suggest getting more information.

I'm not sure what you mean by what you are writing about connecting the HC do you mean to the mount?

I would start by having the HC connected to the mount and the RasbPi connected to the HC. All the physical connections made. Then turn the power on to everything and do an alignment. A quick align is good enough. Then start Kstars and connect to the mount.

I'll try to see wat I can do tomorrow.

Chris

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 2 weeks ago

Looking at your log file:
[2019-09-19T14:12:08.136 UTC INFO ][ org.kde.kstars.ekos] - Celestron CGEM Version: "3.2" Interface: 5 is connected.
[2019-09-19T14:12:08.237 UTC INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[INFO] Controller version: 5.31 "
That's good, NS+ HC version 5.31
There's no mount communication information, that's a problem because the next mount information is:
[2019-09-19T14:12:10.123 UTC INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[WARNING] Unrecognized model (-1091685556). "
[2019-09-19T14:12:12.518 UTC INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[WARNING] Failed to retrive firmware information. "
[2019-09-19T14:12:12.520 UTC INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[WARNING] Mount firmware does not support getting pier side. "
The lack of mount communications is a problem because the model number is critical, this should be a fairly small positive integer. I'm not sure how to force the verbose debugging earlier in the connection process.
Verbose logging doesn't happen until later:
[2019-09-19T14:12:22.022 UTC DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[DEBUG] Toggle Debug Level -- Scope Verbose "
[2019-09-19T14:12:22.823 UTC DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[DEBUG] CMD <E> "
[2019-09-19T14:12:27.438 UTC DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[DEBUG] RES <D6FE,0BD1#> "
[2019-09-19T14:12:27.439 UTC DEBG ][ org.kde.kstars.indi] - Celestron CGEM : "[SCOPE] RA-DEC (20:09:20,16:37:01) "

What this tells us is that there's no obvious problem with mount to driver communication but there seems to be a problem with reading the initial mount properties. I'll try to see what I can do about getting more information but I don't have the same mount. It may be possible to trigger the verbose logging a bit earlier that would help.

However in the light of your latest rather snide comments you would rather I didn't bother I quite understand. It's going to be a bit of work because I don't happen to have a development environment at the moment.

Chris

Read More...

Chris Rowland replied to the topic 'At an impasse with CGEM/NexStar USB' in the forum. 2 weeks ago

There are commands sent to the mount at start up which identify the HC version, the HC type, the mount model, if it's a GEM or not and the motor controller versions. These are used to determine what the mount is capable of. The verbose logging was turned on after the mount was connected so the detail of this wasn't shown.

The "Failed to retrive firmware information" warning indicates that for some reason the HC didn't respond to the "V" command used to read the HC version, I don't know of a reason this woud happen for any HC produced by Celestron in the last 15 years.

That causes the communication to revert to the simplest mode, the low precision "E" command to read the position confirms this but that these commands work indicates that some sort of HC is connected.

We need a full, verbose log from the start of the connection attempt AND the exact HC version read from the HC display using the menu commands. "The latest" is not good enough.

Chris

Read More...

Chris Rowland replied to the topic 'AstroPi3 Scripts revised' in the forum. 3 weeks ago

Thanks, Yes I was thinking of the Raspbian version. Looking forward to a Ubuntu Mate build for the Pi4.

Read More...