giorgio created a new topic ' Hitecastro Mount Hub Pro Compact' in the forum. 6 days ago

I've purchased an Hitecastro Mount Hub Pro Compact from www.hitecastro.co.uk and I'd love to use it in Indi.
This device is the Compact version of its popular bigger brother and it includes: a robofocus compatible focuser controller, four 12V DC ports that can be switched on/off in software and a dew controller with three ports also manageable in software.
It's a very neat and relatively inexpensive device that could have a lot of potential for automated remote configurations in Indi

Read More...

giorgio replied to the topic 'KStars 2.7.4 for Windows is released' in the forum. 1 month ago

Great news and well done!!

Read More...

giorgio replied to the topic 'iAstroHub 3.0 for RPi3 is ready!' in the forum. 1 month ago

Can iAstroHub act as an out of the box INDI server for Ekos/KStars and other INDI client applications?
In other threads we are trying to come up with a default INDI RPi image that can be easily deployed with minimal configuration. A plug and play box pretty much like iAstroHub.
With such a thing I would then be free to use Ekos/KStars on my client computers..

Read More...

giorgio replied to the topic 'Malfunctioning indi_temma driver' in the forum. 3 months ago

Hello Jasem, I'm afraid I do not have a version of minicom to try. On the other hand I confirm I can use the mount with with the same cable under Mac Os and the Cloudmakers version of Indi running on the same Mac. The issue seems to be restricted to Raspberry Pi. I have the impression that Jean-Christophe is having my same issue. See is thread on this same forum: indilib.org/forum/general/1782-problems-...takahashi.html#13660

He also noticed that RA and DEC position cannot be read from the Pi.

Thank you and regards,
Giorgio

Read More...

giorgio replied to the topic 'Problems with STi and Takahashi' in the forum. 3 months ago

Hello Jean-Christophe, I believe I am experiencing your same issue. I'm also using an EM-200 and, with the latest version of indi_temma, RA and DEC positions cannot be read from the mount when using a Raspberry Pi. Here is the link to my thread:

indilib.org/forum/mounts/1781-malfunctio...di-temma-driver.html

My troubleshooting has stalled since I do not have (and not sure how to get) a version of minicom running on windows.

Regards,
Giorgio

Read More...

giorgio replied to the topic 'Malfunctioning indi_temma driver' in the forum. 3 months ago

Thanks again for your help.

I've tried running Indi as root using:
sudo indiserver -vvv indi_temma but the issue is still there. Checked permissions for /dev/ttyUSB0 and they are:

giorgio@astropi3:~$ ls -al /dev/ttyUSB*
crw-rw-rw- 1 root dialout 188, 0 Dec 30 23:25 /dev/ttyUSB0

I've also added user 'giorgio' to the dialout group but again, the problem persists. I'm tempted to rebuild the RPi from scratch to see if the issue was caused by upgrading from Indi 1.2 to 1.3 or during any of the other updates...

Read More...

giorgio replied to the topic 'Malfunctioning indi_temma driver' in the forum. 3 months ago

One more thing, here is the output of 'lsusb' from the RPi3:

giorgio@astropi3:~$ lsusb
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Read More...

giorgio replied to the topic 'Malfunctioning indi_temma driver' in the forum. 3 months ago

Thank you for your reply Gerry. Here are some more details/answers:

- I'm running Ubuntu Mate on the RPi3 and I've installed Indi and KStars using Jasem apt repository.
- I assume I have the latest Indi and driver versions configured using 'apt-get update' followed by 'apt-get upgrade'.
- The RPi3 connects to the mount using a well tested (using other applications/computers on my EM-200) FTDi serial to USB adapter.
- Driver is configured to use /dev/ttyUSB0 at 19200 baud.

After additional testing I can definitely say that issue is limited to the RPi itself. Today I successfully used Indi Server and indi_temma on my macbook (Peter Polakovic Cloudmakers version) directly connected to the mount on /dev/cu.usbserial-AI02CT1N at 19200 baud. Cartes Du Ciel worked flawlessly and driver parameters on Indi control panel were reporting coordinates in sync with Cartes Du Ciel.

