Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_dslr_mirrorlesss.thumb.jpg.5b348d6a5e7f27bdcb79e9356b7fc03b.jpg

RadekK

Members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

38 Excellent

About RadekK

  • Rank
    Nebula

Contact Methods

  • Website URL
    https://www.astrobin.com/users/radical/

Profile Information

  • Gender
    Male
  • Location
    Warsaw, Poland
  1. Looking for triplet APO with focal length up to 480mm.
  2. I used it for fun but apparently it's pretty useless for astro. At the most it can indicate actual position of a scope in remote observatories... still a cheap ipcam is better. You will never get a >1 arcmin precission with it compared to astrometry / plate-solving.
  3. This is correct. AFAIK ethernet port (1Gbps) is still using USB 2.0 bus. WiFi is using SDIO pins on BCM chip. So in 3B+ USB ports compete with Ethernet, and WiFi competes with... SD card
  4. ASIAir uses generic Raspberry Pi. The same applies to Stellarmate. Astroberry is designed for Raspberry Pi 3B and 3B+ as well. As the matter of fact you can use any single board computer (SBC) to run KStars/Ekos and INDI as far as you connect everything to USB and don't use GPIO for custom devices (e.g. focuser, relays, temperature sensors etc.). The biggest bottleneck for Raspberry is 1GB of RAM. Another issue is single communication bus for all USB ports, ethernet and wifi. Running KStars/Ekos sessions over network (so the images are transferred to PC after capture) is not only slow (intrinsic to network bandwith) but also risky - any network problem will abort session, which is on the PC side, and not Raspberry side. The recommended approach is all-on-raspberry controlled over network as a remote desktop - this way only screen and keyboard are using bandwidth, you can disconnect PC anytime and even leave Raspberry connected 24/7 (e.g. when using Ekos Scheduler which fully automates your observatory).
  5. Looks like backlash in DEC. Don't use Auto in DEC, instead set North or South direction for DEC guiding.
  6. I'm aware of the project but haven't used it. I'm afraid I can't help in this very case
  7. First of all if the disk sounds noisy, there's little chance you can recover. This might be mechanical problem of disk head scratching disk plates. If it runs smooth you can still try recovering data from it with recovery tools. I wouldn't expect too much from Windows builtin tools. Use a live cd that can help you with recovery e.g. https://www.ultimatebootcd.com/ or https://www.hiren.info/pages/bootcd
  8. All you need for going wireless is 5V compatible Bluetooth Adapter. No need for Synscan handset nor it's modification. Take a look at EQDIR.
  9. Don't worry ? Anyway I need to review WLAN/VAP scripts because ppl have problems with them. I will keep you posted.
  10. Can we fix it? Yes we can! I come to serve ?
  11. I have just checked and tested: KStars 3.1.0 (kstars-bleeding 6:3.1.0+201902271506~ubuntu16.04.1) indi-atik 2.1~201902271934~ubuntu16.04.1 libatik 2.2.4~201902271745~ubuntu16.04.1 The above works without problem whatsoever. NB. KStars version does not matter, it is drivers' version which matters. However I see that the latest ATIK drivers available are: indi-atik 2.2~201903091424~ubuntu16.04.1 armhf [upgradable from: 2.1~201902271934~ubuntu16.04.1] libatik 2.2.5~201903091345~ubuntu16.04.1 armhf [upgradable from: 2.2.4~201902271745~ubuntu16.04.1] I haven't installed these yet. BTW. you can easily check your versions by running "dpkg -l|grep atik"
  12. Let's do a quick review of configuration 1. Networking Your /etc/network/interfaces should contain: auto wlan0 iface wlan0 inet dhcp wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf 2. WLAN Your /etc/wpa_supplicant/wpa_supplicant.conf should contain at least: network={ scan_ssid=1 ssid="$SSID" psk="$PSK" } where $SSID is your wireless network name and $PSK is your wireless password With only these two configuration files you should successfully connect to your home network. No other tricks are necessary. If you cannot connect despite proper configuration we have some major issue here and need to debug it with logs review i.e. /var/log/syslog You can disable VAP autoconfiguration by editing /etc/rc.local file. Just comment out the line with check-wlanconn so it looks like: #check-wlanconn > /dev/null 2>&1 This way artificial intelligence embedded in Astroberry Server will not mess with standard networking configuration described in points 1 & 2 above. After thius, you can run check-wlanconn and astroberry_vap scripts manually to play with VAP. BTW. What is you RPi version (3B or 3B+)? Does your home AP support AC mode? Does your PC support AC mode? BTW2. Take a look at the last but one question in FAQ
  13. Take a look at this guide: https://indilib.org/download/ubuntu.html Activate nightly builds and check if EFW2 work OK. Stable versions are released much less frequently, so you could have not got the update yet. Anyway, I use EFW2 and have not noticed the issue with the latest driver. Actually I have noticed the problem but it was related to USB port on EFW2, which was soldered really badly and I found out it lost connection to USB pins. After resoldering everything works OK. You can check it out - just open EFW2 and inspect USB port - if it swings this might be a problem. I was really surprised how badly it was mounted by Atik guys on the main controller board.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.