Parsing M105 results
Send: M105
Recv: ok T:160.0 /160.0 B:60.0 /60.0 T0:160.0 /160.0 @:20 B@:23 P:31.9 A:26.1
Using the above example, I'm trying to figure out what everything in that line means. The "B:nnn/nnn" is obviously the bed process value and setpoint, and "T0:nnn/nnn" is tool zero process value and setpoint. On my single extruder printer the "T:nnn/nnn" and the "T0:nnn/nnn" are the same value. On multi-tool printers would the "T:nnn/nnn" be the currently active tool, or is always tool zero? The "P:nnn" is presumably the PINDA temperature, and "A:nnn" I'm guessing is the "ambient" temperature (i.e. temperature sensor on the Rambo, which is sensing the temperature inside the cable rats-nest that is the electronics enclosure, not the ambient room temperature).
For the life of me I can't figure out what the "@:nn" and the "B@:nn" values are indicating. Anyone out there know? I've looked online and found https://prusa3d.github.io/Prusa-Firmware-Doc/group__GCodes.html linked from Prusa's GitHub Firmware Repository's wiki and this document doesn't explain the M105 results. I'm not sure where to look in the source code, nor not confident that I would understand the source if I could find the right function/class.
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
RE: Parsing M105 results
It's actually been updated to be better documented internally to be compliant with the RepRap documentation
https://reprap.org/wiki/G-code#M105:_Get_Extruder_Temperature
From the source:
RE: Parsing M105 results
Thanx for the info. I hadn't checked the reprap docs yet. (General grumble that RepRap's docs are more complete than Prusa's for their own fork...)
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
RE: Parsing M105 results
@vintagepc
When I go to the homepage of Marlin ( https://marlinfw.org/docs/gcode/M105.html) - why is there nothing to find about the parameters like you described them? I thought (regarding firmware I am more a newbie) Marlin is the core and so there should be documented everything. But your link is going to reprap. Is there a single truth or is it more the best of all worlds?
I am interested, beause at the moment I try to build my first 3D-printer and one major step is to get firmware running on my mainboard.
Best regards, Clemens
Mini, i3 MK2.5S, i3 MK4, CClone (Eigenbau)
RE: Parsing M105 results
When a printer manufacturer implements Marlin (or any other firmware) their particular version can use a subset of all commands or even expand upon them. Marlin is the basis, not the limitation. Not all devices require all the commands so they don't get included. The same goes for other routines which is why some of the manufacturers printers dont/didnt include basic safety features like thermal runaway protection.
If you are compiling or writing your own firmware you get to choose what is and isn't included. Of course sometimes the hardware limits what you can fit due to memory constraints so you have to make hard choices.
Its the same with the expansion of the base code, if your device needs something not covered you can add to Marlin base to include it. I'm not sure on the process of feeding your additions in back upstream but that can certainly happen if your additions work out to be beneficial to the general project.