I'm very keen to understand what is going wrong with the RPi. That is my preferred configuration since it allows me to operate telescope and all other gear remotely. Is /dev/ttyUSB0 a correct parameter? How can I check for permission issues on the serial port?

Thank you for any possible help or hint.
Giorgio

P.S. error 'SLEW_CENTERING is not a member of TELESCOPE_SLEW_RATE property' was being logged when trying to use the Cloudmakers AstroTelescope client. At this point it seems it is a secondary issue.

Read More...

giorgio created a new topic ' Malfunctioning indi_temma driver' in the forum. 3 months ago

I have Indi configured on a RPi3 and connected to a Tak EM-200.

File Attachment:

File Name: IndiTemmaDriverLog.rtf
File Size: 45 KB

Any attempt to slew, sync or park the mount fails. I always power on the mount and start Indi with the mount having the counterweights down and the scope pointing north. RA and DEC motors respond to commands but the mount moves to completely random positions. I have tried to use Cartes du Ciel and Cloudmakers AstroTelescope but the results are the same.
Even issuing commands directly into the Indi Control Panel bears the same issues.

In both Cartes Du Ciel and AstroTelescope I noticed that mount RA and DEC positions are always both showing as 00:00:00 and never change even when I try to slew somewhere.
Also the Eq. Coordinates property in the driver is set to 00:00:00 and never changes. Could this be the root cause of the issue? During some of my attempts I've seen the following message appearing in the Indi driver control panel: SLEW_CENTERING is not a member of TELESCOPE_SLEW_RATE property.

If it can be of any help here attached is the output of the Indi server -vv (verbose) mode after having attempted a slew to RA 00:00:01and having aborted the motion to avoid the scope hitting the tripod legs. I could not find a Debugging property in the Driver itself.

Any help would be greatly appreciated.

Read More...

giorgio created a new topic ' Polemaster in KStars' in the forum. 3 months ago

I don't know if this has been asked before but I would love to see in KStars a feature to polar align the mount by imaging the celestial pole region. Exactly what the QHY Polemaster does. There's a GitHub project that has some code in Python, could this be embedded in KStars?

Read More...

giorgio replied to the topic 'Auto focus in Ekos with Sky watcher auto focus' in the forum. 3 months ago

I tried to compile the Hitecastro driver on my rpi3, but then got an error when try 'make'. Here is what I wrote on GitHub. Maybe you know what's happening:

