Getting diagnostics from charger

Sometimes chargers own diagnostics logs are required to help troubleshooting malfunctions. From eMabler UI you can request the charger to send its diagnostics logs to an FTP server.

Prerequisites

The charger to be diagnosed needs to be online
An FTP server URL to upload the diagnostics package into
Available also from eMabler support
An FTP client installed on your machine

Getting diagnostics

1. Navigate to charger in question and click "Details"

2. From the top right corner click "Actions"

3. Click "Send diagnostics"

4. Insert the FTP URL in the field that appears. Any credentials needed for login should be included in the URL, eg. ftp://username:password@example.com

5. After clicking send, the charger should send an update message confirming the upload as complete which can be read from the "Last message".

// Example message:
[
  2,
  "35123123-asd23-243x-ba12-0141fc",
  "DiagnosticsStatusNotification",
  { "status": "Uploaded" }
]

6. Now you can download the diagnostics package from the server with your FTP client.

Downloading diagnostics packages with a terminal FTP client

Open terminal
If not already installed, install the FTP client package to your computer. For new OSX versions, you will need to install it via Homebrew
Open FTP with the FTP server address

ftp user@example.com

Input the password when prompted
Change to binary transfer mode

ftp> binary

Get file listing from the server

ftp> ls

Look for the file you want, they are typically named in a format which indicates the charger ID and date.
Download the file

ftp> get <filename>

Exit the FTP prompt

ftp> quit

You should now have a ZIP file downloaded to your machine. You should be able to open it with common zip handling tools, if not, please see the section about fixing broken ZIP packages.

Fixing broken zip packages

When some chargers generate the zip package of diagnostics information, they omit a mandatory part of the zip package which describes the contents of the file. This may result various errors extracting files from the archive, for example:

End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.

On OSX terminal this error can be fixed by rebuilding the zip package with the zip utility like so:

zip -FF <broken.zip> --out <fixed.zip>

Replacing <broken.zip> with a path to the original file, and <fixed.zip> with a path to a new file.

This should result in a new, working file being created.

Prerequisites​