After moving the M172 controller firmware update to a FAT32 USB drive, the controller can detect the firmware file at power-up and start the update automatically. Application downloads may be scripted, but BIOS or firmware flashing cannot be executed through the EWDevice or ESME command line described here.
Update-path decision
-
Classify the payload. Determine whether the file is a control application or controller firmware. If the task changes the user application, follow the scripted online-download path documented by
HowToESME_DownloadOnLineCommand. Confirm that the application download completes before moving to functional testing. - Separate firmware from application logic. If the requested operation flashes the BIOS or updates controller firmware, stop evaluating the application-download command. That command does not provide a firmware-flashing mechanism.
- Check the required automation boundary. If an operator can reach the controller and cycle its power, use the USB update path. If the machine enclosure or test cage cannot be accessed while live, schedule an access window before attempting the update.
- Confirm the controller identity. Read the controller model and installed firmware version from the device information available in the engineering software or controller interface. Match the firmware package to that controller before copying it to removable media.
Do not move on until the payload type and controller identity are known. Application download and firmware flashing modify different parts of the controller and use different update mechanisms.
Command-line capability boundary
| Operation | Available path | Decision |
|---|---|---|
| M172 application download | Scripted online command covered by HowToESME_DownloadOnLineCommand
|
Use the application-download workflow and verify the loaded application. |
| M172 BIOS or firmware update | USB drive or the interactive engineering-tool path | Do not design the process around a CLI firmware command. |
| Unattended firmware flashing | No command-line mechanism is available in the described toolset | Introduce a controlled manual USB step or change the production access plan. |
The command-line application workflow transfers the compiled control application through services exposed for online download. A firmware update replaces lower-level controller software and enters a separate boot-time update path. Access to application-download commands therefore does not imply access to the bootloader or BIOS flashing function.
A command-line BIOS update was tracked as a possible improvement, but no implementation schedule was stated. Treat it as unavailable when defining commissioning time, operator access, safety-test sequencing, or production automation. An improvement request is not a callable interface.
Physical-access and process checks
- Check enclosure access. Record whether personnel can reach the TM172 USB port without violating the machine's access controls. If the controller sits inside a locked test cage, the USB method requires the test operation to stop and the cage to be released under the site's access procedure.
- Check the power-cycle opportunity. The controller detects the firmware file when it powers on. Confirm that the process permits a controlled shutdown and restart; inserting media alone is not the complete update trigger described for this method.
- Check test-state retention. Determine which automated application-flashing, safety-test, and functional-test stages must be restarted after controller power is removed. Place the firmware operation before tests that depend on the final firmware state whenever the production sequence allows it.
- Check recovery access. Keep the controller accessible until the update and restart have been verified. Do not relock the cage or resume unattended testing immediately after power-up.
The access requirement is the main integration constraint. A production cell that already automates application loading still needs a physical intervention for firmware because the two update paths are independent.
USB media and firmware preparation
| Item | Required setting | Confirmation before use |
|---|---|---|
| USB drive filesystem | FAT32 |
The host computer reports the drive as FAT32. |
| Firmware-file location | Root folder of the USB drive | The firmware file is visible at the top level, not inside a subfolder. |
| Firmware selection | Package intended for the identified controller | The package documentation or official support channel matches it to the controller model. |
| Controller state | Ready for a controlled power-on with the drive inserted | The machine process is stopped and the permitted access window is active. |
Before anything else, confirm the target model and current firmware version. The evidence does not supply a firmware filename, extension, or package-version rule, so obtain those details from the package documentation or Schneider Electric's official support channel. Do not rename a package or substitute a file based only on a similar controller name.
Keep the selected firmware file in the USB drive's root. Extra files can complicate troubleshooting because the controller must identify the intended update package during startup. The decisive preparation checks are the FAT32 filesystem, root-level placement, and a package matched to the target controller.
Firmware update procedure
- Stop the machine process and place the equipment in the state required for controlled access. Confirm that removing controller power will not leave connected equipment in an unmanaged state.
- Read and record the installed firmware version. Also record the controller model so the post-update comparison refers to the correct device.
- Format or verify the USB drive as
FAT32. Confirm the reported filesystem before copying the update package. - Copy the correct firmware file to the root folder of the USB drive. Confirm that it is not nested in a directory and that the copy operation has completed.
- With the process stopped, insert the prepared USB drive into the TM172 controller's USB port.
- Power on the controller. The controller should detect the firmware file and start the update automatically.
- Observe the controller throughout the update. Do not interrupt power or remove the USB drive while update activity is indicated. Use the controller interface or engineering software to distinguish an active update from a normal startup.
- After the update completes and the controller returns to its operating state, reconnect with the engineering software or use the available device-information interface. Confirm that the displayed firmware version equals the intended package version.
The USB route was described as approximately ten times faster than updating through ESME HVAC. Treat that figure as a workflow observation rather than a guaranteed duration; package size, USB media, controller state, and tool communication can change elapsed time.
Verification and recurring pitfalls
| Observed result | Likely branch | Next check |
|---|---|---|
| No automatic update at power-on | The controller did not recognize the media or file | Recheck FAT32, root-folder placement, file-copy completion, and controller/package match. |
| Application downloads but firmware does not | The application CLI is working, but it is the wrong interface for firmware | Return to the USB update path; do not retry the application command as a BIOS flasher. |
| Firmware version remains unchanged | The package was not applied or the wrong version was selected | Review startup indications and revalidate the package against the exact controller model. |
| Controller updates but automated testing cannot resume | The firmware operation disrupted the cell sequence | Restore the required application and test state, then repeat the commissioning checks from their defined entry point. |
Do not treat a normal-looking power-up as proof of success. The acceptance reading is the firmware version reported after restart, followed by the controller's normal application state and the required machine functional checks.
Frequently asked questions
What happens if I use the M172 application-download CLI for firmware?
The command described by HowToESME_DownloadOnLineCommand handles application downloading, not BIOS or firmware flashing. Move the firmware task to the FAT32 USB workflow.
What happens if the firmware file is inside a USB folder?
The specified procedure requires the firmware file in the USB drive's root folder. Move it to the top level, confirm the drive is FAT32, and power on the controller with the drive inserted.
What happens if the TM172 does not start the update automatically?
Check the USB filesystem, root-level file placement, completed file copy, and firmware-package match. Then repeat the controlled power-on while observing the controller's startup indications.
What happens if the controller restarts normally after flashing?
A successful restart alone does not prove that the new firmware was installed. Read the controller's firmware version after restart and confirm that it matches the intended package before resuming functional testing.