I have installed 'build essential' and libindi-dev.
I successfully issued the 'make .. ' command and got the following, I presume successful output (btw I've swapped FindINDI.cmake with another found at: sourceforge.net/p/indi/code/HEAD/tree/tr...dules/FindINDI.cmake):

giorgio@astropi3:~/hitecastrodcfocuser/build$ cmake ..
-- The CXX compiler identification is GNU 5.4.0
-- The C compiler identification is GNU 5.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for module 'libindi'
-- Found libindi, version 1.3.1
-- Found INDI: /usr/include/libindi (found version "1.3.1")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/giorgio/hitecastrodcfocuser/build

At this point I tried issuing a 'make' but got the following message:

giorgio@astropi3:/hitecastrodcfocuser/build$ make
Scanning dependencies of target indi_hitecastrodcfocuser
[ 50%] Building CXX object CMakeFiles/indi_hitecastrodcfocuser.dir/hitecastrodcfocuser.cpp.o
In file included from /home/giorgio/hitecastrodcfocuser/hitecastrodcfocuser.cpp:21:0:
/home/giorgio/hitecastrodcfocuser/hitecastrodcfocuser.h:28:34: fatal error: indibase/indifocuser.h: No such file or directory
compilation terminated.
CMakeFiles/indi_hitecastrodcfocuser.dir/build.make:62: recipe for target 'CMakeFiles/indi_hitecastrodcfocuser.dir/hitecastrodcfocuser.cpp.o' failed
make[2]: *** [CMakeFiles/indi_hitecastrodcfocuser.dir/hitecastrodcfocuser.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/indi_hitecastrodcfocuser.dir/all' failed
make[1]: *** [CMakeFiles/indi_hitecastrodcfocuser.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
giorgio@astropi3:/hitecastrodcfocuser/build$

It seems file indibase/indifocuser.h cannot be found, but I can see it in /usr/include/libindi/ .

Read More...

giorgio replied to the topic 'Auto focus in Ekos with Sky watcher auto focus' in the forum. 5 months ago

Sorry for reopening a very old thread but it seems that Andy (a member of this forum) built a driver for the Hitecastro Dec focus controller:
github.com/A-j-K/hitecastrodcfocuser

Has anyone tried it? I would be grateful to hear some feedback before pulling the trigger on the controller and a skywatcher motor for my widefield rig.

Cheers,
Giorgio

Read More...

giorgio replied to the topic 'How to upgrade to Indi 1.3.0' in the forum. 5 months ago

Right,

I've run:
sudo apt-get update
sudo apt-get upgrade

but when I check the version using:
apt-cache show indi-full

It still shows: 1.2+r1.255~ubuntu16.04.1

I'm tempted to use:
sudo apt-get dist-upgrade

Read More...

giorgio created a new topic ' How to upgrade to Indi 1.3.0' in the forum. 5 months ago

Hi folks,

I have Indi running on Ubuntu Mate on a RPi2 and RPi3, how do I upgrade to the newly released Indi 1.3.0?

Is a:
sudo apt-get update
sudo apt-get upgrade

all I need to do? Or do I have to reinstall Indi from scratch?

Thanks,
Giorgio

Read More...

giorgio replied to the topic 'Error connecting to EM200' in the forum. 5 months ago

Success!!

I had to turn off/on the mount disconnect/reconnect a few times and then it connected :)

Thank you again for your help Jasem!!

Regards,
Giorgio

Read More...

giorgio replied to the topic 'Error connecting to EM200' in the forum. 5 months ago

Great! Thanks for this. I've set /dev/ttyUSB0, which is the same value I see on the RPi2, and now I get these messages when trying to connect:

2016-10-29T21:39:55: Client 0: read <newSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T21:39:55: Driver indi_temma: queuing responsible for <newSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T21:39:55: Driver indi_temma: sending <newSwitchVector device="Temma" name="CONNECTION">
2016-10-29T21:39:55: Driver indi_temma: Connecting even parity 9600 baud
2016-10-29T21:39:55: Driver indi_temma: Calling get version
2016-10-29T21:39:55: Driver indi_temma: Wrote 3 of 3 bytes rc 0
2016-10-29T21:39:57: Driver indi_temma:
2016-10-29T21:39:57: Driver indi_temma: We timed out reading bytes 0
2016-10-29T21:39:57: Driver indi_temma: get version returns nothing
2016-10-29T21:39:57: Driver indi_temma: Attempt clearing hack fd is 3
2016-10-29T21:39:57: Driver indi_temma: Do disconnect
2016-10-29T21:39:58: Driver indi_temma: Try get version again port is 3
2016-10-29T21:39:58: Driver indi_temma: Wrote 3 of 3 bytes rc 0
2016-10-29T21:40:00: Driver indi_temma:
2016-10-29T21:40:00: Driver indi_temma: We timed out reading bytes 0
2016-10-29T21:40:00: Driver indi_temma: get version returns nothing
2016-10-29T21:40:00: Driver indi_temma: Disconnect port
2016-10-29T21:40:00: Driver indi_temma: read <setSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T21:40:00: Client 0: queuing <setSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T21:40:00: Client 0: sending <setSwitchVector device="Temma" name="CONNECTION"

Read More...

giorgio replied to the topic 'Error connecting to EM200' in the forum. 5 months ago

Thank you for your reply Jasem,

Yes, I confirm that the ports value under option is set to 7624. Unfortunately still no joy.

Regards,
Giorgio

Read More...

giorgio created a new topic ' Error connecting to EM200' in the forum. 5 months ago

On my RPi3 using the latest version of indi and all its drivers, I'm getting the following error when trying to connect to my EM200 using indi_temma driver:

2016-10-29T17:36:32: Driver indi_temma: connect error Port failure Error: No such file or directory. Check if device is connected to this port.

I'm running Indi using:
indiserver -vv indi_temma

here are the on screen messages:

2016-10-29T17:48:16: startup: indiserver -vv indi_temma
2016-10-29T17:48:16: Driver indi_temma: pid=1827 rfd=3 wfd=6 efd=7
2016-10-29T17:48:16: listening to port 7624 on fd 4
2016-10-29T17:48:16: Driver indi_temma: sending <getProperties version='1.7'/>

2016-10-29T17:48:16: Driver indi_temma: read <getProperties device='GPS Simulator' name='GEOGRAPHIC_COORD'>
2016-10-29T17:48:16: Driver indi_temma: snooping on GPS Simulator.GEOGRAPHIC_COORD
2016-10-29T17:48:16: Driver indi_temma: read <getProperties device='GPS Simulator' name='TIME_UTC'>
2016-10-29T17:48:16: Driver indi_temma: snooping on GPS Simulator.TIME_UTC
2016-10-29T17:48:16: Driver indi_temma: read <defSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T17:48:16: Driver indi_temma: read <defTextVector device='Temma' name='DRIVER_INFO'>
2016-10-29T17:48:16: Driver indi_temma: read <defSwitchVector device='Temma' name='CONFIG_PROCESS'>
2016-10-29T17:48:16: Driver indi_temma: read <defTextVector device='Temma' name='DEVICE_PORT'>
2016-10-29T17:48:16: Driver indi_temma: read <setTextVector device='Temma' name='DEVICE_PORT'>
2016-10-29T17:48:16: Driver indi_temma: read <defSwitchVector device='Temma' name='TELESCOPE_BAUD_RATE'>
2016-10-29T17:48:16: Driver indi_temma: read <setSwitchVector device='Temma' name='TELESCOPE_BAUD_RATE'>
2016-10-29T17:48:16: Driver indi_temma: read <defTextVector device='Temma' name='ACTIVE_DEVICES'>
2016-10-29T17:48:16: Driver indi_temma: read <setTextVector device='Temma' name='ACTIVE_DEVICES'>
2016-10-29T17:48:16: Driver indi_temma: read <getProperties device='GPS Simulator' name='GEOGRAPHIC_COORD'>
2016-10-29T17:48:16: Driver indi_temma: read <getProperties device='GPS Simulator' name='TIME_UTC'>
2016-10-29T17:48:16: Driver indi_temma: read <defNumberVector device='Temma' name='TELESCOPE_TIMED_GUIDE_NS'>
2016-10-29T17:48:16: Driver indi_temma: read <defNumberVector device='Temma' name='TELESCOPE_TIMED_GUIDE_WE'>
2016-10-29T17:48:16: Driver indi_temma: read <defNumberVector device='' name=''>

upon trying to connect to the mount via the Indi Control Panel I see:

2016-10-29T17:50:27: Client 0: read <newSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T17:50:27: Driver indi_temma: queuing responsible for <newSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T17:50:27: Driver indi_temma: sending <newSwitchVector device="Temma" name="CONNECTION">
2016-10-29T17:50:27: Driver indi_temma: Connecting even parity 9600 baud
2016-10-29T17:50:27: Driver indi_temma: connect error Port failure Error: No such file or directory. Check if device is connected to this port.
2016-10-29T17:50:27: Driver indi_temma: read <setSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T17:50:27: Client 0: queuing <setSwitchVector device='Temma' name='CONNECTION'>
2016-10-29T17:50:27: Client 0: sending <setSwitchVector device="Temma" name="CONNECTION"

By the way, everything still works fine on my RPi2 but I haven't updated packages for a while on that device (apt-get update, apt-get upgrade).
Would you know what could be the issue here? What file is being not found? Please let me know if you need further details.

Many thanks in advance,
Giorgio

Read More...

giorgio replied to the topic 'Unable to connect to QSI 690 from RPi3' in the forum. 10 months ago

Success! I was able to take pictures at various exposure lengths:)
The rig is now ready for a trial under a the stars.

Thanks a lot for all your help with the qsi driver!!

Giorgio

Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!