Feature Request: Show the Mcu frequency, memory(ram), and flash memory(rom) in the build information

[XYartlab]

Recently I was writing about a sender and wanted to put a separate panel on the host to display the control board information. For example, the number of axes, the name of the axis, the MCU, the MCU frequency (I have modified the firmware, now it is displayed as DRIVER:RP2040 @250MHz like this), MCU memory (there is already display with free RAM), MCU flash, firmware version, SDK version, number of IOs. A panel displays firmware information such as type (grblHAL/fluidnc/grbl), firmware URL, firmware compilation options, and features. I looked at the HAL website and it seems that there is currently no interface for RAM and Flash. Perhaps a more refined build information could be considered.

[XYartlab]

By the way, after many days of short running, the RP2040 @250MHz looks completely fine, no heat, no abnormal bugs, and of course I haven't tested it enough.

[terjeio]

Some of the information you ask for is already available in the $I output, an example:

[VER:1.1f.20260314:] -> firmvare version == build date
[OPT:VNMSL2,100,1024,4,0]
[AXS:4:XYZA] -> axis configuration
[NEWOPT:ENUMS,RT+,ES,REBOOT,TC,SED,ETH,FTP,YM,SD]
[FIRMWARE:grblHAL]
[SIGNALS:EFP] -> available inputs, same letters as in the |P: status report element.
[NVS STORAGE:*EEPROM 16K]
[FREE MEMORY:139K]
[DRIVER:STM32F412]
[DRIVER VERSION:260311]
[BOARD:SuperLongBoard Ext]
[AUX IO:7,4,1,0] -> available auxiliary ports, digital in and out, analog in and out, use $PINS (and/or $PINSTATE) output for details about these and other pins.
[PLUGIN:Bootloader Entry v0.03]
[PLUGIN:SLB Probing v0.06]
[WIZCHIP:W5500]
[MAC:02:08:dc:11:49:90]
[IP:]
[PLUGIN:FS stream v1.06]
[PLUGIN:FS macro plugin v0.22]
[PLUGIN:MODBUS v0.22]
[PLUGIN:H-100 VFD v0.11]
[PLUGIN:Macros v0.19]
[PLUGIN:RGB LED strips (M150) v0.07]
[PLUGIN:SIENCI Indicator Light v2.0]
[PLUGIN:Events plugin v0.13]
[PLUGIN:SDCARD v1.26]
[SPINDLE:H-100]

I do not understand why RAM and flash size is needed, just for fun facts? What could be more relevant is free space in filing systems.
SDK version is already available in $I output for the ESP32 and RP2040 drivers - I do not know if this information is readily available for the other drivers. I will add MCU frequency to the DRIVER elemet since it is already available for most drivers.

Here is the about dialog in ioSender:

[XYartlab]

My envision is to read and write FLASH like current SD card, and then display the Free FLASH capacity at $I. FLASH can put some editable macros. Simply displaying the RAM+ROM of the MCU is indeed a bit redundant.

[terjeio]

My envision is to read and write FLASH like current SD card, and then display the Free FLASH capacity at $I.

For that part of (or remaining) flash has to be assigned to a filing system, grblHAL support littlefs for non-SD filing systems. In the next build I will add filing system type, mount directory, size and remaining space to the $I report for each filing system, e.g:
[FS:FatFs@/ size 14.72 GB, free 14.69 GB]

littlefs is not available for the driver I am working on now, it will show up for those who have it available.

[XYartlab]

Is it possible to consider displaying an additional MCU UID in the $I message? In this way, the sender can count the running information of each board individually. For example, [MCU UID:0042002F12345678AABBCCDD], I don't have grblHAl boards for other MCUs, so I can only implement the uid display of rp2040 by myself at most. Consider this.

[terjeio]

IMO use $I=id to set an unique ID or machine name, it is appended to the VER element in the $I report.

[XYartlab]

Request to add line number display in the SDcard plugin's status report. In fs_stream.c, modifying the commented section can make it display. After simple testing, it works.
However, the line number here is the line number that has been read, not the line number currently being executed, right? Is there a clever way to display the currently executing line number?

static void onRealtimeReport (stream_write_ptr stream_write, report_tracking_flags_t report)
{
if(!report.all) {
if(hal.stream.read == read_redirected) {

        char *pct_done = ftoa((float)file.pos / (float)file.size * 100.0f, 1);

        if(state_get() != STATE_IDLE && !strncmp(pct_done, "100.0", 5))
            strcpy(pct_done, "99.9");

        stream_write("|SD:");
        stream_write(pct_done);
        stream_write(",");
        stream_write(file.name);
        //display current line.
        stream_write(",Ln:");
        stream_write(uitoa(file.line));
    } else if(hal.stream.read == await_cycle_start)
        stream_write("|SD:Pending");
}

if(on_realtime_report)
    on_realtime_report(stream_write, report);

}

[XYartlab]

Perhaps consider using a $$ command（or $10） to toggle the display of sdcard line numbers？

[terjeio]

Is there a clever way to display the currently executing line number?

Yes, add line numbers to the file (N-word) if not already present and enable line number output (a $10 option) in the real time report.

FYI the line counter maintained by the SD card code cannot be used reliably, especially when the code contains subroutines, loops etc. It may be possible to fix this but I believe it is not trivial.

[XYartlab]

It can be considered to include the total line count in the returned information after executing $C on SD card files.
For example:
[MSG:Total Line:66666. ]
ok
This way, the sender can display complete information about the current line, sent lines, total number of lines, progress percentage, and runtime...

[XYartlab]

Is there a clever way to display the currently executing line number?

Yes, add line numbers to the file (N-word) if not already present and enable line number output (a $10 option) in the real time report.

FYI the line counter maintained by the SD card code cannot be used reliably, especially when the code contains subroutines, loops etc. It may be possible to fix this but I believe it is not trivial.

When there are line numbers in the file, I found that it is indeed possible to display the current execution line number. Combined with the cmd_status plugin, it can also display the complete information of the currently executing line, such as G1 X50 Y20 F600.
It can be considered to include everything, with the display controlled by a $10 or other command switch.