×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Astroberry 2.0.1 Hotspot vs Win10 - connection problem

  • Posts: 10
  • Thank you received: 0
Thanks again,

Will try all that from scratch...

And why did I changed GPSD at all?
All of them I did before you wrote me :( as initially it was not working at all, gpsmon was simply empty, - now it shows something (at least!) :) and all these steps I wrote, were offered on Indi for astroberry or other sites for rPi.

P.S.
On windows, I was able to get data coming via its own software, but was not able to link it to EQMOD or SGP.

Anyway, - nice to know it should work almost out of the box
Last edit: 3 years 10 months ago by Roland.Kol.
3 years 10 months ago #53874

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74
Hi

Another possible idea especially for RTC and power management - read this thepihut.com/products/wittypi3-rtc-power...ent-for-raspberry-pi.

No GPS though :-(
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
The following user(s) said Thank You: Roland.Kol
3 years 10 months ago #53947

Please Log in or Create an account to join the conversation.

  • Posts: 10
  • Thank you received: 0

Sorry to bother again,
Can you please check how does your gpsmon window look?
Does it show U-Blox at the top or NMEA?
I tested my GPS dongle on windows, - it catches all the data and gets the fix even indoors and within 60sec.
So checked it on the fresh Astroberry install and outside (so none of my initial adjustments were in action) and I had GPS fix, - and fast, 20sec or something.
But..
Only once... After rPi reboot, - nothing... It looks like data is coming in, - but no fix.
Tried to re-plug, to stop/disable Virtual GPS, - no luck..
However, I have noticed what sometimes gpsmon service shows U-Blox, sometime NMEA on the top....
also, not sure why, - data/time is sometimes correct even without the fix and sometimes it is 2019 April...

Last edit: 3 years 10 months ago by Roland.Kol.
3 years 10 months ago #54146
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74
I would bring it up with @Radek - with logs etc see if he can see anything.

But mine shows - see attached

But agree its flaky - hardware/software or both.
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
3 years 10 months ago #54147
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74
Tried rebooting a number of time and removing and reinserting Ublox (which normally works) - GPSMON just hangs even though systemctl said gpspanel and gpsd services were active. Noticed that GPSMON in my case showed JSON XXXXXXXXX where hardware device name is normally :-)

So shurdown - disconnect power lead,waited 30 secs ,started PI and see attached. Flaky IMHO hence I just set the things(Time,Location) manually - I dont get enough clear skies time !

Other thing to check is power - Are you fully connected with all your devices and are you using a powered Hub - guessing really!
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
3 years 10 months ago #54148
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 10
  • Thank you received: 0
Thanks a lot for a extremely fast reply.

I do not want to bother Radek with such a small issue, he already did more than enough, dont want to waste his time.

One thing I noticed on your print screens, -
initially before your GPSMON got fix, it had the first row "tcp://localhost:2947"
once fix got
it became "/dev/ttyACM0" - this is actually the USB slot GPS dongle is attached....

In my case, it remains on tcp://localhost:2947 for ever....
So maybe, my initial tries to direct all to ttyACM0 were correct...
Will give a try once again...

P.S.
As per power: I guess all is OK, as rPi is fed by original and independent power source.
GPS dongle is connected directly to rPi...
Also, I do have USB hub connected to rPi (which has cameras connected), - but the Hub is also powered externally..
Last edit: 3 years 10 months ago by Roland.Kol.
3 years 10 months ago #54150

Please Log in or Create an account to join the conversation.

  • Posts: 10
  • Thank you received: 0
Just one more observation:

cat /dev/ttyACM0 and
cat /dev/GPS0
both show U-Blox data stream which looks the same. (Data about U-blox manufacturer and some kind of numbers and letters, some of them look like coords: N*53 or N*30 and etc).
3 years 10 months ago #54155

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74
If you dont know already maybe this will help

gpsd.gitlab.io/gpsd/troubleshooting.html

gpsd.gitlab.io/gpsd/faq.html

indilib.org/forum/astroberry/6128-using-...stroberry-2-0-0.html

And maybe with your device and Astroberry HOTPLUG doesn't work - but it does on std Raspbian. Anyway it appears you might have to edit the devices file.

"Regarding hot-plugging GPS - it works for USB devices but does not work with hardware serial port (/dev/ttyACM0). To use hardware serial port you need to either edit /etc/default/gpsd and set DEVICES or you can leave the file alone and run: sudo gpsdctl add /dev/ttyACM0
To make the second approach persistent you can add gpsdctl add /dev/ttyACM0 to /etc/rc.local "
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
3 years 10 months ago #54164

Please Log in or Create an account to join the conversation.

  • Posts: 169
  • Thank you received: 3
Edit - I went into the Advanced Network Configuration and saw where it said it had connected to my 2.4GHz network a few hours ago. I manually configured things to connect to that network and I am at least on that network now. Does it not support 5.8GHz?

I've a similar problem re: wifi network/hotspot.

My old Pi4 running Astroberry 2.0.1 died suddenly, and today I received a replacement. I thought I could simply pull the uSD card from the defective one, plug it into the new one, and presto. But this Pi4 is not working the same as the old one. It apparently does not detect my internal network. So, it comes up in hotspot mode.

Funny enough, Stellarmate OS did exactly the same on the old Pi4, the primary reason I switched to Astroberry. Thoughts?

Thanks!
Last edit: 3 years 9 months ago by Paul Nixon.
3 years 9 months ago #54911

Please Log in or Create an account to join the conversation.

  • Posts: 19
  • Thank you received: 3
My guess is that because of new RPI4, all the MAC address's are new, and all your past network connection will have the old RPI4 MAC address's you need to create new connections. the hot spot would have self setup.
3 years 9 months ago #54912

Please Log in or Create an account to join the conversation.

  • Posts: 76
  • Thank you received: 5
I found that the 5 GHz connection will not work unless you set your country in the raspberry configuration. The only issue with this is that the country code doesn’t stick after you reboot. I’ve stop troubleshooting this as the 2.6 works better at distance and through solid objects like doors and windows. 5 GHz is actually slower where my scope is.
3 years 9 months ago #54925

Please Log in or Create an account to join the conversation.

  • Posts: 983
  • Thank you received: 375
elken2004 could be right. MAC addresses could saved in your network profiles. Go to network config icon in top bar and remove MAC addresses, leaving just wifi network interface name.
Another cause coud be wifi country/region.
3 years 9 months ago #55038

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 1.540 seconds