Garth thanked Radek Kaczorek in topic Astroberry Server yesterday
gehelem thanked Radek Kaczorek in topic Astroberry Server yesterday
Jasem Mutlaq thanked Radek Kaczorek in topic Astroberry Server yesterday
Radek Kaczorek created a new topic ' Astroberry Server' in the forum. yesterday

I have just finished building a sneak preview of Astroberry Server and prepared a video teaser for it - youtu.be/t3CHtQmzvhY
Astroberry Server is a preconfigured desktop for Raspberry Pi 3 with KStars, Ekos and INDI server just ready to use. It is based on Ubuntu Mate 16.04 and it's accessible from your browser, VNC client or SSH. It works as a virtual wireless access point (VAS) and WLAN client at the same time. So you can use it to control your setup in the field without any additional device. Let me know of your thoughts

Read More...

Radek Kaczorek replied to the topic 'Still stuck with my ZWO 120MM' in the forum. 5 days ago

bads3ct0r wrote: I had similar problem with my ASI120MC-S (USB 3) when I bought it, it just couldn't take any exposure and went into infinite loop in Ekos. I flashed with USB 2.0 *-compatible firmware and since then never had any issue.

I would be very careful with flashing a device with other firmware. You can brick your camera this way.
Are you sure you successfully flashed USB 3.0 camera with USB 2.0 firmware?
I believe you should edit your post and warn users about unpredictable results if they follow this recommendation.

Read More...

Radek Kaczorek replied to the topic 'RaspberryPI - GPIO to ST4 Guiding Driver' in the forum. 7 days ago

What I'm thinking of is:
- Focuser
- ST4
- Shutter control
- Cover servo (maybe also light control for flats)
- Temperature, humidity and pressure sensors
- 4xPWM for dew heaters
- 4xPower switches

Anything else would be interesting?

Read More...

Radek Kaczorek replied to the topic 'RaspberryPI - GPIO to ST4 Guiding Driver' in the forum. 7 days ago

jwestervelt wrote: There really should be a unified RaspberryPi GPIO driver where individual pins can be assigned to things such as focuser control, ST4 guiding, DSLR bulb trigger, flat/cover servo actuation, and so on.


It's hardly possible because all the functionalities you mention require another piece of hardware controlled by RPi i.e. you need at least level shifter 3.3V to 5V for guiding pulses coming from GPIO and for the others you need special purpose device (stepper motor controller or relay/mosfet or pwm servo controller and so on). Unified driver will come to play when unified astro HAT is available... which is part of my development pipeline ;-)

Read More...

Radek Kaczorek replied to the topic 'Astroberry Focuser with Adafruit Motor HAT' in the forum. 1 week ago

The Motor HAT is already available in my local store. I gave it a closer look and found out that it supports Raspberry Pi model A+, B+ and Pi 2. Raspberry Pi 3 is not on the list. This means I'm not going to buy it but I can develop a driver for it anyway. Let me know when you have all parts altogether so there is a piece of hardware for tests.

Read More...

Radek Kaczorek replied to the topic 'Connecting indi via Bluetooth to a compuer' in the forum. 2 weeks ago

I'm glad you got it solved! As the matter of fact you can do all of these from GUI by clicking bluetooth icon on your taskbar, selecting bluetooth dongle, pairing devices and connecting the dongle. All of these will expose bluetooth serial port to a user - ready to use by INDI serial connection.
What was discussed with petarm is a generic approach for people keen on terminal and cli. Depending on linux distribution it might be the only approach available to a user. However in majority of cases GUI approach will work out of the box.

BTW. my experience is that in some cases neither of the approaches is sufficient and you need to use bluetoothctl to pair and connect the device.

Read More...

Radek Kaczorek replied to the topic 'Connecting indi via Bluetooth to a compuer' in the forum. 3 weeks ago

There are two things.
First, you need to connect to the device not only bind. Just use sudo rfcomm connect hci0 XX:XX:XX:XX:XX to accomplish this. Before you do that you need to pair the devices of course.
Second, make sure you have write access rights to the device /dev/rfcomm0 from a user you run indiserver. Just run ls -al /dev/rfcomm0 and check it out. If not add your user to a bluetooth (?) group with usermod -a -G
And the last but not least, let us know how it goes ;-)

Read More...

Radek Kaczorek replied to the topic 'Device not appearing in Ekos profile editor' in the forum. 3 weeks ago

I will try to trace it down. The only thing that I didn't do was to remove all KStars configuration from user profile. Strange indeed

Read More...

Radek Kaczorek replied to the topic 'Connecting indi via Bluetooth to a compuer' in the forum. 3 weeks ago

You can use any bluetooth dongle supporting 5V on communication lines e.g. HC-06
Just connect RX and TX lines to TX and RX lines of your mount, connect power to bluetooth dongle and you're done. You can connect from your PC to bluetooth serial line and use it in KStars as a port your mount is connected to.

Read More...

Radek Kaczorek created a new topic ' Device not appearing in Ekos profile editor' in the forum. 3 weeks ago

I have encountered a strange problem while setting up profiles in Ekos with a custom driver, which are not listed in Ekos dropdowns.
XML file for the driver is located in /usr/share/indi and it has proper syntax. The problem does not appear in new installations but pops up in case of updated systems with a new version of the driver. Among a few changes in the driver's binary (connection plugins) the XML was updated to reflect driver's name change i.e.
Before update:

<devGroup group="Auxiliary">
        <device label="AstroHub">
                <driver name="AstroHub">indi_astrohub</driver>
                <version>0.1</version>
        </device>
</devGroup>
After update:
<devGroup group="Auxiliary">
        <device label="Jolo AstroHub">
                <driver name="Jolo AstroHub">indi_jolohub</driver>
                <version>0.2</version>
        </device>
</devGroup>

Installing the driver on new system works OK, it appears on the Ekos list and works as designed.
Installing the driver on a system where previous version was installed results in the drivers does not appear on the Ekos list. This applies also for full removal and reinstallation of INDI/KStars/Ekos BUT removing local configuration files for KStars.
When I manually edit the driver's XML and change the label and name to e.g. "Test Driver" it appears on the Ekos list and works OK. If I reedit this file in the next step and change "Test Driver" to anything else it disappears from the Ekos list.

The above suggests that a driver name is somehow cached by KStars/Ekos (where?) and changing XML label/name for a driver results in kind of conflict between cache and source XML. As the result the driver does not appear on the list.

Now the question is where this cache is sitting so I can purge it.

Read More...

Radek Kaczorek replied to the topic 'Installing INDI on Ubuntu 16.10' in the forum. 4 weeks ago

It looks like you have ald version of libindi present on your system. Remove it first with apt-get remove --purge libindi1

Read More...

Radek Kaczorek replied to the topic 'Ekos Polar Alignment Assistant (Beta) is here!' in the forum. 1 month ago

Note that after first run your mount remembers 3 alignment points (based on 3 resolved captures), next you adjust the mount manually with screws, so these alignment points are not valid anymore, but probably are used in the next run of the procedure. Can you check on your mount's Align tab how many points are used before the second run? I believe it might be the root cause of this issue in some circumstances. In such a case it's enough to clear all the points before the second run.

Read More...

Radek Kaczorek replied to the topic 'Compilation of example indi-client does return error' in the forum. 1 month ago

These are C++ prerequisites. Just run the following to install required libs.

sudo apt-get install libz libcfitsio libnova


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!