@T3P3Tony and we are back

@tom22 short answer: Open Loop control is easier and cheaper than Closed Loop control, and is good enough for most 3d printing purposes.

That said RepRapFirmware does support servos with the 1CL toolboards, so for those that do require closed loop control for their purposes (possibly including but also beyond 3d printing), the option is there.

@dc42
Thanks David. I'm rethinking the problem. The issue I was trying to solve was potential 'tool' offsets of different pnp nozzle tips during mid job tip changes. The CP40 tips themselves are all similar length but tip to nozzle mounting depth seems to vary a tip change to tip change. Vacuum threshold was going to be the probe feedback.

I not familiar w tool offsets in Openpnp, but that's not what is bothering me. The inconsistent mount depth of the CP40 is. I'm going back the Juki tips that I am familiar with them and they firmly mount at consistent lengths. Probing for the Juki tips isn't needed.

Thanks for the tip.

@SwalBaylor said in Duet 3 MB6XD not sensing temperature change Merged:

I had posted this last week but it wouldn't let me respond to the advice I was given.

Have you verified your email address?

@oliof OK Thanks

@Simone Eventually you have a high "first layer extrusion factor" ?

@wayneosdias

https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Expansion_1HCL#duet3d-magnetic-shaft-encoder

The cable length should not exceed 200mm.

@jay_s_uk

Great! That is the reason, thanks for your help 🙂

Gentlemen,
Thanks so much for your quick responses. Your suggestions have both been very helpful. I've got the solution now.

Using the Object Model browser allows me see all parameters/values. Using the brackets [] to denote a specific item in a list is the way to go.

I ran into a slight snag using them with curl:
7eb8a30b-88e2-409d-8777-501b142c9639-image.png

However, a StackOverflow post https://stackoverflow.com/questions/8333920/passing-a-url-with-brackets-to-curl about using brackets in curl solved the issue: pass in a -g flag to turn off the URL globbing parser https://curl.se/docs/manpage.html#-g.

Now it works perfectly:
77a3d400-f767-4a34-bbf4-31a1e28076c1-image.png

Thanks again for your help,

Mike

@tronman thanks for confirming the fix!

@T3P3Tony
Indeed, right now I realised this, and hurried to my post to correct my mistake. However, you were much more faster 😊

It was not a bug in 3.4.6, where I only could move the motors by commands issued from Panel or DWC, when (or not) homed. Being some time, I forgot that I have not done this manually, but by command.

I hope at least that this will help somebody else, as normally this kind of support should be paid, even with a beer. Have my blessings, then...

@T3P3Tony said in 3 Bed Scanner Questions:

@becky9 thanks for the feedback. The spring steel plates i tested on my toolc hanger (which has a Mandala Roseworks Bed with strong magnets on it) do not show the point magnets through. Once of those is a generic spring steal bed, the other is a Wham Bam one (quite old though, not sure when i first got it)

Thanks for the info. I am using the Mandala Rose Works bed with WhamBam pex sheets. Hopefully I’ll have similar experience.

@damaged_goods

Any ideas …

The photo isn’t quite clear, but I tend to assume the gap might be where the layer changes are located. If that’s true, observe your printhead when the layer change occurs: what you call a "gap" rather looks to me like an imprint of the nozzle tip into the first layer infill. This deduction is far fetched, to drill down on this, you should eventually reduce print speed.

Thanks @jay_s_uk, you are right... I have not seen that I can point out to the probe No. when I use G30. I will give it a try... That looks promising.

Sure, I can merge the points from two files. But it would be far more handy if both print heads can do that job in parallel.

Anyway, I have some other problems with the IR probe and the PEI surface I guess
6e5f9128-53c8-4a3f-ad41-4ff56981fc13-image.png

@Phaedrux

I'm an idiot, I was using temp_1 instead of temp_0 in my config. disregard, works great now.

@racitup in case you are using an E3DRevo hot end, and for the benefit of anyone who is and encounters this thread: early E3D Revo hot ends with white thermistor leads develop problems with the thermistor after a while, with this sort of symptom. The more recent ones with blue thermistor leads are good.

@Allaudri said in Unable to run the servo motor:

; External Drivers
M569 P0.0 S1 R0 T0.2:0.2:0.1:0 ; driver 0.0 goes forwards and requires an active-low enable signal (X axis)
M569 P0.1 S1 R0 T0.2:0.2:0.1:0 ; driver 0.1 goes forwards and requires an active-low enable signal (Y axis)
M569 P0.2 S1 R0 T0.2:0.2:0.1:0 ; driver 0.2 goes forwards and requires an active-low enable signal (Z axis)
M569 P0.3 S1 R0 T0.2:0.2:10:0 ; driver 0.3 goes forwards and requires an active-low enable signal (extruder 0)

I'd guess that your timing is far too fast for the servo driver. Start with something like:

M569 P0.0 S1 R0 T5:5:10:10

It could also be the enable signal, which causes people no end of problems, usually. Please provide a link to the servo driver datasheet or manual, and we'll come up with some better timing for you, and advise on the enable signal.

See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Motors_connecting_external

Ian

@R006 said in 12V under voltage event using MB6HC:

but i have checked there is nothing wrong in machine.

Following that logic, you are victim of a miracle

@o_lampe I don't think we've ever included deployprobe.g and retractprobe.g in a firmware release, or indeed anything in the sys file. If you start with a factory or blank SD card and use the SD_Card_Contents.zip from https://github.com/Duet3D/Duet-2-Hardware/tree/master/Duet2/SD Card Contents you don't get those two files, though confusingly you get a homedelta.g that must be deleted if you are running a cartesian or coreXY machine.

Ian