Skip to content

Latest commit

 

History

History
218 lines (180 loc) · 16.6 KB

troubleshooting.md

File metadata and controls

218 lines (180 loc) · 16.6 KB
Raw

Home | Hardware Guide | Installation Guide | Using Stellarium | Using Nina | Troubleshooting | FAQ

Troubleshooting

Benro Polaris Troubleshooting

B1 - Cannot start the Benro Polaris Device.

There is a known issue with the recommended Benro Polaris device startup procedure. "Power On. In the off state, double press and hold the [Power Button], and release it after hearing “beep beep beep” three times to turn on the device. ". Its worse than an old lawnmower at starting. If your device doesnt start, try the following:

  1. Remove Power cable - Dont have the Benro Polaris charging, while trying to start.
  2. Send to Park - use a Long Press to send the Benro Polaris to the parked position and ensure Power LED is off.
  3. Short Press - Every second or so (but no faster), until Power LED is illuminated.
  4. Long Press - As soon as its illuminated, do a long press, releasing after "beep, beep beep".

Another word of caution. Do not travel with the Astro USB cable or Camera USB Cable plugged into the Benro Polaris. There is a chance that movement within your bag may damage the cable. This can even lead to damage of the Benro Polaris and costly repairs.

B2 - Cannot connect BP App to the Benro Polaris Device

Sometimes the BP App cannot search and connect to the BP over Bluetooth or Wifi. The Searching for device might list your device in white but it never turns green or connects or shows a green check-mark.

  • Fully exit close the BP App on your phone.
  • Reset all Bluetooth and Wifi communications on your phone. Easiest way to do this is to toggle Airplane/Flight Mode on and off.
  • Restart the BP App and it should find and connect to your BP.

B3 - Polaris has poor quality Sidereal Tracking

As an Alt/Az mount, the leveling of the Benro Polaris Tripod Head is a critical factor in the accuracy of your star tracking. To adjust the Polaris so it is as level as possible：

B4 - The Polaris cannot connect to my Home Wifi

The current firmware of the Benro Polaris does not allow connection to other WiFi networks. It can only host its own Wi-Fi hotspot.

This is no longer a limitation. The Alpaca Benro Polaris Driver can serve as a proxy for the Polaris. It is capable of connecting to both the Polaris Wi-Fi Hotspot and your home Wi-Fi network. This allows you to manage the Polaris from any device connected to your home Wi-Fi, including an iPad, a phone, a desktop, or a laptop.

Alpaca Communications Troubleshooting

C1 - Cannot see "communications init... done" in the log.

  • Use the Alpaca Benro Polaris Driver log window to help diagnose your problem. The messages aim to help point you in the right direction. The driver will continue to retry connecting until you have resolved any issues.
  • Confirm the Benro Polaris is in Astro Mode.
  • Confirm the Benro Polaris Compass and Star Alignment steps are complete.
  • Confirm the Benro Polaris App is still running (we hope to remove this requirement).
  • Confirm your Cammera hasn't gone to power save mode.
  • Confirm the mini-PC has connected with the polaris-XXXXX hotspot. It should look like the following:

C2 - Cannot see any log message except two INFO ==STARTUP== lines

  • Check your device doesnt have any IT policy to not allow connecting to an open WIFI like the Polaris Hotspot.
  • Check which Wifi adapter is being used. There is a known issue with the Mele Quieter 4C not being able to connect to the Polaris Wifi. Do not use the MediaTek RZ616 Wi-Fi 6E 160MHz (Driver version 3.3.0.595) built in Wifi Adapter. Use the TP-Link AC600 USB WiFi Adapter instead.
  • Check your IP Configuration using a Command Prompt to run ipconfig.exe. Ensure your Mini-PC has a valid IP Address from the Benro Polaris DHCP server. It should look like the following:

C3 - Connection from Mini-PC to Polaris Wifi drops out

  • We originally required the BP App to remain running in the background. This is no longer the case. You can close the BP App once you have the Polaris WiFi established and the Driver connected. With the BP app closed you can save on Battery usage. The Driver will keep the Polaris Wifi up and continue to allow operation.
  • Check for RF interference. eg. Turn off your microwave in the kitchen.
  • Check for RF signal strength. Move your remote desktop machine closer to the mini-pc.
  • Check resouce usage on mini-PC. Ensure it has plenty of free ram and CPU.

C4 - Still cannot get communications with Polaris Wifi

To further help diagnose communication problems between ABP and the Polaris, you can use Telnet or PuTTY to directly connect to the Polaris. This will isolate whether the problem is ABP related or not.

On Win11:

  • Use the following link to Download PuTTY (a telnet client) to your device running the Driver.
  • Select the 64-bit x86 version for the Windows installer.
  • Double click on the file you downloaded to install PuTTY.
  • Perf the normal BP App setup (a) Search for Device (b) Connect to polaris_xxxxxx (c) Select Atro Mode (d) Align Compass (e) Align Star (f) Confirm.
  • Connect the Device running ABP to the Polaris Wifi Hotspot.

  • Run the PuTTY app.

