REXDESK: send a new configuration over the air

Change the configuration of a logger that is already out in a vehicle. Export the new configuration from REXDESK, name it config.rxc and place it in the logger's folder on your FTP server or S3 bucket. The logger picks it up on its next check.

How it works

A REXGEN Air or REXGEN Pro with upload enabled checks its own folder on the server at a set interval. Set the interval in Configuration Check Time (sec) for S3, or in Check Config Time (sec) for FTP. When the logger finds a file named config.rxc there, it loads that configuration. It then carries on logging and uploading with it.

Before you start

• A logger already connected to the server, running a configuration with S3 or FTP upload enabled. To set this up, see these guides:
  • REXDESK: upload logs to AWS S3, MinIO or Google Cloud Storage
  • REXDESK: upload logs to an FTP server
• A new configuration with the same upload enabled and the configuration check time set. The logger then keeps uploading and checking for updates after the change.
• The USB cable unplugged from the logger. The logger connects to the server only when the USB cable is unplugged.

Export the configuration

1. Make the new configuration. Build it in REXDESK. Enable S3 or FTP upload in Device Configuration and set the configuration check time.
2. Save the project. Save it under the name you want for this configuration.
3. Export the configuration. Select Config > Export > Export ReXgen Configuration (rxc), choose a folder and select Save.

   

4. Rename the file. The new name must be config.rxc.

Through FTP

Upload config.rxc to the logger's root folder on the FTP server. The logger created this folder and named it after its serial number, for example REX04_A1_B007_SN000xxxx.

Through an S3 bucket

Use the AWS console or any S3 client to upload config.rxc to the logger's root folder in your bucket. This folder is also named after the logger's serial number.

Watch: Update the configuration to the REXGEN Air via Cloud (1:11)

If the logger does not pick it up

• The file is named exactly config.rxc, not config.rxc.rxc or a name with capitals. Windows can hide the extension, so check the full name.
• The file sits in the logger's own root folder, not in a date folder below it or in another logger's folder.
• The configuration the logger runs now has upload enabled and a configuration check time set. Wait at least one check interval.
• The USB cable is unplugged.
• For a hand-written XML configuration, the GUID differs from the one the logger already runs.

Next: REXDESK: send decoded snapshot files to S3.