WiFi troubleshooting tips

The below steps can be useful in troubleshooting WiFi connectivity issues.


Verify a simple connection to our S3 test server

To start with the basics, ensure that you can connect in a ‘simple setup’:

  1. Ensure that you have physical access to the CANedge2 during testing
  2. Create a backup of your original Configuration File on the device SD card
  3. Enable your smartphone’s shared WiFi and test if your PC can get online through it
  4. Modify your Configuration File via the config editor as follows:
  • Use your smartphone’s shared WiFi hotspot details as the only WiFi access point[1]
  • Set both the ‘Firmware, config and certificate’ and ‘Heartbeat’ sync rates to 10 seconds[2]
  • Add the below S3 test server details to your Configuration File
"server": {
    "endpoint": "http://s3.us-east-1.amazonaws.com",
    "port": 80,
    "bucket": "canedge-test-bucket",
    "region": "us-east-1",
    "request_style": 0,
    "accesskey": "AKIA32WGRU62KABRUPMN",
    "keyformat": 0,
    "secretkey": "W6aFYFLdT74S7y4a6wcfgiQ5BYJ1KsJaZsx3cFur",
    "signed_payload": 0
}
  1. Log into the S3 test server via CANcloud and check if your device uploads the device.json

If the device does not connect, please try with another WiFi access point. If it is still not connecting, please send us an e-mail with your Configuration File.

If the device connects, proceed to the next step below.


Test your original WiFi access point access

Below we assume that you have verified that your device connects to our S3 test server using your smartphone as WiFi access point. Next, you’ll test if the original WiFi access point works.

  1. Use CANcloud to login to the AWS S3 test server
  2. Delete your device Configuration File from the S3 test server[3]
  3. Configure your device via the SD to use your original WiFi access point only
  4. Wait ~30s to see if the device loads the new Configuration File, power cycles and reconnects

If the device does not update the device.json file after the change, check the following:

  • Double check if the SSID/password are correct
  • Check if the blue LED lights up (it should light up with each sync attempt)
  • If it is a corporate WiFi access point, check if e.g. MAC address white listing is required

If the device connects via your original WiFi access point, proceed to the next step below.


Test your own S3 server access

  1. Log into your own S3 server via CANcloud, while connected to your original WiFi access point
  2. Delete the device Configuration File on your own S3 server[3]
  3. On the device SD, update your Configuration File to use your own S3 server details again
  4. Check if the device is now able to connect to your own server (i.e. is the device.json updated)
  5. If the device is still unable to connect to your server, check the below:
    • Verify that all your server details are correct (see the S3 server guides for syntax)
    • Verify that you do not use https:// in your endpoint (if you have enabled TLS, disable it)[4]

If you’re still unable to get started after trying the above steps, contact us and describe your results from the above tests. In your mail, please include your Configuration File.


[1]A smartphone shared hotspot is typically a simple WiFi access point in the sense that no firewalls, whitelisting etc. is involved - hence it’s useful for troubleshooting purposes. If you’re using an iPhone as hotspot, you may need to go to the ‘Personal Hotspot’ menu before the hotspot becomes visible
[2]The 10 second frequency is mainly for testing purposes. For your final setup we recommend setting the sync rates back to their original values
[3](1, 2) The device will automatically upload the Configuration File from the SD card when it connects to an S3 server. If a change is made after this to the Configuration File directly on the SD card, the device will perform an over-the-air update and download the Configuration File from the S3 server. To avoid confusion, it is therefore recommended to delete the S3 Configuration File during troubleshooting
[4]HTTPS transfer is an advanced feature. For troubleshooting purposes we recommend to first get the simpler HTTP transfer to work. If you are using a MinIO S3 server and you have enabled TLS, you can temporarily remove the TLS certificates and restart the server