Radek Kaczorek replied to the topic 'Astroberry GPS with Adafruit GPS breakout board' in the forum. 10 hours 48 minutes ago

You miss the leading / in DEVICES - it should be:

DEVICES="[b]/[/b]dev/ttyS0"


Read More...

Radek Kaczorek replied to the topic 'Guiding - Lost guide star causes abort of the ccd sequence' in the forum. 10 hours 57 minutes ago

Indeed, when using external guider such as PHD2 and starting it from Ekos reaquires a lost star. I have tested it recently. I believe the behavior should be the same for internal guider. If it's not it would be good to change it.

BTW. Rob, could you give access to the 5 secs parameter to a user? or set it to a higher value? I believe 5 secs is too low - if you guide with 4 secs exposure time it will try to reaquire after loosing just one frame, which in many cases is not enough (e.g. passing clouds). In my case ZWO ASI 120MM, used as a guiding camera, sometimes scrambles the image, which renders 2-3 subsequent captures lost. I would then set the value to 15 secs and would be just fine.

Read More...

Radek Kaczorek replied to the topic 'Astroberry GPS with Adafruit GPS breakout board' in the forum. 3 days ago

If you see raw NMEA data, your gps device is ok. gpsd access rights are also ok (gpsd is a member of dialout group so it can access /dev/ttyS0)
This means your gpsd should receive gps data stream (double check config options in /etc/default/gpsd). I think it's all about getting fix. The module should work with the internal antenna... if you have external antenna, give it a try.

Read More...

Radek Kaczorek replied to the topic 'Astroberry GPS with Adafruit GPS breakout board' in the forum. 4 days ago

Serial device seems to work.
You need to set port for minicom by running

minicom -D /dev/ttyS0 -b 9600

If you have miniterm.py available on your system you can run:
miniterm.py /dev/ttyS0 9600

... and observe the output - you should get raw NMEA data over serial.

If not... well double check that your gpsd user is in dialout group by running

id gpsd


You can find gpsd config in /etc/default/gpsd

Read More...

Radek Kaczorek replied to the topic 'INDI Control Panel tab in Ekos' in the forum. 4 days ago

Well, in my case I tend to keep INDI Control Panel open all the time... however I use some custom drivers which are not integrated with Ekos. It's probably not everybody's world though. You're right re tabs within tabs, not perfect but might be a trade-off. More opinions are needed on this for sure.

Read More...

Radek Kaczorek created a new topic ' INDI Control Panel tab in Ekos' in the forum. 5 days ago

What about joining Ekos window and INDI Control Panel? I think that placing INDI Control Panel as another tab in Ekos would be good step towards improving user experience. What do you think?

Read More...

Radek Kaczorek replied to the topic 'Astroberry GPS with Adafruit GPS breakout board' in the forum. 5 days ago

First, confirm that serial connection works - try connecting to gps with any terminal emulator e.g. minicom, screen etc. (remember to stop gpsd before testing to free the serial line). If you get NMEA stream of data you're ok, if not, something's wrong with serial communication - check baud rate, double check that rx is connected to tx and tx is connected to rx, check power... Second, if it connects ok, run gpsmon or cgps and make sure your gps device has free access to sky - test it outside. Cold fix takes some time, be patient. If it does not get fix after 5 minutes outside, there's some major malfunction.

Read More...

Radek Kaczorek replied to the topic 'Astroberry Server - wlanconfig' in the forum. 6 days ago

So you have broken it yourself ;-) Anyway, good to know it works again!

Read More...

Radek Kaczorek replied to the topic 'Astroberry Server - wlanconfig' in the forum. 6 days ago

It's not enough information to diagnose the issue. It looks like it's all about network connectivity problem not astroberry server per se. Long boot time might also suggest sd card corruption. Review your boot up logs, they might contain important information.

Read More...

Radek Kaczorek replied to the topic 'Astroberry Server - wlanconfig' in the forum. 7 days ago

Thanks for suggestion Helge. Indeed, an issue with vnc black screen appears from time to time, mostly after restart. I have not found good fix for this. So far in such cases I was removing /home/astroberry/.Xauthority file, restarting novnc service and rebooting. However it is not a solution per se.
I will set hdmi_ignore_edid in /boot/config.txt and we'll see how it goes.

Read More...

Radek Kaczorek replied to the topic 'Image capturing not resuming after guiding abort' in the forum. 1 week ago

rlancaste wrote: Does it still do this today after all the changes I made in PHD2 support in December?

Yes. The issue still exists. I think it might come from PHD2 itself though, because it does not resume guiding after abort. So Ekos just can't do anything about it.
However I have not found anything I can do about it on PHD2 side. Or I'm missing something?

Read More...

Radek Kaczorek replied to the topic 'WLANCONF not working as expected' in the forum. 1 week ago

I have replied to your question in the original Astroberry Server threat. See this post.

Read More...

Radek Kaczorek replied to the topic 'Convert JMI Motofocus to something Ekos can drive' in the forum. 1 week ago

If you can drive your stepper directly, you can use stepper motor controller and a driver. As an example see Astroberry DIY

Read More...

Radek Kaczorek replied to the topic 'Astroberry Server - wlanconfig' in the forum. 1 week ago

Hi Roger. It seems that wireless networks are not discovered with wlanconf-gui... In such a case use wlanconf - open your terminal and run:

sudo wlanconf
You will be asked for network name and password and you're done ;-)

Read More...

Radek Kaczorek replied to the topic 'Image capturing not resuming after guiding abort' in the forum. 1 week ago

Anybody?

Read More...

Radek Kaczorek replied to the topic 'Astroberry Server' in the forum. 1 week ago

The only related setting is the one you have already identified - force_turbo=1. This however is not really about overclocking, instead it fixes cpu clock for secondary serial line. Note that RPi3 comes with 2 serials: one for bluetooth and one for free use (actually you can use both of them while bluetooth is disabled). Secondary serial line speed is cpu dependent so if used force_turbo=1 is a recommended setting. Otherwise the line might get unstable.

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!