Simplify3D User Forum

Hi,

Sometimes I am sending some commands to the MACHINE CONTROL PANEL of S3D and it gets a huge mess because it keeps sendins M105 command all the time. It is terrible cause I cant follow easily the comands I am sending and their responses cause ALL THE TIME S3D is sending M105 command.

Pronterface does that too BUT IT DOES NOT displya any sending/reading data when it's M105 command to avoid trashing the serial output.

How can I disable this anoying and terrible M105 command from being showed in the serial?

Just uncheck the "verbose" option at the top left. That hides the M105 commands and only displays actual warnings or echo messages

I didt exactly what you said but unchecking verbose does not display most of the commands I try to execute. it hides everything.

Is there a list of commands for the machine control mode? i would like to view its position

M105 is the code for requesting the extruder temperature....which S3D will be monitoring.

Try unchecking the Monitor temperature indicator in the Temperature Plot tab of the Machine Control Panel. It might then stop the requests being sent.

I realize this is an old question, but since it is likely the same version of Simplify3d it is still a current issue. The point that the OP is trying to convey is that it is only the software monitoring the extruder temps, the user does not care to see BOTH the command being sent, the reply coming back just to see what the software is updating the display with as well. There are some commands that are simply of no use to the user. I personally would be happy with the ability to log the output to a file. Try running an autotune PID, then leave the room to empty the drier in the basement. By the time I get back to the software it has completed the autotune, posted the results to the Verbose screen(since you do not get the output if not verbose) and has gone past the log files size limit and is gone forever. I have a hard time believing that I am the only person that has fallen for this.

Its simple, create a simple flat file that the user can enter the gcodes he/she wishes to either block or display in the standard log, then you can use the verbose log setting to capture it all, and save it to a file. Or, simply start showing autotune commands in the standard log.