Welcome! Log In Create A New Profile

Advanced

Minor updates: firmware 0.78r-dc42 and web interface 1.02

Posted by dc42 
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 08, 2014 05:46PM
When the PC keeps making USB keeps connecting/disconnecting sounds, if you run M122 and look at the message log, what value is shown for "Never used RAM"?



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 04:45AM
Well today it's not making USB connect/disconnect sounds.
When I tried to print (to see if sound is back) i had again problem with extruder not getting to 200*C in 120 sec.
And i have M301 H1 S1.0 command.
I don't get it anymore?
Attachments:
open | download - Last problem.png (76.3 KB)
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 05:26AM
1. Please attach your config.g file to your next post - I know you have posted the contents as text, but I would like to check the actual fie.

2. See this post [forums.reprap.org] for how to adjust the T parameter on your system. Leave S at 1.0.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 05:53AM
This is the config.g

So if i got value of 117,4 at 200*C this means T value is 0.671.
Do i just put in command M301 H1 S1.0 T ???
I understand that T value is by default 0.25, If i have 0.67, this means that it should go down or up?
Or just set it to 0.25

Edited 1 time(s). Last edit at 09/09/2014 06:15AM by Mercnik.
Attachments:
open | download - config.rar (932 bytes)
open | download - config.g (1.8 KB)
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 06:53AM
It sounds as though your heater is producing quite a low power. Try setting your T parameter to 0.67 in that M301 command. If that causes the temperature to overshoot, try a lower value such as 0.5. The default value of 0.25 is certainly too low for your Ormerod, I can tell that from the shape of the temperature graph.

Edited 1 time(s). Last edit at 09/09/2014 06:54AM by dc42.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 07:17AM
One more question. I see you have set the axis compensation to zero in config.g. If you send command M503 to list config.g from the printer, does the output in the message log show that the M566 command has parameters X0 Y0 Z0 ?



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 07:41AM
Ok.
I have set T to 0.62, if higher it was overshooting (not much 1*C)
But if lower, then it reached 198 quite fast, but last two degrees it took almoust a minute.
I will try to print the snowman, to see if everything else works ok.
The bed compensation (set to 0), and all other things that i had problems with in last few days.
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 11:11AM
The USB disconnects sound like there may be a bad solder connection on the Duet USB socket - check it by eye (with a magnifying glass) - unfortunately a common problem with that type of connector because pulling on the cable puts strain on the solder connections. Or maybe your USB cable is faulty.

