Thank Yo Kaczorek, I was running pyindi-client 0.2.3 after upgrading to 0.2.4 mqtt broadcast installs and runs as expected. Thanks again.
Read More...
Hi, I'm running Indi server with Ubuntu 18.04 on a desktop PC. When I run sudo dpkg -i indi-mqtt_1.0.1_all.deb I get the following output ...
ray@indiastro:/shared$ sudo dpkg -i indi-mqtt_1.0.1_all.deb
(Reading database ... 133158 files and directories currently installed.)
Preparing to unpack indi-mqtt_1.0.1_all.deb ...
Removed /etc/systemd/system/multi-user.target.wants/indi-mqtt.service.
Unpacking indi-mqtt (1.0.1) over (1.0.0) ...
Setting up indi-mqtt (1.0.1) ...
Usage:
pip install [options] <requirement specifier> [package-index-options] ...
pip install [options] -r <requirements file> [package-index-options] ...
pip install [options] [-e] <vcs project url> ...
pip install [options] [-e] <local project path> ...
pip install [options] <archive url/path> ...
no such option: --no-warn-script-location
Created symlink /etc/systemd/system/multi-user.target.wants/indi-mqtt.service → /etc/systemd/system/indi-mqtt.service.
When I run indi-mqtt from the command line I get this ...
ray@indiastro:/shared$ sudo /usr/bin/indi-mqtt.py
INDI server localhost/7624 disconnected.
Traceback (most recent call last):
File "/usr/bin/indi-mqtt.py", line 315, in <module>
observatory_json = getJSON(devices)
File "/usr/bin/indi-mqtt.py", line 223, in getJSON
device_type = strDeviceType(device.getDriverInterface())
File "/usr/bin/indi-mqtt.py", line 146, in strDeviceType
if s & 0:
TypeError: unsupported operand type(s) for &: 'SwigPyObject' and 'int'
swig/python detected a memory leak of type 'uint16_t *', no destructor found.
I've also tried installing as per the instructions above provided by Kaczorek but I get the same error when run manually.
Any ideas please?
Read More...
Strange. I can confirn that Align tab and EQMOD driver is now working for me under windows 8.1. I'm using Kstars Build: 2019-12-06T17:21:51Z
Read More...
Hi Jasem, A quick test of the latest Kstars nightly build (3.3.9) using simulators only suggest my problem of Kstars crashing when selecting the 'Align' module looks to be fixed. Will do more testing when the sky's clear but for now many thanks.
Read More...
I'm running Kstars remotely on a windows PC and indi running on a separate tower PC running Linux(ubuntu 18.04)
Read More...
Another update. I have found that if I delete the file 'kstarsrc' and run Kstars if goes through the initial setup of kstars again and I can use the align tab again once only, 2nd and further attempts crash kstars. In these first attempts I have verified that Astrometry.net solving works, both online and remote using CCD and Telescope Simulators.
Read More...
Hi Jasem, Just an update on this crash. My PC I run Kstars on and is now crashing when selecting the Align tab is running W8.1. I have just tried installing Kstars (#211) on another W8.1 PC and a W10 PC, both have never run Kstars before. Both these new PC's crash at the same point. Strange thing is the first time after install it doesn't crash and remote solving worked but the 2nd and subsequent runs of Kstars now all 3 PC's crash when selecting the Align tab.
Read More...
Hi Jasem, Thanks for looking at this. I tried the new nightly build (211) and I'm no longer getting the 'no binaries' message but the instant I press the Align icon Kstars crashes. The log only has entries prior to the crash so not sure how much help it will be but I can provide the full log it if will help. I've provided some of the log that looks to me to be significant below. This line from the log looks strange as the Astometry driver is in the profile along with CCD and Telescope Simulators only (3 drivers) - 'Cannot set solver to remote. The Ekos equipment profile must include the astrometry Auxiliary driver.'
Cheers.
[2019-11-20T17:03:19.656 GMT Standard Time INFO ][ org.kde.kstars] - Welcome to KStars 3.3.8
[2019-11-20T17:03:19.657 GMT Standard Time INFO ][ org.kde.kstars] - Build: 2019-11-20T23:23:39Z
[2019-11-20T17:03:19.658 GMT Standard Time INFO ][ org.kde.kstars] - OS: "windows"
..
[2019-11-20T17:03:53.068 GMT Standard Time INFO ][ org.kde.kstars.ekos] - "Establishing communication with remote INDI Web Manager..."
[2019-11-20T17:03:53.214 GMT Standard Time DEBG ][ default] - INDI: Error communicating with INDI Web Manager: "Error transferring http://192.168.0.11:8624/api/info/version - server replied: Not Found"
[2019-11-20T17:03:53.295 GMT Standard Time INFO ][ org.kde.kstars.ekos] - "Connecting to remote INDI server at 192.168.0.11 on port 7,624 ..."
[2019-11-20T17:03:53.297 GMT Standard Time DEBG ][ org.kde.kstars.indi] - Adding managed driver "Ekos Remote Host"
[2019-11-20T17:03:53.298 GMT Standard Time DEBG ][ org.kde.kstars.indi] - INDIListener: Adding a new client manager to INDI listener..
[2019-11-20T17:03:53.306 GMT Standard Time DEBG ][ org.kde.kstars.indi] - INDI server connected.
[2019-11-20T17:03:53.306 GMT Standard Time INFO ][ org.kde.kstars.ekos] - "INDI services started. Connection to remote INDI server is successful. Waiting for devices..."
[2019-11-20T17:03:53.332 GMT Standard Time DEBG ][ org.kde.kstars.indi] - Received new device Astrometry
[2019-11-20T17:03:53.348 GMT Standard Time DEBG ][ org.kde.kstars.indi] - INDIListener: New device Astrometry
[2019-11-20T17:03:53.348 GMT Standard Time INFO ][ org.kde.kstars.ekos] - Ekos received a new device: Astrometry
[2019-11-20T17:03:53.378 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < CONNECTION >
[2019-11-20T17:03:53.379 GMT Standard Time INFO ][ org.kde.kstars.ekos] - Astrometry Version: "" Interface: 0 is connected.
[2019-11-20T17:03:53.379 GMT Standard Time DEBG ][ org.kde.kstars.ekos] - 1 devices connected out of 1
[2019-11-20T17:03:53.434 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < DRIVER_INFO >
[2019-11-20T17:03:53.448 GMT Standard Time INFO ][ org.kde.kstars.ekos] - CCD Simulator Version: "" Interface: 0 is connected.
[2019-11-20T17:03:53.449 GMT Standard Time DEBG ][ org.kde.kstars.ekos] - 2 devices connected out of 2
[2019-11-20T17:03:53.494 GMT Standard Time DEBG ][ org.kde.kstars.indi] - Received new device Telescope Simulator
[2019-11-20T17:03:53.495 GMT Standard Time DEBG ][ org.kde.kstars.indi] - INDIListener: New device Telescope Simulator
[2019-11-20T17:03:53.496 GMT Standard Time INFO ][ org.kde.kstars.ekos] - Ekos received a new device: Telescope Simulator
[2019-11-20T17:03:53.496 GMT Standard Time INFO ][ org.kde.kstars.ekos] - "Remote devices established."
[2019-11-20T17:03:53.502 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Telescope Simulator >: < CONNECTION >
[2019-11-20T17:03:53.503 GMT Standard Time INFO ][ org.kde.kstars.ekos] - Telescope Simulator Version: "" Interface: 0 is connected.
[2019-11-20T17:03:53.503 GMT Standard Time DEBG ][ org.kde.kstars.ekos] - 3 devices connected out of 3
[2019-11-20T17:03:53.504 GMT Standard Time INFO ][ org.kde.kstars.ekos] - All INDI devices are now connected.
[2019-11-20T17:03:54.112 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Telescope Simulator >: < GUIDE_RATE >
[2019-11-20T17:03:54.114 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < DEBUG >
[2019-11-20T17:03:54.119 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < CONFIG_PROCESS >
[2019-11-20T17:03:54.123 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < ACTIVE_DEVICES >
[2019-11-20T17:03:54.125 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < DEBUG_LEVEL >
[2019-11-20T17:03:54.127 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < LOGGING_LEVEL >
[2019-11-20T17:03:54.128 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < LOG_OUTPUT >
[2019-11-20T17:03:54.129 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < ASTROMETRY_SOLVER >
[2019-11-20T17:03:54.163 GMT Standard Time INFO ][ org.kde.kstars.ekos.align] - "Idle."
[2019-11-20T17:03:54.164 GMT Standard Time INFO ][ org.kde.kstars.ekos.align] - "Cannot set solver to remote. The Ekos equipment profile must include the astrometry Auxiliary driver."
[2019-11-20T17:03:54.236 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < ASTROMETRY_SETTINGS >
[2019-11-20T17:03:54.242 GMT Standard Time DEBG ][ org.kde.kstars.indi] - < Astrometry >: < ASTROMETRY_DATA >
[2019-11-20T17:03:54.628 GMT Standard Time DEBG ][ org.kde.kstars.indi] - Astrometry : "[DEBUG] Toggle Debug Level -- Driver Debug "
Read More...
Hi, I've been running version Kstars v3.3.6 for a while and all works well. When trying the latest two Kstars versions I'm getting the error message "Failed to find astrometry.net bininaries". I can go back to v3.3.6 and everything works fine again. Can anybody advise why under 3.3.7 and 3.3.8 its complaining about the offline Astometry.net config when nothing has changed from 3.3.6.
Thanks.
Read More...
Hi Jasem,
I'm currently implementing the Baader Dome driver into my home made dome. Previously I have used both MaxdomeII and Dome Scripting Gateway drivers successfully. I had a problem with Baader dome in as much that whilst all commanded rotation and shutter movements worked fine I found that Slaving wouldn't work when enabled. Doing comparisons between the Dome Simulator source code and the Baader source code I added the following code from the Simulator source to the Baader source and this resolved my issue. Perhaps you could look at this when you have time . It might help others who experience this issue. For info I was testing with Telescope Simulator.
./ added this to the end of void BaaderDome::TimerHit()
// Not all mounts update ra/dec constantly if tracking co-ordinates
// This is to ensure our alt/az gets updated even if ra/dec isn't being updated
// Once every 10 seconds is more than sufficient
// with this added, dome simulator will now correctly track telescope simulator
// which does not emit new ra/dec co-ords if they are not changing
if (!isParked() && TimeSinceUpdate++ > 9)
{
TimeSinceUpdate = 0;
UpdateMountCoords();
}
Hope this is useful.
Read More...
Problem solved.
Found another post referencing a xml config file. I looked for such a file earlier but while finding many xml files for other drivers I didn't see one for XAGYL. Luckily the other post gave the full file name (XAGYL Wheel_config.xml') so I searched a gain and found it. Once deleted my filter wheel worked again.
Regards.
Read More...