Troubleshooting

Please make sure you always use the latest firmware version. Here's a video which shows how you can upgrade to the latest firmware instantly without waiting for the scheduled automatic upgrade:

Do NOT unplug the openSPOT2 during the firmware upgrade!

If you can't find an answer to your issue, then please send an email to us, or ask help in our community forum!

The web interface can't be opened

Use SharkRF Link to open the web interface.

Make sure your web browser device (phone/tablet/computer) is connected to the same network the openSPOT2 is using.

Check if the openSPOT2 is connected to the Wi-Fi network by looking at it's LED. Please see the LED states section for possible LED states. If the openSPOT2 is not connected to the Wi-Fi network according to the LED, see the next troubleshooting question's answer on how to set up the openSPOT2's Wi-Fi connection.

The openSPOT2 can't connect to the Wi-Fi network

Here's a video which shows how to switch the openSPOT2 to AP mode and connect it to a Wi-Fi network:

Please see the Connecting the openSPOT2 to a Wi-Fi network section for the detailed description of the steps required to set up the openSPOT2's Wi-Fi connection.

The openSPOT2 can't connect to my phone's Wi-Fi network

Note for iPhones: the phone's hotspot settings page needs to be open all the time during the openSPOT2 Wi-Fi setup because the iPhone will only broadcast it's own Wi-Fi network if the internet share hotspot settings page is open.

First you should connect your openSPOT2 to your home Wi-Fi network and then when it's connected (LED is green or green/yellow) open the web interface using sharkrf.link. After that you can set up additional Wi-Fi networks if you turn on Advanced mode (checkbox at the bottom right corner of the web interface) and go to the Network page, Wireless settings section. Enter your phone's hotspot SSID and key as the 2nd Wi-Fi network.

After that if the openSPOT2 can't connect to your home Wi-Fi network it will also try connecting to your phone's Wi-Fi network.

I'm not hearing anything on my radio

Please read the Setting up your transceiver section.

Check if your radio's LED is on when the openSPOT2 is transmitting. The openSPOT2 is transmitting if it's LED is blinking red:

If it's blinking alternating red/orange, then BCLO is on:

If this is the case then make sure it's turned off by setting it to 0 at the Other modem settings section.

If your radio's LED does not turn on when the openSPOT2 is transmitting, then make sure they are on the same RX and TX frequencies.

Make sure the openSPOT2's modem is set to the same mode as your radio, and the following settings are set:

  • DMR radio: the color code (CC) match in your radio and the openSPOT2 (example: set it to the default 1). Make sure the talkgroup you want to hear is set as the TX contact of your DMR radio's currently active channel, or the talkgroup is in an RX group list which has been assigned to the currently active channel. You should also add TG9 to your the RX group list and assign it to the currently active channel to hear the openSPOT2's voice announcements.
  • C4FM radio: the DGID is set to the same value both in your radio and the openSPOT2 (example: set it to the default 0).
  • NXDN radio: the radio access number (RAN) match in your radio and the openSPOT2 (example: set it to the default 0). Make sure the talkgroup you want to hear is in your NXDN radio's contact list, or it is set as the TX contact of the currently active channel.

No one is hearing me on the network

Please read the Setting up your transceiver section.

Check where your radio is sending your call by looking at the Call log on the openSPOT2's web interface. Make sure your radio is sending the call to the desired talkgroup or reflector.

The openSPOT2's LED should blink green when you press the PTT on your radio:

If not, then make sure the openSPOT2 and your radio are on the same RX and TX frequencies.

Make sure the openSPOT2's modem is set to the same mode as your radio, and the following settings are set:

  • DMR radio: the color code (CC) match in your radio and the openSPOT2 (example: set it to the default 1).
  • C4FM radio: the DGID is set to the same value both in your radio and the openSPOT2 (example: set it to the default 0).
  • NXDN radio: the radio access number (RAN) match in your radio and the openSPOT2 (example: set it to the default 0).

The openSPOT2 can't connect to the selected server

If the LED is pulsating like this, then the openSPOT2 is trying to connect to the selected server, but it can't for some reason. If it's not pulsating like on the animation, check the LED states section for more information about the current LED state.

The server may be currently offline, or there may be a connection issue between your openSPOT2 and the server. You can try using another server, or enable the Override DHCP DNS servers setting.

Also check if the server password is set correctly (in case there's a server password), and that your connector settings are valid (example: if there's a callsign setting, make sure your callsign is valid, if there's a DMR/CCS7 or NXDN ID setting, make sure your ID is valid for your callsign).

If you want to connect to the BrandMeister network, and the openSPOT2 won't connect to any BrandMeister server, then make sure you use the hotspot security password you've set on your BrandMeister SelfCare page (or turn off hotspot security so the default server password can be used).

There are dropouts in incoming calls, voice is stuttering

Make sure you use a server nearest to your location to avoid network dropouts and high latency. Please keep in mind, that packet loss and high latency can occur in VoIP (Voice over IP) streams even if you have a really high quality network connection.

Check the dejitter queue graph on the Status page for invalid seqnum errors. These indicate that the openSPOT2 does not receive all network packets so there are missing parts from the incoming call's stream.

If there are no invalid seqnum errors, but the dejitter queue graph shows that the queue gets empty during a call, then you can try increasing the dejitter queue length at the Network settings section.

Try to set another Wi-Fi channel in your Wi-Fi network (see the next troubleshooting entry for more info). The currently used one may be overcrowded, which you may not notice during web browsing, as the web uses a protocol which resend missing data frames, but this can't be done in real time VoIP streams so the packet loss issue becomes instantly noticable.

Wi-Fi disconnects (blue LED) or internet connection errors (red/blue LED)

Try to set another Wi-Fi channel in your Wi-Fi network. The currently used one may be overcrowded. It is advisable to use Wi-Fi channels 1, 6 or 11. Do not use the others as they only cause more interference. Also try placing the openSPOT2 closer to your Wi-Fi router / access point.

Color code mismatch warnings on the web interface

Make sure the color code programmed for your radio's current channel is matching the openSPOT2's color code. If they match, then probably there's an offset between the radio's TX frequency and the openSPOT2's RX frequency. Please try to use AutoCal, or manually enter different frequencies in +-100 Hz steps at the RX offset on the Modem page.

The device can't check firmware upgrades, it shows retrying

Make sure the NTP, HTTP and HTTPS outgoing traffic is not disabled in your router's firewall. You can also try turning the Use DHCP server if available option off.

The device does not turn on, the LED is dark

Probably the openSPOT2 was plugged out during a firmware upgrade. Press the button and the upgrade process will continue. If the LED is still dark and there's no way to get it light up, contact us at info@sharkrf.com.

results matching ""

    No results matching ""