Dave
(#106)
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 01:54PM
Yes axis compenstaion in log shows 0.
There are no visible bad connectins or bad soldering on the duet USB socket.
I
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 02:07PM
Quote
Mercnik
Yes axis compenstaion in log shows 0.
There are no visible bad connectins or bad soldering on the duet USB socket.
I

Try a different USB cable in that case. Maybe your phone uses the same type?

[Added] - OTOH if you update to DC42's firmware and web interface you can get rid of the USB cable completely.

Dave
(#106)

Edited 1 time(s). Last edit at 09/09/2014 02:08PM by dmould.
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 02:29PM
I tried different cable. I have new firmware and webinterface,
I use webinterface and pronterface, becouse, if print goes bad, you can not move axes after pause or stop in webinterface.
So i use bouth to move z up, to clean nozzle or something else.
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 04:53PM
Quote
Mercnik
I use webinterface and pronterface, becouse, if print goes bad, you can not move axes after pause or stop in webinterface.

That's not quite correct:

The STOP button does an emergency stop. The printer will remain halted until you reset the Duet. You can do this by powering it off and on, or by pressing the reset button, or by sending the M999 command via the web interface.

The Pause button pauses the current print. After a Pause, you can either Resume the print, or Reset. After a Reset, you have full control of the printer again.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 09, 2014 05:56PM
Yes that is all true.
If something goes wrong (first layer not sticking, or something similar. or now when i had problems...)
I just wanted to pause/stop, retract fillament, move up Z axis' to clean nozzle, home all axes and try again.
Without reseting, homing, bed leveling, reheating bed..
But i can not move motors when in pause or when stoping print.
I do ewerything ower web, just when i stop the print, I use pronterface to, move up nozzle before turning off heater.
It is easier to clean
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 10, 2014 05:05AM
Quote
Mercnik
Yes that is all true.
If something goes wrong (first layer not sticking, or something similar. or now when i had problems...)
I just wanted to pause/stop, retract fillament, move up Z axis' to clean nozzle, home all axes and try again.

You can do all of that from the web interface when the print is paused - I have just tested it.



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 10, 2014 10:28AM
Quote
Mercnik
Yes that is all true.
If something goes wrong (first layer not sticking, or something similar. or now when i had problems...)
I just wanted to pause/stop, retract fillament, move up Z axis' to clean nozzle, home all axes and try again.
Without reseting, homing, bed leveling, reheating bed..
But i can not move motors when in pause or when stoping print.
I do ewerything ower web, just when i stop the print, I use pronterface to, move up nozzle before turning off heater.
It is easier to clean

You most certainly can move anything you like after pausing a print by using the Web interface control buttons or G commands. Move X,Y,Z and E, change temperatures, change home positions etc. I have done so often. I cannot think of anything that can be done in Pronterface that cannot be done just as easily in the web interface. I do not understand exactly what you mean - you say that you would like to home all axes and try again without homing?

If a print is going wrong at the start I simply (1) pause (2) reset (3) set the bed temperature again so it doesn't cool (4) clear the bed of the failed print, remove cause of failure etc. (5) home as required (6) start the print again. I cannot see it being any different in Pronterface. Adjusting the Z height without aborting the print is done in the same way as Pronterface. (1) pause and note current Z height (2) move Z up or down using buttons or a G command (3) enter G92 Z (4) resume. Or do as I usually do and just give the Z screw a firm turn in the appropriate direction while it is printing. That forces the nozzle up or down a step or two against the force of the stepper motor (does no harm to the motor) and the firmware doesn't know it has happened.

Dave
(#106)
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 11, 2014 12:03PM
I realized that. I couldn't move anything in old webinterface. Or when pushing STOP.
It works fine now. I had a lot of problems with software.
Not shure why, but things that should work, didn't.
Or didn't work sometimes.
I'm learning...
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 12, 2014 02:19PM
Hey Dave, This may have been suggested allready but it would be helpful (atleast for me) if you could add a name when adding a temp, I made a example image.


I will update to your firmware and update the web interface the minute I find my damn usb cable hahaha, its lost among the hundreds of cables I have in my office

Best regards


Youtube: [www.youtube.com] 3D printing videos
3D Hub: [www.3dhubs.com] Pictures of stuff I've printed
Thingyverse: [www.thingiverse.com] More pictures
Facebook: [www.facebook.com]
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 22, 2014 12:36PM
I'm just back from holiday (hence no firmware updates for a while) and planning to produce a new firmware revision tomorrow. The changes I have in mind are:

1. Add support for Simplify3D, in particular to read the filament needed. Looks like zpl has already done the work!

2. Fix bug whereby Z homing moves (and possibly others) with axis compensation enabled cause a shift in the reported XY position.

3. If time, complete the support for the serial interface that will be used for the TFT panel + rotary encoder control board.

Have I promised anyone anything else in the last couple of weeks?



Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 22, 2014 01:13PM
Welcome back @DC42 and that sounds like a fine list to have completed one day after you return thumbs up
Re: Minor updates: firmware 0.78r-dc42 and web interface 1.02
September 22, 2014 07:25PM
Hi dc42, you didn't promise any of these, but I hope you consider merging my following changes into one of your future firmware releases smiling smiley

Quote

- Modify XY homing moves to set the final axis position (either axis min or max) depending on the move direction. I've implemented this in my firmware fork to hopefully add support for the new Ormerod 2 Y-axis, so O2 users don't have to rely on G92 in their homing files any more. That seemed kind of reasonable to me and required changes to only two lines of code IIRC.

- Think about M0/M1 again - does it really make sense to disable all the drives when M0 (Stop) is called? In my firmware fork, every drive is only disabled if M1 (Sleep) is called. My motivation for this change was to simplify print restarts, and of course I've modified my web interface fork to match this behaviour.

- Reset homed axes in the GCodes class whenever axis drives are either disabled or axes are being homed. This provides a nicer feedback on the web interface, too.

- Add the possibility to pass certain axes and/or extruders to M18/M84 (Disable drives). I saw a commit on Cura's GitHub page the other day in which "M84 E0" was added to their RepRap G-Code generation files, so I want to stay compatible with it just in case.

- You may want to implement an internal code queue in the GCodes class to run non-moving codes just-in-time. By non-moving codes I mean codes which don't have an immediate effect on the Move class, like M106 or so. On that occasion you could also modify M23 to pause a print as soon as the current move finishes, just as in my firmware fork.

Edited 1 time(s). Last edit at 09/22/2014 07:27PM by zombiepantslol.
Sorry, only registered users may post in this forum.

Click here to login