Folks, I am new to Simplify3d and think I screwed something up and cannot find a way to reset it.
At some point I think that I set the temperature sampling rate to a very short interval. It seems that now half of the entries in the Communications window on the Machine Control Panel are temperature reporting.
Unfortunately, I cannot find where I set this up in the software.
Can someone point me in the right direction to reset this?
That might be and I may be trying to solve the wrong problem.
I find that I cannot issue any gcode commands in the communications window. If I issue a G28 or M119 code, I get a message saying unknown command. I figured that with so many M105 commands being issued automatically, the ones I tried was being timed out. Obviously, this is not the case.
So tell me, what is the trick to sending GCode commands manually?
If you get a message saying "unknown command", that is coming from the firmware. So it has nothing to do with the software. You need to figure out what commands your firmware supports.
You haven't given any details about your printer, so I can't really offer any other help
If everything is working OK but you don't like the constant stream of temperature info on your screen, you can go to the Machine Control screen and uncheck "Verbose" up near the top-right.
CompoundCarl. Thanks for your response. I am running a MendelMax 2.0 with the latest marlin firmware.
I've tried several commands like M119, G28, and G0 x100, y200 z100
All to no avail.
I found the GCode Library and entered a few command scripts there and it seemed to work fine. However, that's not the answer as this will only allow me to issue static commmands that I previously saved as scripts.
I am new to Simplify3D but have been running Repetier for a year or so quite successfully.
My whole Simplify3D install was quite squirrely so I removed it and all traces of it from my drive and registry. I have a new install now and some of the things that were not working (Real Time Updates and the system ignoring my End script) seem to be working fine now. Perhaps my problem issuing gcode commands directly has gone away as well. I'll test it out when my current print is finished.