Skip to content

BUSMASTER-NG 3.6.0 "Overdrive"

Choose a tag to compare

@github-actions github-actions released this 14 Nov 18:52
· 7 commits to master since this release

Feature release: a Frequency (Hz) column in the Message and Transmit windows, a message list that can be sorted while
the bus is connected, messages that stop arriving shown in grey, repetition times that follow the clock, and updates
installed from inside BUSMASTER-NG.

Note on updating

  • Window positions and the last configuration are stored per version, so after updating from 3.5.0 load your
    configuration once (File → Load).

Message Window

  • With the Simulation driver the Time column could show the wrong time in System Time (the time since the PC was
    started instead of the time of day) after the first connect (#13). The reference time is now asked to the simulation
    engine when the connection is made, and a driver that does not provide it no longer leaves random values (not
    tested yet)
    .
  • New Frequency (Hz) column (CAN): how often the messages with the same ID, channel and direction arrive, from the
    time between them, averaged over the last messages ("-" for the first one). In append mode each row keeps the value
    it had when it arrived. After the Data Byte(s) column, so a saved configuration keeps its columns; drag it where
    you like.
  • Simulation driver: the time stamp of a message is taken when it is sent and not when the simulation engine hands it
    to the clients. Messages sent every millisecond used to show intervals such as 1 ms and then 20 ms, because the
    engine delivers them one at a time and a pause there bunched them together (the number sent per second was right);
    Relative Time and Frequency (Hz) are now regular. Interfaces with real hardware are not affected, they time
    stamp in the device.
  • CAN: the list can be sorted while the bus is connected (it only worked when disconnected), and in the overwrite mode
    it stays sorted: click the header of ID (or Message, Channel, Time, Tx/Rx, Msg Type, DLC) once for
    ascending and again for descending, and an ID that appears later goes to its place. Rows that are equal in the
    column keep a fixed order (by ID, channel, direction). The sorting stays when the bus is connected again. In the
    append mode, which is a trace in order of arrival, it still sorts only the messages already there, when disconnected.
  • CAN, LIN: the Data Byte(s) column opens narrower, enough for 8 bytes (its width came from a title padded with spaces;
    a width saved in a configuration is kept).
  • CAN, overwrite mode: a message that stops arriving turns grey and its Frequency (Hz) shows "-", when nothing came
    for three times its period (at least 100 ms); it goes back to normal when it comes again. A message seen only once
    is never greyed, and on disconnecting the rows stay as they were.
  • CAN: the Frequency (Hz) column can be sorted too (in the overwrite mode the list is sorted when the header is
    clicked and when an ID appears, the frequencies that change afterwards do not move the rows).
  • Connecting with messages already set to repeat in the Transmit window sometimes failed with "Failed to start the
    hardware" (seen with Simulation): the Transmit window started sending before the hardware was started, kept the
    driver busy and the start gave up. The Transmit window now starts once the hardware has started, with every driver
    (with a real interface the first messages used to be sent to a controller not started yet), and the Simulation
    driver also waits its turn instead of giving up.
  • CAN, sorted list (overwrite mode): the error frames kept their row after a sort (their row could take the place of a
    message, or show another message's data); the Frequency (Hz) sort is made with the frequencies held still (they
    changed during the sort and could leave it unsorted); Clear while connected no longer leaves rows pointing at the
    wrong message (the error frames are not tested yet, they need a real interface).

Transmit window

  • Messages sent with a repetition time (CAN and LIN) go out at the time you set: a message every 10 ms went out every
    20 ms or less often, because the repetition was counted in wake-ups of the transmit thread (a wait of 1 ms lasts one
    or two ticks of the system timer) and not in real time. It now follows the clock.
  • The shortest repetition time depends on Windows: 1 ms (1000 Hz) on Windows 10 1803 or later and Windows 11, which
    have a high resolution timer, 2 ms (500 Hz) on Windows 7 and earlier Windows 10, where a wait of 1 ms lasts 1 to
    2 ms. A shorter value is raised to the minimum, and the repetition time and the frequency shown in the list tell it.
    On the fast timer a message that is late goes out again for the periods it missed (up to three in a row), so the
    average rate holds.
  • New Frequency (Hz) column next to Repetition (ms) (CAN and LIN): type the repetition time and the frequency is
    calculated, type the frequency (a comma is accepted as decimal separator) and the repetition time is calculated, in
    the range 1 ms to 60 s.

Updates

  • Help → Check for Updates installs a newer version from inside BUSMASTER-NG: Install now downloads the
    installer (with a progress window and Cancel), checks it against the SHA-256 that GitHub gives for it, closes
    BUSMASTER-NG (with the usual question about saving the configuration) and installs the update without the wizard;
    BUSMASTER-NG starts again when it is done. Windows asks for administrator permission when BUSMASTER-NG is
    installed for all users, not when it is installed only for you. Portable copies (zip) still get the release page.
  • Help → Check at Startup (off unless you turn it on): checks for a newer version every time BUSMASTER-NG starts,
    in the background, and speaks up only when there is one.