Flasher Hub - FTP server
The FTP server on the Flasher Hub provides easy access to the files on the connected Flasher Compact modules.
FTP server connection
The FTP server supports a maximum of 2 simultaneous connections and works with all common FTP clients.
The root folder contains a folder for each module, as well as an "All Modules" and a "Logs" folder.
The FTP server allows you to upload or download the target configuration and data files.
Files and folders uploaded to the "All Modules" folder automatically get copied to all connected Flasher Compacts. Note that the "All Modules" folder itself does not retain any files or folders and will always appear empty.
Please also note that you may have to perform a "Refresh" operation on the Module folders before the FTP client will display the 'true' content of these folders. This is because many FTP clients tend to cache the folder contents and don't necessarily refresh the display automatically, even if the folder contents has changed.
The Flasher Compacts create log files for executed operations. These files can be found in the module folders and downloaded from there.
The IP setup is described here: Setting up Flasher Hub's IP interface.
Timestamps
When uploading a file via FTP, the timestamp is set based on Flasher Hub's current local time.
Furthermore, when listing files using the legacy LIST command, Flasher Hub's FTP server sends these timestamps to the client exactly as they were saved on the filesystem (See File management for reference).
Because the original FTP specification for the LIST command does not define a standard timezone, FTP clients (e.g., FileZilla) often assume these timestamps are in UTC and automatically apply a local time zone offset.
This can result in the FTP client displaying incorrect timestamps compared to the timestamps shown in the Flasher Hub web interface.
The legacy LIST command lacks a standardized output format [1], allowing the server to transmit the filesystem's local timestamps. In contrast, the modern MLST and MLSD commands are machine-readable and strictly require timestamps in UTC [2]. Because the Flasher Hub uses a FAT filesystem which stores timestamps exclusively in local time, reliably converting these to UTC is impossible without timezone context. To maintain strict RFC compliance, the server does not send timestamps for MLST and MLSD responses.
Many FTP clients offer a setting to manually correct this offset. In case of FileZilla, this can be achieved as follows:
- Navigate to File → Site Manager
- Select connection
- Open Advanced tab
- Adjust the server time zone offset
Example:
If Flasher Hub is configured to use UTC+02:00 (German summer time), the client would need to offset this by -2 hours, as shown in the screenshot.
Access data
Anonymous access to the FTP server is limited to read-only access to the file system.
For write access, special login credentials have to be used:
| Setting | Value |
|---|---|
| Host name | Flasher Hub: ftp://flasherhub-<serial_number> Flasher ATE2: ftp://flasherate2-<serial_number> |
| Username | admin |
| Password | 1234 |
| Port | 21 (Default FTP port) |
The access data for read/write access cannot be modified and is intended to be used only as a convenience feature to avoid unintended modification of the Flasher's file system. It is not meant as a security feature.
References
- ↑ RFC959: FILE TRANSFER PROTOCOL (FTP). "... this information may be hard to use automatically in a program, but may be quite useful to a human user."
- ↑ RFC3659: Extensions to FTP. "The MLST and MLSD commands are intended to standardize the file and directory information returned by the server-FTP process. These commands differ from the LIST command in that the format of the replies is strictly defined although extensible."