Various questions
-
Is there a way to view and edit the .g files on the SD card without removing it? Nevermind, figured this one out, just have to upload a new bed.g or whatever in the settings pane.
How do you make the web interface not cover the move buttons with gcode notifications when you're pressing move buttons repeatedly? I want to keep all gcode in the console log, but don't want to see the big green popup boxes. Am I missing/misunderstanding a setting?
Can we get a warning when settings are changed in the configuration file but not saved?
What does the standby tool temp setting do? Looks like a dualstrusion thing?
What are all the functional stepper driver setting options that we can set in the config.g file?
Is it possible to change the PanelDue brightness?
What is the PanelDue Console page for? Can I get it to display completed gcode commands, or is it for entering gcode commands, or what?
How soon will firmware with a fix for the "crazy effector dance during board reset" behavior be released? I just nozzle-crashed the shit out of the dead center of a brand new sheet of buildtak… glad it wasn't a PEI stack...
-
Is there a way to view and edit the .g files on the SD card without removing it? Nevermind, figured this one out, just have to upload a new bed.g or whatever in the settings pane.
And of course you can edit the config.g file directly in the web interface. I have it on the list to allow the bed.g file to be edited this way too.
How do you make the web interface not cover the move buttons with gcode notifications when you're pressing move buttons repeatedly? I want to keep all gcode in the console log, but don't want to see the big green popup boxes. Am I missing/misunderstanding a setting?
Pressing move buttons should not cause messages to pop up. What commands are you running that give rise to the notifications? You can set a timeout on the notifications, it's "Default Notification Timeout" on the Settings page. EDIT: in the Settings page, un-check "Log any successful gcode" and then click "Apply settings", that should stop it.
Can we get a warning when settings are changed in the configuration file but not saved?
I'll add that to the list.
What does the standby tool temp setting do? Looks like a dualstrusion thing?
Yes, it prevents oozing from the nozzle that is not currently in use. I find 150C about right for PLA.
What are all the functional stepper driver setting options that we can set in the config.g file?
See http://reprap.org/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer#Movement_section, and add M350 to set microstepping.
Is it possible to change the PanelDue brightness?
No, the original displays I designed PanelDue for do not have that functionality. However, most of the current displays do, so I may add it in the next revision of the PCB.
What is the PanelDue Console page for? Can I get it to display completed gcode commands, or is it for entering gcode commands, or what?
It's for entering gcode commands and for seeing the results from commands that return information.
How soon will firmware with a fix for the "crazy effector dance during board reset" behavior be released? I just nozzle-crashed the shit out of the dead center of a brand new sheet of buildtak… glad it wasn't a PEI stack...
I am looking into this. Although I have never see it happen following a software reset, I've recently discovered that it happens on my delta if I press the reset button. So I will be able to test the fix.
-
Regarding the crazy effector dance, I've put temporary firmware at https://dl.dropboxusercontent.com/u/19369680/DuetWiFiFirmware.bin. I believe this resolves the problem when you do a software reset. Unfortunately, resolving the problem when you press the reset button requires a hardware change, which we will make to the production boards. The dance happens for as long as you hold down the reset button. So I recommend that you do not use the hardware reset button, unless you first disable the motors by sending M18 - in which case you might as well send M999 to do a software reset instead.
-
A correction to the above. The temporary firmware does stop the crazy effector dance when Reset is pressed on my 12V bench test system. On that system, the dance only occurred after the reset button was released. However, it doesn't stop the dance on my delta, which (with the new firmware) only happens while the reset button is held down.
My interpretation of this is that some wiring - probably mains wiring or stepper motor cables - that runs near the stepper driver STEP signal lines is coupling capacitively to those lines, and the ~100K pullup resistors in the microcontroller that are active during reset are insufficient to suppress this.
So you may find that the new firmware resolves the issue when the reset button is pressed in your machine. Or not.
-
Seems to have fixed the spazzing out for me. Painless firmware update process as well, very nice.
-
I uploaded the firmware. Will let you know if I see any more spazzing.