PuTTY Setup

  • Enter 192.168.0.1 into the HostName (or IP address) field.
  • Enter 9090 into the Port field.
  • Select Connection Type Other and drop down Telnet.
  • Click Open
  • Select Yes when asked by User Account Control, Do you want to allow this app to make changes to your device? This opens the firewall to allow PuTTY to communicate with BP.

The PuTTY application should show a window with the raw communications from the Benro Polaris. If your connection is working it should look like the following, constantly scrolling.

PuTTY Setup

C5 - No Telnet/PuTTY communications with Polaris Wifi

If you cannot see the raw communications scrolling in PuTTY from Troubleshooting Step C4, then there is a problem communicating with your device that is independant of Alpaca Benro Polaris Software.

  • Check the Signal Strength of the Polaris WiFi hotspot at your ABP device. You may need to move the device running ABP closer to the Benro Polaris.
  • Check you are not running AntiVirus Software that may block open Wifi Connections
  • Check you do not have an IT or Windows policy blocking open Wifi Connections.
  • Check you do not have a Virtual Private Network (VPN) enabled.
  • Check for IP connectivity to the Polaris by using a Command Window to ping the Benro Polaris.
C:\Users\Astro> ping 192.168.0.1
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Astro>
  • If the ping does not respond within a few milliseconds, go back through C1-C3 to double check the setup.

Nina Troubleshooting

N1 - Cannot Remote Desktop to MiniPC running Nina

  • There are a range of remote desktop applications avalable which you might want to try:
    • Microsoft Remote Desktop - Free with Windows 11 Pro. Some testers have had issues connecting via MS Remote desktop. I've been using it quite successfully.
    • AnyDesk - "Best remote desktop solution for occasional users" - Techradar. Successfully used by a beta tester.
    • Splashtop - "Powerful remote desktop with impressive features" - Techradar. I've used this on my home network successfully.
    • TeamViewer - "Best remote PC software for cross-platform compatibility" - Techradar.
    • RemotePC - Short free trial.
    • LogMeIn - Lacks a free trial.
    • Zoho Assist - Free tier very limited.
  • When using AnyDesk and certain other programs, you might need to use an HDMI Dummy Plug to get video output from the mini PC if a monitor is not connected. Microsoft Remote Desktop Client does not require this, but it may not be available for some mobile devices.

N2 - I still cannot remotely connect to the MiniPC running Nina

  • Windows Updates can be delivered every month that may effect the state of the device.
  • Check Mini-PC state. Reconnect a monitor and Keyboard to the Mini-PC and check that it is up and running.

N3 - I have a Mini-PC running without internet access. I cannot remotely connect to it.

  • This type of configuration is more challenging and can be confusing, but it is possible.
  • There are two Wifi Hotspots in this configuration, the BP Hotspot and the Mini-PC Hotspot.
  • Check that your laptop has not dropped connection to the Mini-PCs hotspot.
  • Check IP connectivity. From a command prompt, use ping <hostname> to ensure you have IP connectivity and DNS lookup to your Mini-PC.
  • You may find using the Mini-PC's IP4-address in Remote Desktop rather than <hostname> may make it easier to connect.
  • Check that the MiniPC Hotspot is not using the TPLink. You can unplug the TPlink to force the MiniPC hotspot to use the embedded Wifi of the Mele.
  • Once you have connected to the Mini-PC via Remote Desktop, then re-plug in the TPLink, to allow ABP to use it to connect with the BP Hotspot.

N4 - Which Mount should I select in Nina's Equipment Tab, it lists 8 Benro Polaris Mounts?

  • The ABP defaults to broadcasing ASCOM Alpaca services on all network interfaces on the MiniPC.
  • If you have the ASCOM Platform installed, Nina will also detect all the ASCOM direct interfaces to the ABP.
  • We recommend connecting to the ABP via ASCOM Apaca services rather than ASCOM. Choose one of the Mounts under ASCOM Alpaca.
  • You can limit what IP Address the driver exposes the ASCOM Alpaca Service on, by setting the field alpaca_ip_address in driver/config.toml.
  • To limit the Alpaca Service only to applications that are running on the Mini-PC (ie no remote applications), set it the following.
alpaca_ip_address = '127.0.0.1'

N5 - Cannot obtain a good autofocus run with Nina?

  • Check your Lens Stabilisation is off. This interfers with sidereal tracking.
  • Check you Lens AutoFocus is off on the Lens and Camera Body. If left on this may cause the camera focusing system to hunt interering with the image capture process.
  • Check for Lens Cap not removed. Not kidding.
  • Check for clouds.
  • Check for haze or smoke.
  • Check for occulusion by trees or buildings.
  • Check for that you are close to focus before starting a Nina Focus run.

