Gilles Gagnon created a new topic ' Pegasus Astro UPB focuser error' in the forum. 2 weeks ago

I get a "Focuser failed to move to new requested position." error message when issuing a focus command (either in or out) on the Pegasus Astro UPB focuser, even though the focuser moves to a different position. I don't know if the UPB reports a focus position before the focuser gets to the requested position, or if the problem is caused by something else but the log file is attached as a reference.

Any help in solving this issue would be appreciated.

Thanks.

Read More...

Gilles Gagnon replied to the topic 'Work for Google & KStars in 2019!' in the forum. 2 months ago

Great initiative! Thanks for contributing to mentor the next generation of software developers.

Read More...

Gilles Gagnon replied to the topic 'Problems with Xagyl on Pi (Stellarmate)' in the forum. 2 months ago

I recently acquired a XAGYL filter wheel with which I had problems making it work with KStars/EKOS/Indi on my ODroid XU4Q system as well as my MAC. It would work erratically and I could not figure out why. Even the logs were not telling me anything useful.

I connected to the FW via 'cutecom' on the XU4, from which I could make it work but not reliably. Once I issued the "R7" command (commands are described in the XAGYL user manual), I could issue other commands (with cutecom) and the FW would work correctly but when I would connect again in indi, the filter wheel would work erratically again. I found out that even in simulation mode, the XAGYL FW wold not work reliably (could not change filter or even filter names). I decided to check the indi ZAGYL driver in /usr/bin against a driver version I had built from sources and their sizes where quite different. I decided to try the driver I built from source and everything started to work without any issue. I can now change filters from indi or any of the EKOS modules that need to control the FW.

Your problem may well be from a different cause but you may want to try building the XAGYL driver from sources to see if that solves your problem. BTW my system is based on an ODroid XU4, and the sources were built on that machine.

Hope this helps.

Read More...

Gilles Gagnon created a new topic ' Persistent serial port mapping and /dev/bus/usb/00x/00y' in the forum. 2 months ago

I use persistent serial port mapping for my all my serial devices with virtually no problem (e.g. /dev/mount, /dev/filterwheel, /dev/focuser,...), except that once in a while a device connects as /dev/bus/usb/00x/00y instead of /dev/ttyUSBz and the port mapping doesn't work. This seem to happen when I disconnect/reconnect the device or if I connect it after the system as booted. As I ideally do not want to reboot to correct the problem, I wonder if there is a reason/solution/work-around to this issue.

Thanks.

Read More...

Gilles Gagnon replied to the topic 'More RTC madness!!!!' in the forum. 2 months ago

Thanks for reviving this thread. You made me realize that my suggestion (in #34237) of putting "hwclock -s" in rc.local was not quite correct; sorry for that.

In my case, what worked was to put "/sbin/hwclock --hctosys" in rc.local (before the "exit 0"), not "hwclock -s" as mentionned in my previous post. "--hctosys" will set the system time and date with the time/date from the hardware clock.

Sorry for the confusion, must have been my winter cold :-/ !

Read More...

Gilles Gagnon replied to the topic 'More RTC madness!!!!' in the forum. 3 months ago

Hello Brian,

When I issue "date; sudo hwclock -r" I get an output similar to yours. I don't have any Internationalisation Options in raspi-config either.

Have you tried adding "hwclock -s" in /etc/rc.local, before the "exit 0" line? It solved the problem for me.

Good luck.

Gilles

Read More...

Gilles Gagnon replied to the topic 'More RTC madness!!!!' in the forum. 3 months ago

Just as a follow-up, adding hwclock -s to /etc/rc.local worked! The system clock is now set correctly when the system boots.

Thanks again.

Gilles

Read More...

Gilles Gagnon replied to the topic 'More RTC madness!!!!' in the forum. 3 months ago

Thanks for the info Radek.

I'll add "hwclock -s" to rc.local and see if it fixes it when I get back home. Hope its "as simple as that", and that the solution can work for Brian and others.

Gilles

Read More...

Gilles Gagnon replied to the topic 'More RTC madness!!!!' in the forum. 3 months ago

I could also make use of the information on making the RTC set the system clock as I am in a similar situation. Stellarmate raspi with a DS1307 RTC which, from what I understand is a "less precise" DS3231.

I have the same dtoverlay line in my /boot/config file; the RTC driver is loaded, from the i2cdetect command; haven't checked the output of lsmod | grep rtc. I know the RTC is accessible and works as I can issue hwclock -w and hwclock -r command to set and read the RTC but the RTC date and time won't be used at boot time to set system date and time. I can always set the system clock manually after boot but I would prefer the system to set it up automatically, especially in a headless configuration.

Any help will be appreciated. Thanks in advance.

Read More...

Gilles Gagnon replied to the topic 'Script to set system date from GPS' in the forum. 4 months ago

Thanks for this info. This GPS NMEA solution is simpler than the GPSD one, plus it frees a port on my USB hub and there's one less cable in the way. Great!

Read More...

Gilles Gagnon replied to the topic 'Script to set system date from GPS' in the forum. 4 months ago

I think you are correct in your assumption. If KStars is running on a machine connected to the Internet, that machine will have correct time and position, and will likely pass the information to the rpi but I haven't tested this configuration and as such can't be certain.

My solution is meant for people who observe/image on the go without access to the Internet for current time and position information. If your position is fixed, there is not much use for the script.

Read More...

Gilles Gagnon replied to the topic 'Script to set system date from GPS' in the forum. 4 months ago

GPS may not be as relevant for fixed installation, as you set your location once and you're done, but it may come handy for those who observe/image on-the-go, at different locations and without internet access.

As far as using the script to set the system time; as per the INDI configuration panel, KStars can get the date/time and position info from gpsd but from what I found out, only the position is passed correctly. The time is taken from the system time which is not correct if it's not set via a real time clock and don't have access to the Internet for ntpd.

BTW, I found the series of posts about your remote pico observatory. Great work and it gives me ideas on how to build one for my installation.

Read More...