@jay_s_uk : ok got it. you can mark this thread as Solved.
Thank you again!
Best posts made by JayT
-
RE: Configure dual extruder via expansion board
-
RE: Shifting Issue After Resuming APF in RRF
I have one machine on Duet3. I flashed 3.5RC4. after this extruder motor holds the torque but does not move on extrude commands. When i go back to 3.4.6, it extrudes fine. looks similar to what she's reported. Mine is dual extruder.
Can anyone confirm that 3.5RC4 with their system:
a) drives dual extruder fine
b) Can you test Resume after power failure & check if it resumes fine & does not print from an offset. (for me it occurs in Y direction only).
This happens with Duet2 wifi based belt driven machine.c) Can anyone suggest a few checkpoints ?
-
RE: Configure dual extruder via expansion board
I have attached the config file.
NOTE:- IF I run M115 B40 or M115 B41, I get positive response. both communicate well & the LEDs blinking is in sync. Same 3.4 beta3 on all boards.
- Also I noticed, if I configure single board with B40 address and run the second extruder it works. So this confirms no problem with second motor or the board. Something in config is weird?
- I haven't used G4 commands.
NOTE: config is too raw, just for trial purpose. main purpose is to try running dual extruder via exp- 1XDs. - B40 (no jumpers), B41-XD : jumper on CAN-FD-OUT.
Mainboard to B40 in -> B40 out -> B41-in-> Jumper on the B41-out. - I tried removing all jumpers too to see just in case it works.
(not able to upload file , so pasted images of the config).
-
RE: Shifting Issue After Resuming APF in RRF
@JayT :
This problem of extruder not working with Duet 3 is resolved after flashing RRF3.5.1.
Shifting problem remains same with Duet2, after resume on power failure. -
RE: Simulated time turns N/A before print ends
@JayT
@dc42 : After few trials, we confirmed that since timer (job duration & the decrementing simulation time) starts immediately after pressing Print. Here if the bed & extruder temperatures are not attended yet, the warmup duration accounts only for bed heater time to attain target temperature. Extruder time to attain temperature is not accounted.
Hence we reach to condition (t<0) and simulated time completes displays N/A, while print is still running for few minutes.2 methods to resolve this:
- We account extruder temperature also in warm up duration
- we start simulated time once Print actually starts (after warm up of bed & extruder)
What do you suggest ?
Do we evaluate time to attain extruder target temperature? Can you direct us to the code to change? -
RE: Gap in printing concentric circles-(CW side)
@modl :
Seam is not the issue. If we change this, it does not reduce gap.
Backlash does though. But even then I see the flatness at the top & bottom surfaces of the circle.I also observed very less similar flatness in left & right most sides of the circle. Is this due to some slippage?
Latest posts made by JayT
-
RE: RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
@droftarts said in RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error:
I notice you are not enabling networking. Are you running the simulation from a PanelDue?
Yes, I ran simulation via PanelDue, not from DWC.
Thanks for trying. If gcode simulated well, ***Will try with new SD card.@droftarts said in RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error:
Is there a reason you're running debug logging? This will impact performance, and means a lot of writes to the SD card. It could be that the level of logging has increased in 3.5.1, and is causing what was a marginal problem on the SD card to become a real one.
Is that so for 3.5.1? I am writing to SD card with debugging enabled, to debug problems if faced during printing. This log file helps me to understand at times if the print fails or there are problems w.r.t gcode, if dwc isn't connected.
What solution do you propose then? Is there a way to create log some other memory place? -
RE: RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
@droftarts : Please see config below. I am not using daemon.g
; General preferences G90 M83 M550 P"INFD300s" M551 P"INFD300" ; Network ;M552 S1 M552 S-1 M586 P0 S1 M586 P1 S0 M586 P2 S0 ; Drives M569 P0 S1 M569 P1 S1 M569 P2 S1 M569 P3 S1 M569 P4 S1 M569 P5 S1 M584 X0 Y1 Z2:3:4 E5 M350 X32 Y32 I0 M350 Z16 E16 I1 M92 X160.0 Y160.0 Z2133.33 E932.00 ;change as per machine M566 X720.00 Y720.00 Z300.00 E600.00 M203 X8400.00 Y8400.00 Z420.00 E8400.00 M201 X3000.00 Y3000.00 Z30.00 E250.00 ;M-curr M906 X2200 Y2200 Z1600 E800 I50 M84 S30 ; Axis Limits M208 X0 Y0 Z0 S1 M208 X300 Y300 Z304.1 S0 ; filament Sensor M591 D0 P7 C"exp.e3stop" R15:300 L7 E17 S1 ; Endstops M574 X1 S1 P"xstop" M574 Y1 S1 P"ystop" M574 Z1 S1 P"zstop+e0_stop+e1_stop" ; Z-Probe M950 S0 C"exp.heater3" M558 P9 C"^zprobe.in" H5 F120 T6000 G31 P500 X0 Y0 Z1.038 ; Auto level, coordinates as per motor order in M584 M671 X-17.66:297.34:140.00 Y-5.00:-5.00:327.61 S5.0 ;points position with left right ¢er ; define mesh grid M557 X30:300 Y30:300 S20 M376 H5 ; End Limits M950 J1 C"exp.e4stop" M581 P1 T2 R0 S1 M582 T2 M581 P-1 T2 M581 P1 T0 R0 S1 ;PA M572 D0 S0.055 ; Bed Heater M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 M950 H0 C"bedheat" T0 M307 H0 B0 S1.00 M140 H0 M143 H0 S105 ; Extuder Heater M308 S1 P"e0temp" Y"pt1000" M950 H1 C"e0heat" T1 M307 H1 B0 S1.00 M143 H1 S320 ; cooling Fans M950 F0 C"fan0" Q500 M106 P0 S0 H-1 M950 F1 C"fan1" Q500 M106 P1 S0 H-1 ; Tools M563 P0 D0 H1 F0 G10 P0 X0 Y0 Z0 G10 P0 R0 S0 ; Miscellaneous M575 P1 S1 B57600 M501 M911 S21 R22.5 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000" M929 S3 P"/macros/log/DEBUG.txt" M17
-
RE: RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
@droftarts :
I will check on this , however...If its SD card issue, then why don't I get same problem when I flash 3.5 RC4/3 or on older version of RRF, for the same gcode file?
Can you try to simulate them in your printer with RRF3.5.1 for once, with Duet 2 wifi? -
RE: RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
@Phaedrux : @chrishamm : It uploaded well please see with RRF 3.5.1version.
-
RE: RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
I am using Duet 2 wifi. Will share a few gcode files. As stated, this problem isn't in 3.5 RC4 much.
I am not able to upload gcode file directly. How do I share?. -
RRF[3.5.1]/RRF[3.5.0] : Gcode bad command error
If I simulate the gcode, I get some errors like bad command or message box stating expected integer after Y.
Sometimes error says "C1 " instead of G1. When I look back at the line number in Gcode, Line looks ok.Because when I run it the second time, or simulate second time, bad command error either does not come at all, or it comes at a different line.
My problems are similar as posted in the thread :
https://forum.duet3d.com/topic/35553/bad-command-error-using-rrf-3-5-0-and-3-5-1-using-duet2-wifi/2- I tried with different versions of cura, problem remains same.
- Everytime line number and error changes for bad command, even during simulating
- I tried 3.5RC4, such problems are not faced before 3.5.0.
-
RE: Resume.g activating twice With FW3.5
@Notepad :
I noticed this too. I had set some extraction in pause.g to resume well. Now it creates blob.
IF you resume after power fail, does it resume well for you ?
-
RE: Software 3.5.1 released
If i simulate the gcode, I get some errors like bad command or message box stating expected integer after Y.
Sometimes error says "C1 " instead of G1. When I look back at the line number in Gcode, Line looks ok.
Is it a problem with Slicer & after error Reprap fixes it ?
Because when I run it the second time, or simulate second time, bad command error either does not come at all, or it comes at a different line.My problems are similar as posted in the thread :
https://forum.duet3d.com/topic/35553/bad-command-error-using-rrf-3-5-0-and-3-5-1-using-duet2-wifi/2