Skip to content

Invoke BALTECH Uploader from a custom application

With BALTECH Uploader, you can deploy configurations or firmware updates. To automate deployment, you can invoke Uploader from your own application or script.

This feature requires Uploader v4.26.02 or above.

Uploader EXE

Uploader is available for download as part of BALTECH ToolSuite. Once you've installed ToolSuite, you can find the Uploader EXE file here:

C:\Program Files (x86)\Baltech\Tool Suite\bf2uploader.exe

Command line arguments

You can invoke Uploader without any arguments; then Uploader will simply start and wait for user interaction. With the following arguments, you can further automate the deployment process.

Argument Supported values Description Note
Path to firmware or config file
  • File path, e.g.C:\{path}\1100_1.30.00.bf2
  • defaultFirmware
 The firmware or config file will be preselected when Uploader starts. If you want to deploy the firmware file that is included in Uploader (see C:\Program Files (x86)\Baltech\Tool Suite\firmware), use defaultFirmware. This must be the first argument.
Mode

optionally with reader serial number
  • wired
  • wireless
  • configCard
 Uploader selects the connected reader and starts the specified upload mode, i.e. Wired Upload, Wireless Upload (using the connected reader as a transfer reader), or ConfigCard creation.

Specify the reader serial number if several readers are connected. To do so, use {mode}={serialnumber}, e.g. wired=12345678.

In Uploader versions below v5.00.03, the serial number must always be specified.

No user interaction

optional

 noInteractions This argument lets you perform Wired Upload without any user interaction: Uploader will start automatically, start Wired Upload, and respond with an exit code instead of a dialog (see table below). As this argument only works with Wired Upload, the argument wired must be passed as well (see argument Mode above).
Show error messages

optional

 onlyErrorMessages This argument can be used as an alternative to noInteractions. Uploader will behave as with noInteractions; however, if an error occurs (exit code = 1, see table below), it will display the specific error message, so you can more easily respond to the error.

Requires Uploader v5.00.07 or above.

As this argument only works with Wired Upload, the argument wired must be passed as well (see argument Mode above).

Success and error response

Upon successful completion or errors, Uploader will respond as follows:

Status With argument noInteractions With argument onlyErrorMessages With neither noInteractions nor onlyErrorMessages
Upload successful Exit code 0 Exit code 0 Success message with options to perform another Wired Upload or return to the Uploader start screen.
Success message for Wireless Upload in BALTECH Uploader
An error occurred during the upload Exit code 1

We recommend you repeat the upload manually to see the error message.

 Specific error message Specific error message
The argument {mode} or {mode}={serialnumber} has been passed, but Uploader doesn't detect a reader. Exit code 2 Exit code 2 Dialog to select reader manually
Dialog Select a Reader in BALTECH Uploader

The argument {mode} has been passed, but Uploader has detected more than 1 reader.

or

The argument {mode}={serialnumber} has been passed, but the specified serial number doesn't match any of the connected readers.

Exit code 3 Exit code 3 Dialog to select reader manually
Dialog Select a Reader in BALTECH Uploader

Example

The following example causes BALTECH Uploader to deploy the included firmware file via Wired Upload to the connected reader and terminate itself upon completion, except if an error occurs (exit code =1).

"C:\Program Files (x86)\Baltech\Tool Suite\bf2uploader.exe" defaultFirmware wired onlyErrorMessages
Title