Posts made by Mirage

Ok small update: (A positive one)

I have unplugged all components from the board including Duex5 except power source. The board powered and the esp connected to wifi! wooohooo! I then reconnected all components one after another (Duet powered off during each plugging of course) and I was able to reconnect all components until full functionality again.

I am suspecting some cabling malfunction at this point, that would be the only logical reason I see. The printer works again.

Will keep you posted of further development.

Thank you for your help

@Veti I am using the one provided with the Duet in the first place. are you saying it might not work?

Device manager does not see it... I'll take them out tomorrow for close inspection of the boards.

I searched the forums for similar issues but could not find anything.

It started to loose wifi connection every 10 seconds, then nothing....

I have checked all wires, made sure no dust was on the board and on the Duex5.
Only a solid red and solid blue leds are on when plugged in, no flashing. The Duex5 shows no led at all.

I have tried un powering the Duet and connecting usb cable. YAT sees nothing either.
All fuses seem to be good.

Is there anything else I can try? Board has been on this machine for 2 years.

Thank you for your help.

Yet another jerk and speed topic....
Anyhow, as I was performing some flow testing last night I came to a halt when I could not raise speed higher than 350mm/s on a 200mm single wall cylinder in vase mode.

Observations

• My settings were:

Duet2 Wifi + Duex5
RRF2.05.1

Accel:
X - 20,000
Y - 20,000
E - 3000
Z - 200

Jerk: 
X - 700
Y - 700
E - 1000
Z - 50

Starting from 300mm/s and up I could see that some section of the perimeter were being performed at different speed and some vibration was occurring.
The DWC speed indicators were also witnessing that speed variation.
I then tried to raise speed again, but nothing would happened, it was in a lock.

Surface finish was like if the tiny segments from the GCode were amplified.

• Here are my resolution settings from Cura (I know 0.1mm resolution might be aggressive):
  

I then tried something....
I bumped jerk all the way to:

Jerk:
X - 3000
Y - 3000 

Magic! speed went up well passed 500mm/s and surface finish was back to normal~ish.

Assumption
Since the GCode little segments are requiring direction change that are so small, the acceleration settings are not used, but jerk is instead.

Question
Is there a way to maintain speed on curves without having to bump jerk? Anything higher than 650-700 triggers step skipping at those accel and speed value.
And the 20000 accel is what allows me to print fast without skipping. Not that fast, but the max I can go with this issue for now: https://youtu.be/ZZDuX6hcd28?t=294

Thank you
Olivier

@BDubs Thank you very much for this advice.

@alankilian thank you very much! the more resources the better! I am keeping that in mind

@alankilian said in ClearPath Servo Motors Testing - So far so good:

@Mirage A colleague of mine from when I lived in Minnesota has made sand plotters for decades and after a successful (Like $2 million on a $50,000 goal) Kickstarter he sells them now.

https://sisyphus-industries.com/

wow ! i did not know these existed until I saw @mrehorstdmd 's post! Beautiful, wonder if this would calmdown my kids....

@mrehorstdmd This sand table is amazing! totally mesmerizing!
Thank you for your feedback. I am going through you impressive material.

Hopefully the auto tuning capability of the clear path will give me the right tools to achieve descent print quality.

@vishiano said in ClearPath Servo Motors Testing - So far so good:

Looking good, can't wait to see a print

Same here! been working at this since July. Getting closer. I have yet to see one successful print created by these motors. A few people have tried, but I have not seen a single confirmation of success.

I have to admit that I am a bit nervous at running into the same dead end... But! luckily I am quite hard headed

So I have been playing with these servo motors for the past week or so and I think that I am on the right "path"

So far here is how I have set them up:
Duet2 Wifi + Breakout board

ClearPath Connector	Duet2 Break out board
Step+ (B+)	5V+ (from Heater6 3pin conn.)
Step- (B-)	Step- (from Drive5 conn.)
Dir+ (A+)	5V+ (from Heater6 3pin conn.)
Dir- (A-)	Dir- (from Drive5 conn.)
En+ (Enable+)	5V+ (from Heater6 3pin conn.)
En- (Enable-)	Ena- (from Drive5 conn.)

I have set the M569 parameters with the followings:

M569 P5 R0 T2:2:2:2 S0

Movements were a bit rough at first but after tuning the servos on the printer One motor at the time with the other one enabled and lock improved things by a lot.

I had drift in the coordinates at first, but I decreased the step/mm from the duet and compensated on the servo config, then played with the M569 timing values a bit. I think they work good now.

Will keep you posted when I have print results.

@Phaedrux Yeah, that's it, I must be lazy...

@dc42 said in Duet 3 NEMA 23 Closed loop with Z axis also using Elec Brake:

