Sovol SV08 Multiple Motion System Upgrade.
-
@dwuk said in Sovol SV08 Multiple Motion System Upgrade.:
I would only use Z for layer changes, with all other Zhops and mesh adjustments being done independently with the B and C Zhopper axis.
That's what I proposed to implement in RRF while I played with the hashPrinter.I wonder if it's possible to use G10/G11 for FW-retraction with zHop in your case? You'd have to link it with your BbCc motors. @dc42 ?
-
@o_lampe Interesting - I hadn't thought about firmware retraction - its turned off in my printer profile - but if I turn it on - I get this as a typical sequence
G10 ; retract ;WIPE_START G1 X140.121 Y84.188 E-.24 ;WIPE_END M486 S-1 M486 S1 G1 Z.6 F15000 G1 X152.303 Y279.456 Z.6 G1 Z.2 G11 ; unretract
I've created my own ZHOP command - M800 - I guess I could use being inside a G10/G11 pair to know to change the Z moves to my M800 commands.
I will also try just commenting out the Z moves (or turning off Z Hopping in the slicer), and try setting the Z axis to my B/C axis in the M563 tool definition as you suggest- and then specify Z Movement in my M207 to see what happens.
Will also try turning on meshing with my BC axis defined as Z to see if it does any auto adjustments using my axis, rather than the proper Z Axis.
-
After snapping off the V gantry end stop for the 2nd time, decided to move the end stop off of the print head onto the flying gantry, and also changed to optical.
Also took the opportunity to redesign the rear gantry holders to allow them to slot in between the idlers at the back - to give about 15mm of extra Y movement.
Got a nice bit of exposure for my project (and its Duet electronics) from Micheal Laws on the Teaching Tech YouTube channel today - see the brief mention in first 2 minutes of this video.
https://youtu.be/F5lyLPyndTU?si=zS3x0FlBM8Jj7b65Made a start on the IDEX belt design. My current thinking is having the two Y belts on the side of the flying gantry - with both motors at the front - to help balance the whole gantry.
The design will be mirrored on both sides of the gantry.
-
@dwuk3d said in Sovol SV08 Multiple Motion System Upgrade.:
Made a start on the IDEX belt design.
Not sure if I get it right: the two Y motors positions indicate a different kinematic model, it seems you want to use a H-bot design mixed with CoreXY? Or is it some markforge stuff?
Another problem might be the M800 macro. IDK if it's smart to use macros while printing dual stream...IMHO you should replace G10/G11 commands with the macro-content by your postprocessor
-
@o_lampe I think it is called Dual Markforge - its the same as the Ratrig Vcore4 idex - doubled up.
Attempt at demo here - although when I re look at it I think there are some errors in the animation - as it should be top belt for one X axis and bottom for the other
https://youtu.be/CjgITPc4vNg?si=SDhkxPcVuqdtXxy6Re G10/G11 - changed post processor to be aware of them and switch the Z movements to my M800's, which handle both servo and stepper based Z hopping.
Also added in G10/M800 M800/G11's around long added G0 moves due to segmenting that seems to work quite well.
Have decided to drop the servo and switch both gantries to stepper based Z hoppers - which might allow me to remove the M800's and let the G10/G11s to do the Z hopping.
Also my little Z hopping stepper isn't really up to the job I think as it is a bit slow and gets hot on idle. I'm currently turning off idle current after every move - but that makes it lose its homed status which I doubt G10/G11 would be happy with.
Tried lowering currents down to 1% instead of- but that seems to mess with parallel printing as I don't think the current changing code works well on motion system 1.
Have ordered two more motor options to try - lead screw Nema8 and lead screw Nema11 - hopefully one or both of those will be faster and have less heatup issues.
-
-
@dwuk3d said in Sovol SV08 Multiple Motion System Upgrade.:
Update - found a command by looking at the RRF code - M606 S1.
This seems to be needed to get the parallel printing to work - it is not mentioned in the Multi Motion System documentation - but is in the Gcode dictionary.
Thanks for pointing this out, this may be the reason that multiple motion systems haven't been working for people. Unfortunately, it mostly beyond my test rig (and comprehension) to test! However, from your description, I think I understand how it should be used. I've a couple of the paragraphs in the documentation to highlight M606:
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Multiple_motion_systems#enabling-and-selecting-a-motion-queue
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Multiple_motion_systems#command-streams-from-fileCan you check they are correct from your understanding, please?
Ian
-
@droftarts Looks good. The only comment I have is that in my current test configuration I have the M606 near the end of the Start Gcode in Orca Slicer, not at the start of the print file - just before it starts actual printing - as I didn't need homing etc. to be parallel processed.
I wouldn't personally expect to put it in the start.g - as I wouldn't want every print to be forked, also I guess the Macro issue mentioned in this post might start occurring.
-
Managed to get Voron Tap type probing to work on the front gantry, and printing now working fairly well. Time now to return to the alignment probes.
Electromagnet wired up - on Mini5+ 6A output - which has a flyback diode ok
; Electro Magnet M950 P4 C"1.out1" M42 P4 S0
Magnet seems to work ok - and hold pliers on anything above S30
Next on to Servo - decided to use on of these, as I have a few in stock
Powering it with 6v for now - via a LM2596 Buck Converter from the main input PSU
Tried it on io0 - but it didn't work as no PWM (although no error message).
Switched to io1 and now workingM950 S0 C"1.io1.out" ; Probe Servo M280 P0 S60 ; Set Servo
Made hole in case to hold servo next to bed.
3d printing of parts and macro's tomorrow.
-
@dwuk3d Those digital servos can draw a lot of current. You'd not want to block the arm or run it above the spec'd angle or the buck converter might fail.