Just received the Tachyon and after having to run the onboarding and downloading journey a couple of times before it worked, have a connectivity issure relatd to the cellualr modem and its TCP/iP connectivity.
Device is connected to both WiFi and to the cellular provider, running ifconfig shows that we have connection and an IP address for both WLAN0 and RMNET_DATA0, the connectivity is in place so the web based front end works.
Ping or traceroute to a random site (www.yahoo.com) works.
The web console shows that the SIM card is enabled and connected to the service provider.
However, I will be using the device remotely and need to access via ssh without the WiFi, via cellular connection. I will connect via ssh via TOR or through ssh via Zerotier (no issues about connectivity in any other device I use this with)
So, turn off the WiFi (sudo ifconfog wlan0 down), should still maintain a connection to the web console or be accessible via TOR SSH or via Zerotier via the cellular connectivity...... Except it doesn't work.
If I console in directly and now try and ping to www.yahoo.com, nothing happens, connectivity via TOR or Zerotier is no longer operative.
Status light goes from breathing blue to breathing green
Not useful, makes the whole purpose rather redundant.
This is exactly how I use my device so it’s a core use case! Not sure what is the exact issue but I’ll ask someone to loop back shortly with more questions!
Can you share your device id via nick@particle.io in the meantime? We need to take a look at the backend.
As a minor update, it sems that manually powering off the WiFi connection is NOT permanent during the session and it is powered back on again by the device after about 30-45 minutes.....
Can you power cycle the device and see if the issue still occurs? Our cellular provider made an infrastructure update last night to fix traffic being incorrectly routed for some devices.
We are actively looking into your device’s issue. Just wanted to ask if you could continue to leave it connected to Wi-Fi, as we’d like to do some live testing on it today.
@MrBrolin for the last few days Cellular has been working with no issues. Wi-Fi has been down though, not sure if you changed something there. Please use the device as normal and let us know if any issues pop up again.
I have also been experiencing issues myself. The console shows the network my device is connected to, but any time I move the device out of wifi range, or simply shut down my AP, it loses its data connection despite having an IP assigned on rnet_data0. I have yet to actually get cellular to work once, and the status LED never changes colour between anything other than blue or green. I havent ever seen purple. particle-tachyon-ril-ctl state returns Connected. Attempts to connect to the internet fail. And the device shows offline in console.
Chiming in with a few observations after taking the Tachyon out for a stroll earlier.
The Tachyon was connected to both WiFi and cellular. When out of the WiFi range, the cellular connectivity was fine and I was able to signal the device.
The cellular connection never dropped whilst out of range. I was out for over 30 minutes.
However, Last vitals in the Console still showed WiFI vitals instead of the cellular info.
Is this a known issue?
Also, NetWorks > Cellular info showed the RRSP the same value as when the device was at home. Unfortunately, I didn’t run a vitals check at the time but will check the next time.
On returning home, Tachyon switched to WIFi fine.
I haven’t seen Networks > Cellular > RRSP change whether at home. or out of WiFi range.
Is this a Console issue?
gnss (particle-tachyon-ril-ctl gnss) works fine.
However, the Console doesn’t display the map from gnss. It’s cellular approximation via the cell towers.
A work in progress from what I understand.
In general, the device is stable. Trying not to tinker with installing tools, etc. Hoping for a 24.04 release soon!
That does seem odd that you didn’t get new vitals after swapping to the cellular connection. We limit how often we allow vitals updates from linux devices, but if the routed access technology changes then you should see new vitals right away.
When you were out on your walk, do you happen to remember what color the LED was on the tachyon? We have seen some issues with our connectivity partner where you can have a connection to the tower, signal levels, etc, but data doesn’t flow. If your device swaps over to breathing green when you take it off wifi, that means you don’t have a connection to the particle cloud.
If you are in that state, please run route -n and send us the result, you can try doing the following series of commands to power cycle your modem and see if it fixes the issue.
particle-tachyon-ril-ctl disconnect particle-tachyon-ril-ctl power off particle-tachyon-ril-ctl power on particle-tachyon-ril-ctl connect
Correct on the GNSS, we have some product work to do around that, then once we have that sorted we’ll get that out for folks.
Yes, the Tachyon led was breathing cyan all the time, when out of WiFI range and when back on home WIFI. I was able to signal the device when out of WiFi range, so it was online and connected to the Particle cloud via cellular.
The cellular connection remained on the same network provider. I’ll run some vitals when I’m remote again with the device.
Currently, on Wifi & cellular. Here’s the output after cellular disconnect & power off/on, and connect
Notice the rsrp: -105 dBm, as reported by the cellular network.
However, the rsrp is not being updated in the Particle Console. I’ve cleared the browser cache and also verified from the Tachyon desktop and an iPad.
In fact, this rsrp: -110 dBm hasn’t changed at all since I’ve had the Tachyon on cellular for almost a week, remote and at home.
Any feedback on the above observations & issues? Clearly the vitals in the Console do not sync up with those retrieved from the particle-tachyon-ril-ctl status vitals command.
Vitals in the Console will only update at the beginning of a new connection or switch between active interfaces (WiFi -> Cellular, Cellular -> WiFi, Etc..).
So later when you run the vitals command manually, what you see there won't sync immediately with the Console. The Console will have been sent vitals data previously from a behind the scenes update during the connection switch.
In Device OS we have an API to push vitals information to the Console more frequently on some regular interval, at the expense of data consumption. We don't have that available yet for Tachyon, but likely something we can implement.
Understood. However, I’ve switched between active interfaces (WiFi -> Cellular, Cellular -> WiFi, etc.) quite a few times since last week, taking the Tachyon out of the WiFi range and then back on several trips.
The Console “Last Vitals” and rsrp haven’t changed at all since I first got the device on the cellular network. It should have changed between the active network interfaces. It appears to be a bug.
Yes, vitals do get updated on the Boron devices, when they reboot and establish a cellular connection and also when switching between cellular networks. Something like that would be nice for the Tachyon.
Regarding minimising data for this activity, can the vitals data not be handled over CoAP DTLS 1.2 CID (as in Boron)?
Even if we used bare minimum data protocols, they will add up over time so we wouldn't likely turn it on by default. It would be something a user can opt-in to and customize the amount of data usage desired. Even if it's over WiFi or Ethernet, it's still data collected by the Cloud as well.
particle-linux (our linux platform support daemon) and by extension Tachyons connect to a new built from scratch new device service, not the same one as our DeviceOS based devices. It’s hooked up to many of the same core infrastructure though to enable our platform features, but talks over HTTP using socketio. The device can continually update it’s status in our UI, though vitals is only aggregated and published to the rest of the platform every 10 minutes or so (there are some exceptions to publish faster when access technology changes). This obviates the need for a manual sync button for vitals.
In your very particular case, there is an issue synching what we call the systemdoc internally that we use to synchronize the vitals information from the device to the cloud. For some reason the cloud is not allowing your device to update that document.
If you don’t mind, I’ll go ahead and turn on verbose logging in the particle-linux daemon? This is so we can see some of our lower level synchronization logs, and work on how we get your device back to healthy and prevent the sync issue in the future.
EDITs: Fixed issues from copying some blocks around in my reply in the post editor
