Choosing the right UFF format in Microlog Analyzer dBX

Summary

Measurements collected using Microlog Analyzer dBX module may be exported to UFF. If saved in the same place as regular Analyzer files, these files can be collected by TCT.dBX and uploaded to @ptitude Analyst as non-route files.

Be aware that there are two UFF formats provided by Microlog Analyzer export:

1. Regular type 58 UFF files, which are 100% ASCII.
2. Binary type 58b UFF files, which have an ASCII header, but the data block is encoded in binary format.

TCT.dBX upload does not support the second type, the binary UFF, so the measurements will not appear in Analyst non-route after upload.

For software versions up to 1.2, the presence of any binary UFF files in the Analyzer data directory will cause the entire non-route upload to fail.

In software version 1.3, due for release in summer 2025, the presence of any binary UFF files in the Microlog Analyzer data directory will not halt the non-route upload. The binary UFF files will be skipped, there will be an advisory for each one encountered, and the remaining standard UFF files will be uploaded as normal.

Note: Analysis and Reporting Module (ARM) is not capable of reading binary UFF files.

Solution

Ensure that when exporting Analyzer measurements, you select standard UFF instead of binary UFF.

 

Contacting SKF Technical Support Group

For further assistance please open a support case using the Technical Support group's self-help portal at www.skf.com/cm/tsg. Once your support case is submitted, a technician will contact you to begin working on your issue. For urgent issues we are available at these times by phone:

• Monday through Friday, 5:00 a.m. to 4 p.m. Pacific Time -
  Phone: [phone] within the US or [phone] outside the US.
• Monday through Friday, 8:00 a.m. to 4:00 p.m. Central European Time -
  Phone: [phone].
• Monday through Friday, 7:30 a.m. to 4:30 p.m. India Standard Time -
  Phone: [phone].