N6 - Cannot plate solve with Nina and ASTAP?

  • Check you are in Focus
  • Check to make sure you camera pixel size and telescope focal length is set correctly in equipment options, including any reducer or extender. Plate solving wants an approximately correct field of view as input and frequently fails if not set to the right values.
  • Check if you are using any filters. Using a narrow band filter on the camera, like the L-Ultimate Optolong HaOIII filter, can make plate solving more challenging for ASTAP.### R1 - Cannot connect Remote Desktop to Mini-PC
  • Check you have downloaded the relevant STAR databases. For 200mm lens and less you may need to download the Wide field STAR database G05

N7 - Cannot Connect Sony Camera with Nina

Some later models of Sony cameras (e.g., Sony Alpha 7R IV) are not recognized by the Sony Plug-in that is included with Nina. To resolve this:

  • Attach your camera via USB. Configure as you would to connect to the Polaris.
  • Turn on your camera.
  • Enter Device Manager in the Windows desktop search bar.
  • Click on the Device Manager icon to open the Device Manager.
  • Check for the linr libusbK Usb Devices.
  • If the line does not exist, close the Device Manager. You are correctly configured.
  • If the line libusbK Usb Devices exists:
    • Left-click on the entry to expand the entry. You should now see Sony Remote Control Devices.
    • Right-click on Sony Remote Control Devices and select Update Driver.
    • Select Browse my computer for drivers.
    • Select Let me pick from a list of available drivers on my computer.
    • Left-click on MTP USB Device.
    • Your driver should now update. NOTE: Your camera is now listed under Portable device. Other software may not function correctly with the Device Manager configured this way.
    • You can change back to the original setting by following these steps and selecting libusbK Usb Devices as the new driver instead of MTP USB Device.

Nina will now connect to your camera.

Stellarium Troubleshooting

S1 - StellariumPLUS Cannot Connect to ABP

There are three approaches to connect StellariiumPLUS to the ABP, depending on your setup scenario.

  • Scenario A: The ABP device conencts to Polaris Hotspot only.
    • Connect your phone to the Polaris Hotspot.
    • In Stellarium's Observing Tools Setup, enter a Network Host of 192.168.0.3
    • You may need to disable Mobile Data on your phone to get this to work.
  • Scenario B: The ABP device connects to Polaris Hotspot and your Home Wifi.
    • Check that the BP App is closed. This frees the phones Wifi from the Polaris Wifi.
    • Check that your phone does not autoconnect to the Polaris Wifi.
    • Connect your phone to your Home Wifi.
    • In Stellarium's Observing Tools Setup, enter a Network Host of 192.168.X.XXX
    • This address needs to match the IP address of your ABP machine on your Home Wifi.
  • Scenario C: The ABP device connects to Polaris Hotspot and has its own NinaAir Hotspot.
    • Check that the BP App is closed. This frees the phones Wifi from the Polaris Wifi.
    • Check that your phone does not autoconnect to the Polaris Wifi.
    • Connect your phone to the NinaAir Hotspot.
    • In Stellarium's Observing Tools Setup, enter a Network Host of 192.168.X.XXX
    • This address needs to match the IP address of your ABP machine on your NinaAir Wifi.

S2 - Still Cannot Connect StellariumPLUS to ABP

  • Check IP connectivity. You must run StellariumPLUS on a mobile device that can communicate with the ABP driver. Use a free mobile Ping app to check that you can ping the ABP driver device. If you cannot ping, then check that you are not using the phone's mobile data, that you are within range of your router's Wi-Fi signal, and that your phone is connected to your home Wi-Fi.
  • Check the StellariumPLUS Host field on the Observing Tools settings popup. This needs to be set to the ABP Driver's IP address. Do not use 127.0.0.1 Loopback.
  • Check stellarium_telescope_ip_address in config.toml. This can be left as its default '' to make the Driver serve the SynScan protocol on any network adapter it can find. If you want to limit the IP address servered by the Driver, you can set this to the IP address of the Mini-PC on your home network.

S3 - Stellarium Desktop has greyed out ASCOM option

  • One Beta Tester encountered problems connecting Stellarium Desktop v24.3 for Windows via ASCOM.
  • Symptom: When trying to add a telescope in Stellarium's telescope plugin, selecting an ASCOM device is greyed out.
  • Solution: Uninstall V24.3, restart your desktop, install V24.2 (available by searching on the download page). Check periodically for an update to Stellarium.

S4 - Stellarium Desktop freezes with Remote Desktop

  • Check fps settings. Stellarium's default is a crazy 10000 fps. We suggest reducing the default settings in the following file C:\Users\Nina\AppData\Roaming\Stellarium\config.ini, where Nina is replaced with your User name. 
    [video]
...
maximum_fps                               = 10
minimum_fps                               = 10
...