App log entries

The app log is opened via the context menu, which is displayed by clicking on the three-dot symbol in the list of sites.

CodeParameterDescription
Shutdown handling
MT.BackupSupplySwitched to buffer batterySupply switched to the internal rechargeable buffer battery.
Supply voltage available againSupply switched back to the supply voltage input (VIN).
Outage timeout expiredTime expired for which a short-term supply voltage failure is ignored.
MT.Shutdown Command to shut down the system issued by the device logic
Software update
MT.ModFwUpdatedIO Controller: <previous version> to <current version>Firmware of the IO controller of the data logger has been updated.
IO Controller: Downgrade suppressed Downgrade to a lower Firmware version has been suppressed for the IO controller of the data logger.
IO Controller: Firmware already up-to-date Firmware of the IO controller of the data logger has not been updated. The latest version is already installed.
IO Controller: Update FAILED Firmware update of the IO controller of the data logger failed.
IO Extension MT-<#>: Updated Firmware of the IO controller of the extension with serial number MT-<#> has been updated.
IO Extension MT-<#>: Downgrade suppressed Downgrade to a lower Firmware version has been suppressed for the IO controller of the extension with serial number MT-<#>.
IO Extension MT-<#>: Firmware already up-to-date Firmware of the IO controller of the extension with serial number MT-<#> has not been updated. The latest version is already installed.
IO Extension MT-<#>: Update FAILED Firmware update of the IO controller of the extension with serial number MT-<#> failed.
Modbus interface
MBMException
Ch(<channel>): 
   Exc:<exception>, 
   FC:<code>, 
   Slave:<address>, 
   Reg:<register>

Modbus server (formerly slave) reported an exception.

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

<exception> Exception code:

01:Illegal function
02:Illegal data address
03:Illegal data value
04:Server device failure
05:Acknowledge
06:Server device busy
08:Memory parity error
10:Gateway path unavailabe
11:Gateway target device failed to respond

<code>Modbus function code
<address>Address of the Modbus server
<register>Address of the Modbus register to be accessed

OK(<channel>)

A valid response was received again from the Modbus server (formerly slave) after an exception was last reported.

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

MBMErrorCRC
Ch(<channel>):  
   FC:<code>, 
   Slave:<address>, 
   Reg:<register>

The calculated CRC does not match the CRC received from the Modbus server (formerly slave).

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

<code>Modbus function code
<address>Address of the Modbus server
<register>Address of the Modbus register to be accessed

OK(<channel>)

A valid response was received again from the Modbus server (formerly slave) after the calculated and received CRC did not match.

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

MBMErrorTimeout
Ch(<channel>):  
   FC:<code>, 
   Slave:<address>, 
   Reg:<register>

The Modbus server (formerly slave) did not respond within the timeout. 1)

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

<code>Modbus function code
<address>Address of the Modbus server
<register>Address of the Modbus register to be accessed

OK(<channel>)

A valid response was received again from the Modbus server (formerly slave) after a timeout occurred last time.

<channel>Modbus measurement channel or Modbus output channel:

0=^First Modbus measurement channel
20 =^First Modbus output channel

1) If a timeout is detected, the Modbus server is marked faulty. Further access to the Modbus server is prevented during the current measurement cycle. All required accesses for the Modbus measurement channels or Modbus output channels are only performed again in the next measurement cycle (i.e. after the measurement interval has expired). Therefore, if a timeout is detected, this app log entry is only created for the first Modbus measurement channel or Modbus output channel that is linked to the corresponding Modbus server.