Tachyon fails to register & connect - Error "Please check antenna and APN setting!"

Tachyon
1

Hi,

I've been trying to setup a Tachyon with appropriate country code. Attempted the setup a few times and had the device both inside and outside the house.

The local Wi-Fi connection to the Particle Cloud works fine. However, the Tachyon fails to register & connect to a cellular network, with "Please check antenna and APN setting!"

Here's the AT commands output via "journalctl -u particle-tachyon-rild --no-pager".

I would appreciate if someone at Particle can assist. Thank you.

Jul 29 00:59:00 tachyon-16ad9a30 particle-tachyon-rild[3331]: 
Jul 29 00:59:00 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:05 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+CEREG?, Response:
Jul 29 00:59:05 tachyon-16ad9a30 particle-tachyon-rild[3331]: +CEREG: 2,0
Jul 29 00:59:05 tachyon-16ad9a30 particle-tachyon-rild[3331]: 
Jul 29 00:59:05 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:10 tachyon-16ad9a30 particle-tachyon-rild[3331]: Error: Network Registration timed out after 5 minutes!
Jul 29 00:59:10 tachyon-16ad9a30 particle-tachyon-rild[3331]: Please check antenna and APN setting!
Jul 29 00:59:10 tachyon-16ad9a30 particle-tachyon-rild[3331]: Processing: STATUS
Jul 29 00:59:10 tachyon-16ad9a30 particle-tachyon-rild[3331]: Signal Strength: 0 (0-31) / -113dBm, RSRP: 0dBm, RSRQ: 0dB, RSSNR: 0.0dB
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: MCCMNC: unknown, LAC: 0, CID: 0, ACT: unknown, CARRIER: unknown
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: data_connection: down
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Registration State: Not Registered, Not Searching, Registration Denied Reason: 0
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Processing: CONNECT
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Registering to Cellular Network...
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: ICCID currently active: 89430520xxxxxxxx (KDDI SIM)
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Active SIM: 1 (INTERNAL)
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Using APN: "kddi.m2m.drei.at"
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+QNVR=5280,0, Response:
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: +QNVR: "0102000000000000"
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: 
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: ATE0, Response:
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+QNVFR="/nv/item_files/ims/IMS_enable", Response: +QNVFR:
Jul 29 00:59:11 tachyon-16ad9a30 particle-tachyon-rild[3331]: 00
Jul 29 00:59:12 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+QNVFR="/nv/item_files/modem/mmode/sms_only", Response: Command: AT+QNVFR="/nv/item_files/modem/mmode/sms_only", Response:
Jul 29 00:59:12 tachyon-16ad9a30 particle-tachyon-rild[3331]: ERROR
Jul 29 00:59:12 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+QNVFR="/nv/item_files/modem/mmode/ue_usage_setting", Response: +QNVFR:
Jul 29 00:59:12 tachyon-16ad9a30 particle-tachyon-rild[3331]: 01
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: ATE1, Response:
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: Get Preferred network type: 24 (NR5G TD-SCDMA LTE CDMA EVDO GSM WCDMA)
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+CGDCONT?, Response:
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: +CGDCONT: 1,"IP","kddi.m2m.drei.at","0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: 
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+CEREG=2, Response:
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: OK
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: Command: AT+COPS?, Response:
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]: +COPS: 0
Jul 29 00:59:13 tachyon-16ad9a30 particle-tachyon-rild[3331]:
2

Could you DM your ICCID and country to @support? Click on the link and select Message.

3

Hi Rick,

Thank you for the quick response.

4

@zpm1066 Your device is impacted by a known cellular issue that we will fix this week. We also moved your device to a roaming list with a temporary quick fix, so your Tachyon should connect to cellular today.

1 Like
5

Hi @laupow , Thank you. Is the APN correct?

I tried rebooting the Tachyon a few times, unfortunately there is still no cellular connectivity.

Also, WiFi connectivity isn't showing location.

Please advise if there is anything I need to do on my end. Thanks.

6

Hi @laupow, unfortunately the “temporary quick fix” isn’t working. I’m still unable to get cellular connectivity.

7

@zpm1066 I'm curious if your device has finally registered to the cellular network and doesn't have connectivity, or if it's just not registering? BTW: The APN is correct for that SIM.

8

Hi @BDub,

Yes!

After seeing your message, I rebooted the Tachyon (currently with the Ubuntu desktop version, as I was waiting for the cellular issue to be resolved) and behold the familiar breathing cyan led.

The tachyon has registered with the local carrier’s home network with NR5G (5G). Also, location map with cellular method shows up in the Particle Console. Thank you!

Do you know what was the issue?

A couple of things I noticed

  • Console > Tachyon > View device > Networks shows both Wi-Fi and Cellular connections, the “Last vitals” on the right hand side only displays the Wifi-Fi signal
    Is this because the Wi-Fi signal is stronger than the cellular?
  • particle-tachyon-ril-ctl state (Tachyon displays breathing cyan led)
    Connected
  • Console > Tachyon > View device > SIMs, there are two ICCID entries, both active. However, the first entry shows eSIM status “Installed” and the second as “Active”.
    What is the first SIM entry for?

What’s the best way to turn off Wi-Fi or Is it best to just leave it on when not on the road?

I do plan to ssh with tor once the reported issue gets resolved.

Regarding AT commands, Are you using a “SG560D AT Commands Manual”? I couldn’t find a specific SG560D version from Quectel.

Cheers!

9

Hi @zpm1066 ,

Great news! Glad you have it connected now. I know they have been working on the configuration for your country in the background. Not sure what the specifics are.

Console > Tachyon > View device > Networks shows both Wi-Fi and Cellular connections, the “Last vitals” on the right hand side only displays the Wifi-Fi signal
Is this because the Wi-Fi signal is stronger than the cellular?

This is because your default connection will be prioritized currently as Ethernet > Wi-Fi > Cellular, so right now if you have Wi-Fi and Cellular connected… the default traffic is over Wi-Fi.

Console > Tachyon > View device > SIMs, there are two ICCID entries, both active. However, the first entry shows eSIM status “Installed” and the second as “Active”.
What is the first SIM entry for?

There are two SIM profiles on Tachyon that are activated during setup based on your Country. So you can safely ignore the non-active one.

What’s the best way to turn off Wi-Fi or Is it best to just leave it on when not on the road?

Probably best to leave it setup so it will take over when you are in range of the Wi-Fi access point, and save cellular data. Here’s the page on Wi-Fi commands. If you wanted to turn it off or remove it, the commands are listed here: WiFi | Particle Developer

Regarding AT commands, Are you using a “SG560D AT Commands Manual”? I couldn’t find a specific SG560D version from Quectel.

I would say it’s not recommended to use raw AT commands at this time, certainly not for trying to configure the device. This should all be handled automatically. What types of things are you looking to do? There are probably a few more particle-tachyon-ril-ctl commands we need to document that might help.

10

@laupow Hi Matt,

Thank you for resolving the cellular connectivity issue. It's much appreciated.

1 Like
11

Does this mean that with Ethernet - WiFi - cellular all active and a breathing cyan led, all the traffic will be over Ethernet?

12

Yes, Ethernet will take priority over Wi-Fi, and Wi-Fi would take priority over Cellular.

The LED will breathe Cyan if Cellular is connected, and Magenta if only Wi-Fi and/or Ethernet is connected but not Cellular. If nothing is connected it will breathe Green.

13

@zpm1066 I’m glad to hear the cellular connectivity fix worked! :+1: