@phaedrux Yes - thank you!!
Best posts made by noblebran
-
What my board controls.
I have a Tevo Little Monster and its just the frame that is left now that I have the Duet Wifi and PanelDue 7i. It is a delta printer that is 350 x 550mm.
-
RE: Start / Stop S3D SCRIPT / G-CODE
@fcwilt Okay, thank you for the explanation my friend.
-
RE: PanelDue “connecting”
@phaedrux yes I read all those. I changed the baud rate on the screen to match what the code was. Then to update the firmware I had to connect via USB to the panel. Thank you.
-
RE: Start / Stop S3D SCRIPT / G-CODE
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
Now with that out of the way let's turn to config.g.
You have an M587 there which not be used in config.g. You use that command when setting up the WiFi connection but you don't keep it in config.g.
At first glance everything else looks reasonable.
Does the PanelDue work?
Does homing work?
Can you move the nozzle to all places in the printable area?
Can you move over the range of the Z axis?
If you move to Z=10 and do a G30 does the Z probe work?
If you activate the heaters do they heat as expected to whatever temperature you specified?
Do the fans work?My PanelDue 7i works, I haven't been able to print an enclosure for it so I haven't really been using it, but it connects and shows readings, etc.
Homing does work.
Yes, I can move the nozzle to all places in the printable area.
I can move the nozzle over the range of the z axis using code, I can using the dashboard buttons. Homed it is x0, y0, z515 so when I put in a g1 z- command it goes down.
The z-probe worked, re-calibrated just now (put the bed at z5, now its z6.35), I thought I put that correction in the config, but I guess not (as you know its the distance between the nozzle tip and tip of the probe).
The heaters work, but I have another thread going as I always get faults that my block heater goes way above the set point. I have all e3d parts, I don't have an e3d cartridge thermistor but I didn't get one when I received the parts years ago and it worked when I had the old smoothieware system (MKS Base). The bed works great though.
The fans work (I think). I say I think because my heatsink fan is on 24/7 now, which I know is because of the connection I plugged it in. My part cooling fans are set to turn on when the temp goes above 50 I think but I didn't know how else to control them as I would normally in the slicer.
I did do an autocalibration and it worked
Besides the extruder heater/thermistor and the fans (but they work) I think to answer everything I would say yes besides my comments above. Sorry for the abundance of detail.
-
RE: Start / Stop S3D SCRIPT / G-CODE
@noblebran Thank you sir! Be well!
-
RE: Start / Stop S3D SCRIPT / G-CODE
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
My first post to you included my complete print_begin.g and print_end.g files.
In my next to last post I simply listed the basics things that needed to be done before a print.
I thought perhaps my files might make sense now that we have conversed.
FrederickI am sorry, yes I see it. I can make it work. I don't know if you want me to post here but can I put my files that I create and have you do a sanity check? I appreciate it.
Now I have to deal with my fans not working now (always on fans).
Thank you again sir.
-
RE: Start / Stop S3D SCRIPT / G-CODE
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
How can you be waiting for hotends/bed to reach temps when you cannot, as a practical matter, set them in config.g?
Frederick
It must be done in the slicer? I choose the bed and temp setting, after I slice it in S3D, it has the code in the file (part GCODE file).
No, it does not have to be done in the slicer.
I do it using the filament handling feature in the DWC.
I have entered in a number of different filaments that I use into the DWC.
For each filament entered there is a special config.g file created.
My start code is in a file named print_begin.g and is invoked from the slicer with M98 P"print_begin.g"
In that file I have (among other things) this:
T0 ; select tool 0 so extruder commands below will work M703 ; configure selected filament (sets bed/extruder temps, extrusion multiplier) ; some other unrelated commands M116 ; wait for temps to reach set points
That M703 command invokes the special config.g file for the currently selected filament and in that file I have any commands I want unique to that filament and in that file I set, at a minimum, the bed temp, the hotend temp and the extrusion multiplier.
I have found this to be an effective way to set my temps and I can use different slicers easily as the start code is on the Duet, not in the slicer.
But this is just my way. You should do it in whatever way suits you the best.
Frederick
Thank you sir, I find I like to 'master' one slicer and I guess I almost put all my eggs in one basket so to speak. I will certainly take advantage of the way you are doing it but I want to get successful at printing the way I am now. I can say my load and unload macros work, ha ha... baby steps
Again thank you for helping!
-
RE: Start / Stop S3D SCRIPT / G-CODE
@fcwilt said in Start / Stop S3D SCRIPT / G-CODE:
@noblebran said in Start / Stop S3D SCRIPT / G-CODE:
Thank you both!
Glad to help in anyway we can.
And if we cannot help we will try our best not to mess things up too badly.
Frederick
ha ha thats all I can ask for!
Now it is just fine tuning...