UDS Services, Security Unlock, and HEX Download
The BUSMUST Diagnostics window includes a service tree that helps users send common UDS requests without typing every byte manually. The service tree is XML-based and can be imported, exported, edited, and shared inside a team.
Service Tree
Section titled “Service Tree”The service tree is organized as service, function, and request. It is designed for parameterized diagnostic operation instead of only raw hexadecimal input. Expand the required service group, choose a sub-service or request template, then edit the visible parameters before sending.
Double-clicking a request node can load or send the prepared request data. The generated payload is shown in the transmit area, so the user can still confirm or fine-tune the bytes before sending the request to the ECU.
Typical services include Diagnostic Session Control, ECU Reset, Read DTC, Read Data By Identifier, Security Access, Communication Control, Routine Control, Request Download, Transfer Data, Request Transfer Exit, Tester Present, and related UDS services.
Common parameter examples include session type, reset type, DID, RID, security level, memory address, transfer length, block sequence counter, and tester-present options. Common DID examples may include boot software ID, application software ID, ECU serial number, VIN, and supplier hardware or software version identifiers. Adjust the DID list to match the ECU project.
This workflow reduces manual byte-entry errors and makes repetitive diagnostic tasks easier to operate. It is especially useful when a support engineer or test engineer needs to run the same service sequence many times while changing only one or two parameters.### Custom Requests and XML Sharing
Use Add, Delete, Save, Save and Send, Import, and Export to maintain the request tree. Exported XML can be reused by other engineers to keep a consistent diagnostic request library.
For project-specific ECUs, create or modify request templates so that common services already contain the correct DID list, routine identifiers, security levels, download parameters, or other project values. After the template is prepared, most users only need to select the request and adjust the few parameters that are different for the current test.### Security Access
The Security Level area automates the common UDS 0x27 seed/key sequence. Select the target security level and click Unlock. BUSMASTER sends the seed request such as 27 01, receives the seed, calls the configured key-generation DLL, then sends the key request such as 27 02 <key>.
The key-generation DLL should implement CANoe-compatible GenerateKeyEx or GenerateKeyExOpt. If the ECU uses a project-specific unlock algorithm, select the corresponding DLL in Diagnostics Settings before unlocking.### HEX Download
The Download HEX File area is used for basic UDS download workflows. After selecting an Intel HEX file, BUSMASTER parses the file and sends RequestDownload, TransferData, and RequestTransferExit requests. In UDS service terms this is the 0x34, 0x36, and 0x37 sequence.
Before downloading, confirm the ECU session, security level, request and response IDs, addressing mode, block size, STmin, timeout, CAN FD options, and power supply. A failed download may leave the ECU in a programming or recovery state.
Authoritative source: BUSMASTER DITA help source Diagnostics_UDS_Services.dita, compiled into BUSMASTER.CHM with the application.