Bug?: M115 does not generate a response when simulating

EasyTarget

As the title implies, if I run M115 while my board is in 'simulating' mode, the command prompt returns immediately with ok instead of the expected data.

RRF 3.5.2 on Duet2 WiFi

<connected via pyserial-miniterm -q>:
----------------
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-06-11 17:13:43
ok
M37 P"0:/gcodes/bailer.gcode"
Simulating print of file 0:/gcodes/bailer.gcode
ok
M115
ok
M115
ok
File 0:/gcodes/bailer.gcode will print in 0h 57m plus heating time
M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.5.2 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2024-06-11 17:13:43
ok

I cannot see any other modes where this fails to respond, eg it works when processing a job. It just seems to be simulating that kills it. RRF 2.4.6 behaves in the same way.

Is this intentional? it caused some confusion since serialOM uses m115 to detect that it is connected during init().

edit: I checked docs and did a forum and google search and cannot find anything related there

dc42

@EasyTarget when a simulation is being run a few GCode commands are executed, some are simulated, and the rest are ignored. I've just added M115 to the list of commands that are executed. This change will be in the next 3.6.0 alpha build.

EasyTarget

@dc42 Thank You, I'd hoped it was a trivial fix of this sort.
I have also added a 'do not check firmware' init() option to serialOM since it's a bit redundant in some situations.