@snippy I couldn't find one or any information that they even make that part number.

It might have been a special for one company.

You can contact them at this site:
https://www.nidec.com/en/nidec-servo/inquiry/

@vwegert is that a positive babystep? If so, then you are correct about the change.
It won't affect anything in terms of using the smart effector

@phaedrux @droftarts yes, I'm part of their beta team. I can forward any suggestions to improve the configurations.

I have find the root of the problem...

It was not a mistake in the configuration of thermistor.... It was simpler.... From what it seems, when mounting the thermistor in the heatblock the screw that held it in position, pressed the cable, affected the readings.... When I adjusted it, outside the Heatblock it gave some temperature values and when it was in the heatblock, it gave others

@örjane yes as we add features to the new site we will allow more people access. for now we are taking it slowly to avoid spam.

In the mean time if you see issues then please let @droftarts know.

@budspencer

Could you describe what you mean by:

"I seem to have an issue with I and J arc factors. Saw on the duet wiki that those two are not supported."

What GCODE are you having problems with and could you post a link to the Wiki that says what is not supported?

@minifiredragon no, there is not. You could go with a duet 3 mini to make it cheaper

@deckingman here you have the files. I have checked them, hopefully you see something I didnt:

tpre1.g tpre0.g tpost1.g tpost0.g tfree1.g tfree0.g

config.g config-override.g

I have no start.g file

M586 command with active and stand by temperatures are set on my load.g file of each filament. For T0 Im using for my tests tis is its file:
[ABS_PRO.zip](Invalid file type. Allowed types are:

load.g

And for T1 for the filament Im using to test (PVA), my load.g is:

load.g

Thanks in advance

@phaedrux ok, thanks. This might be interesting to be redesign in a future. The duet has the ability to add many support extra boards, with a lot of sensors than can be used for many aplications, but I think having to stop the print to wait for a macro to finish might be a big issue to this extra boards.

@dc42 will be a non issue for me in the future, im working on replacing the entire ribbon cable due to its limitations.
will run individual wires, just have to seperate them properly so they wont be close to stepper motor or other higher current wires.

@phaedrux Well color me surprised, the 3.4 RC firmware seems to have fixed it!

Really appreciate your help! Hopefully the RC is stable enough everything works ok but it sure beats a broke printer. Cheers!

@aviationguy said in X and Y move opposite with same config:

Other than possibly LDO changing the steppers between the two builds, any other thoughts on what could cause this?

That's the only thing I can thing of.

I've gotten a batch of Litton aircraft-grade steppers and has steppers FROM THE SAME BATCH wired differently.

I haven't thought about it deeply, but would a motor turn the other direction if they inserted the stator pack in the other-way-up in the casing? That's all I can think of.

@budspencer I did this yesterday and didn't work, this it went perfect, thanks mate!

@peirof The 4 pin Fan ports also support 2 wire Fans.( see [https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mini_5+_Hardware_Overview]
the cooling pads of the driver are on the backside of the PCB..so best would be if the cooling air comes from the side.
In my Voron i used this solution:

M950 F5 C"out5" Q100 ; Creates Case Fan 1 M106 P5 T40 L0.4 X0.4 H3 ; Case Fan 1 Settings (Turns on at 40°C tool temp) at low speed M950 F6 C"out6" Q100 ; Creates Case Fan 2 M106 P6 T40 L0.4 X0.4 H3 ; Case Fan 2 Settings (Turns on at 40°C tool temp) at low speed and hooked them up to the MCU Temp M308 S3 A"MCU" Y"mcu-temp"

Others connected the fans to the hotend tempsensor...so if you start to print it starts to cool the board

@resam
Worked a treat, thx! 😃

@phaedrux I should clarify in case its misleading for anyone in the future.

The original DuetPi image was downloaded from the official GitHub location as was the last install which appeared to solve my problem.

I think I must have bodged the HDMI screen installation tbh. I ran some install command but really it just needed to be configured in config.txt.

All seems to be working now. I've since upgraded to the 3.4 RC and I've successfully tested motion on the stepper motors.

Thanks again.

Jason

@phaedrux just sent it. Any news if the replacement from the US will work?

@peirof it's difficult to recommendation settings without having a resistance vs temperature table for that thermistor.

If it's for a bed heater then you can use R100000 B3950 C0 and get reasonable temperature accuracy up to at least 100C.

If it's for a hot end heater then you really need to do better. Preferably, get a resistance-temperature table for that thermistor from the supplier of the thermistor.

@randyl00123 said in We need a verbose mode for general troubleshooting:

@gloomyandy One thing I have always found confusing about the gcode explanations is the inconsistancy of definitions. For example, in M111, Pnn is the module number. What is a "module", how did it recieve a number, and what does that "number"refer to?

Send M111 and it will list all the module numbers.