@Mirage said in Duet 3 NEMA 23 Closed loop with Z axis also using Elec Brake:

I am definitely keeping a close eye on this new expansion board. My new XY gantry for NEMA23 is ready to take the beating! And clearpaths are in stock

This expansion board is not intended to drive devices such as ClearPath, because it does the closed-loop control on-board. It's intended for stepper motors with built-in encoders (but no control electronics), or stepper motors with our add-on encoder, or stepper motors driving axes equipped with linear encoders.

Oh shoot! that's news to me
I was following this thread in the hope of an update soon:
https://forum.duet3d.com/topic/17780/clearpath-servos-with-1xd-expansion

So would taking the Step and Direction signal directly from the header pins of a Duet2 and level shift it to more than 5V be a better solution?

Edit:
Just realized that this thread refers to a completely different expansion board.

I am definitely keeping a close eye on this new expansion board. My new XY gantry for NEMA23 is ready to take the beating! And clearpaths are in stock

Yes, I do definitely prioritize layer orientation in function of functional load vectors when designing parts. 3D printers and slicers do have very good support functions. A well calibrated and good FDM machine can do supports

Zero support is not a decision factor to me.

All parts for HevORT will require support yes, where is the issue? We have now close to 20 functional HevORTs out there with and another 25 members have reported intention of actual progress in making one.

@fma Thanks Fred!
I switched to rails under bed for easier mounting and more rigidity. Fixing a linear rod under there and the capturing the bearing was getting too much plastic involved. Plus I had a hard time sourcing good LM10UU for that task and did not want to go with misumi solution.

I am using MGN12H replicas worth 10$ each.

Thank you for the prompt reply as always dc42

I am pulling my old and rusty C skills and will get at it Will keep you posted.
Olivier

Good day all!
I know the topic has been touched a few times here but I cannot find the answer to this question.

Q: Can I map 2 additional Axis for the build plate to tilt around the roll and pitch attitude using three Z motors
My bed design can give me around 30 degree of freedom (+-15deg) in all direction.

I have no knowledge about delta printers, but I would assume that they share some similarities with what I am trying to achieve.

I am also totally aware of the immense slicer challenge I am facing. But one bite at the time is how you eat an elephant.

Demo video:
https://www.youtube.com/watch?v=aL7pEEHTTe4

Here is a Fusion 360 web explorer of my Design.
https://a360.co/3gweJiw

Just for the record,

I ran in the exact same situation. The printer gets stuck in busy mode every time i try to resurrect from a power outage.

Before running in this issue the system was refusing to complete the extrusion command from the prologue due to no tool being selected. The tool selection line generated by the system was set to :

T-1 P0

After running M122 (System Status), I noticed that the current Gcode executed was stuck at the first tool offset G10 command. See code below.

=== GCodes ===
Segments left: 0
Stack records: 4 allocated, 1 in use
Movement lock held by http
http is doing "M116" in state(s) 0 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is doing "G10 L2 P3 X0.00 Y0.00 Z0.00" in state(s) 0 <------ STUCK IN BUSY MODE
autopause is idle in state(s) 0
Code queue is not empty:
Queued 'G10 L2 P4 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 L2 P5 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 L2 P6 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 L2 P7 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 L2 P8 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 L2 P9 X0.00 Y0.00 Z0.00' for move 22
Queued 'G10 P0 S225 R225' for move 22

After modifying my resurrect.g by disabling the G10 Tool Offset command, everything went well.

; Resurrect.g file content:
G21
M140 P0 S60.0
T0 P0                         ; For some reason this line was set to T-1 P0.  
G92 X109.706 Y148.431 Z70.550
G60 S1
M98 P"resurrect-prologue.g"
M116
M290 X0.000 Y0.000 Z0.550 R0
;G10 L2 P1 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P2 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P3 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P4 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P5 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P6 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P7 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P8 X0.00 Y0.00 Z0.00 Disabled by commenting
;G10 L2 P9 X0.00 Y0.00 Z0.00 Disabled by commenting
G54
G10 P0 S225 R225
T0 P6
M106 S1.00
M106 P0 S1.00
M106 P2 S0.00
M106 P3 S0.00
M106 P4 S0.00
M106 P5 S0.00
M106 P6 S0.00
M106 P7 S0.00
M106 P8 S0.00
M116
G92 E0.00000
M83
M23 "0:/gcodes/holedwand.gcode"
M26 S17110915 P0.765
G0 F6000 Z73.100
G0 F6000 X109.706 Y148.431
G0 F6000 Z71.100
G1 F1800.0 P0
G21
M24

This might be a band-aid to another problem or wrong setting, but if you come across this issue, you may give this a try.

Thank you! I'll be placing a M561 at the beginning of my bed.g file