@Freddy I'm glad you solved it. Out of interest, what motor currents are you using?
Posts made by dc42
-
RE: Duet 2: Driver 1 Over Temperature
-
RE: Macro string errors in print files since update to 3.5.1
@clegg78 is the end gcode (the M98 line) being repeated in the form of a comment later in that gcode file? As the macro call is working, perhaps the lines you posted are not the ones provoking the error message.
-
RE: Printer hanging during tool change with v3.5.1
@Gamefanatic3D thanks, I'm glad that workaround worked for you. I've created https://github.com/Duet3D/RepRapFirmware/issues/998.
-
RE: GCode meta commands case senetive?
@Chriss yes meta commands, function names and variable names are case sensitive.
-
RE: Failed to connect Unexpected token '<'
@Asabol please tell us what board, firmware version and Duet Web Control version you are using.
-
RE: Ignore W channel on M150 if RGBW not Supported
@robotsneversleep in the M950 command to declare an LED strip you need to specify whether it is RGB or RGBW because RRF has to drive them differently. Assuming you get that right, if you provide a W parameter but the strip was configured as RGB then that parameter will be ignored.
-
RE: Printer hanging during tool change with v3.5.1
@Gamefanatic3D from your M122 report I can see that the job is held up waiting for the tpre file to complete, but it hasn't completed because there are three G10 P0 commands pending. These appear to be coming from your tconfig0.g file.
I don't yet know what is causing these commands to remain pending; however if you insert a M400 or G4 P0 command before the M98 P"/sys/tconfig0.g" line at the end of tpre0.g, that may work around the problem.
-
RE: duet 3 6xd
@gardon64 said in duet 3 6xd:
hi all pc wont connect to my duet 3 6xd
red green red led lit but i get this error Unknown USB Device (Device Descriptor Request Failed) pls helpIf the 6XD is not running firmware (in which case it should flash the red STATUS LED once a second) then it is probably in Bossa mode. When in Bossa mode the MCU unfortunately puts the USB port in high speed mode, which makes it very sensitive to the cable. In particular, using cables longer than the recommended maximum for USB, or using USB extension cables, is likely to result in the "Device Descriptor Request Failed" message that you report. So try a good quality USB cable, making sure that it is a data cable and not a power-only cable.
If you are not sure whether the board is in Bossa mode, you can put it in Bossa mode by fitting the Erase jumper and then pressing the Reset button. Remove the Erase jumper before you use Bossa to program it.
-
RE: Probe deviation / calibration questions
@whizzard I've just run probe reproducibility test on my delta. Test conditions:
- Hot end heated to 200C, to soften any filament on the nozzle tip
- Probing speed 1200mm/min (i.e. 20mm/sec - this is the recommended probing speed. I also trued 2000mm/min (33.3mm/sec) and obtained similar or slightly better results.
- 1 dummy probe done (reading ignored) to squash any filament on the nozzle tip, followed by 10 probes, done at bed centre from a height of 3mm
- Each probe done twice, repeated if the difference between their stopping heights differed by more than 0.020mm (two probes was enough most of the time)
- The machine has x16 microstepping and 200 microsteps/mm on the towers, so the theoretical resolution is at best 0.005mm.
The standard deviations were 0.018, 0.010, 0.009 and 0.015. I then repeated it at 2000mm/min (33.33mm/sec) and had deviations of 0.008, 0.004, 0.004 and 0.005. When I ran the test a little later, it had increased to about 0.015mm before reducing again.
Observations:
- Filament on the end of the nozzle makes a a big difference to the deviation. I presume this is because it softens the impact, making the time of contact less precise.
- You can't expect better deviation than 1 microstep. Many deltas use x16 microstepping with 80 microsteps/mm, so in this case don't expect less than about 0.012mm deviation.
I always heat the bed to temperature (in case it changes shape) and heat the nozzle to 200C (to soften any filament on the tip) before running auto calibration. I have the probe Z offset set to -0.050mm (i.e. it triggers when the nozzle reaches Z=-0.050mm). Then I print at 200 to 240C depending on the filament.
HTH David
-
RE: Cannot run CNC slower than 0.6mm/min
@droftarts said in Cannot run CNC slower than 0.6mm/min:
I'm not sure, either, but the 'maximum time that a move is allowed to take is about 30 minutes" came from @dc42, so probably need his input on that one. I guess segmentation would make it okay?
Correct. Implementing segmentation automatically for long-duration moves is already on my list.
-
RE: Unable to get sensorless homing working....
@Chriss the sentence is "For example, M574 X1 S2 and M574 Y1 S3 sets the X and Y endstops to sensorless homing at the axes low end". It's an example. However, it's unclear to me what the following sentence "This is required." refers to, or why it's there at all.
-
RE: Duet3 6HC v1.02 and later
@Sophiechka maximum recommended voltage for the 6HC 1.02 is 50V. When you turn off a stepper motor, it feeds power back into the power rail, causing the voltage to rise. That's why you need to keep the power voltage well below the stepper driver rating of 60V.
-
RE: M122 Duet 3 Mini 5+ Drivers not found
@brampie do you have a 2-driver addon board plugged into the Duet 3 Mini? If so, please remove it and then see whether the drivers are found.
-
RE: HardFault causing failed prints 3.5.1
@Nate-Nygren please see my response to this thread which I see you have also contributed to https://forum.duet3d.com/topic/35611/my-printer-reboots-alone/14.
-
RE: M669 polar offset
@jumpedwithbothfeet we don't have a date set for implementing it, however you can work around it using the G10 L2 command to set workplace coordinate offsets.
I have created Github issue https://github.com/Duet3D/RepRapFirmware/issues/993.
-
RE: My printer reboots alone…. 3.5.1
To those of you experiencing this issue, please send the following command after power up, before you start printing:
M122 P500 S0
This will reduce performance a little, however it should change the imprecise Hard Fault resets that I see in your M122 reports to precise ones, which will make this easier for me to diagnose. Then post M122 reports if the problem happens again.
-
RE: Use Custom Timeserver Duet2
@qurt the time is passed by Duet Web Control to the Duet when it connects. If you don't normally have an instance of DWC connected to the Duet, you could use another device that has a real-time clock either to send rr_connect messages over the HTTP interface, or to send M905 messages to the Duet over USB or serial.
-
RE: CNC Parallel SCARA Plasma Cutter - GCODE Issues
@NortonAntivirus if you don't need G93 then you can either ignore the error messages that G94 provokes, or create an empty macro file called G94.g. Similarly for M8.
-
RE: CNC Parallel SCARA Plasma Cutter - GCODE Issues
@NortonAntivirus what board are you using, and what version of RepRapFirmware?