gwhite wrote:I'm certainly no expert, but I believe (at least with Marlin systems) that the software should be able to interrogate the settings that are set in the firmware.
Yes, M503 is used to query the printer, but, it does not work on every firmware, it is formatted differently on each printer etc... and what is most important you don't often have your printer attached to the machine running s3d... normally you'll run them stand alone or attached to some rpi or similar mini computer accessible over network controled by some octoprint or similar system, even if you have only one printer that makes sense so not too useful to query printer. Some defaults should be configurable (s3d already have some default configuration per supported printer but s3d is completely ignoring accel/jerk/jd values and expect you to set them either on printer itself or in the start g-code manually (not ideal as it could make some very good things modifying acceleration and jerk settings during print but that's another story) but ...
anyhow, for me showing proper data in s3d is not too important, I look at the g-code and decide if that's what I want or not .. and then when I get what I want I send it to octoprint... there, before printing, for me is good to know how much time and how much plastic I'll have to spend and that's why I plan to make this (once) in to octoprint plugin
... of course if s3d exposed plugin interface I'm sure I'd make s3d plugin too but right now the only way to do it is to add it as postprocessor for saving file that would pop up some info... not very nice nor useful nor user friendly
gwhite wrote:
you've shown that a path exists.
the path is there for a while
for e.g.
http://gcodeanalyser.com/
I shared the relevant piece of code already here
https://forum.simplify3d.com/viewtopic. ... 310#p36310