When Homing, Not traveling Correct Distance 3.3 beta1

Toastinator

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta4.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-12-02

Downloaded and uploaded Duet2and3Firmware-3.2.2.zip, Ran M997 and I get this Error, There is a file Similar in the Zip Named "Duet3_SDiap32_MB6HC.bin". I Tried Renaming The File to what its looking for, and it canceled automatically.

Error: M997: In-application programming binary "Duet3_SDiap_MB6HC.bin" not found

@fcwilt
Changing those now, Thanks

I Double Checked the Pulley's and they are Indeed 20 Tooth 8mm Bore 2GT 6mm Belt

After These changes I Did Another Test. It is still doing the same thing.

I Have Noticed that this Works:

G1 X130
G1 Y195

But This Does not Work:

G1 X130 Y195

What would Cause this?
All Boards Updated to 3.2.2 EXCEPT the Main Duet3 MB6HC

Veti

@Toastinator said in When Homing, Not traveling Correct Distance:

". I Tried Renaming The File to what its looking for, and it canceled automatically.

dont just rename files

https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet3iap_sd_MB6HC.bin

Toastinator

@Veti

That File name is Incorrect Aswell.
Duet3iap_sd_MB6HC.bin

Its Looking for Duet3_SDiap_MB6HC.bin. Thanks I Really Appreciate the Help.
The Github has Duet3_SDiap32_MB6HC.bin

The GitHub Said all you need to do is download Duet2and3Firmware-3.2.2.zip And it Auto Runs the Firmware Update. Except it Seams to be Missing the File. Not Sure why it has the Same File name but an additional "32" in the name

Veti

@Toastinator said in When Homing, Not traveling Correct Distance:

Duet3_SDiap_MB6HC.bin

sorry linked the wrong file from the 3.0 release

https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet3_SDiap_MB6HC.bin

Toastinator

@Veti

Thanks! I was just Searching and Found the same file on a 3.1.1 Release.

Somehow, It seams to be working Now. This was a Firmware Issue with the Duet 3 Expansion 1XD Boards?

When will the duet start looking for Duet3_SDiap32_MB6HC.bin Files?

Veti

@Toastinator said in When Homing, Not traveling Correct Distance:

When will the duet start looking for Duet3_SDiap32_MB6HC.bin Files?

for firmware update from 3.2

Toastinator

@Veti The Github should say Update to 3.2 First, Then to the Newest. The Small Details lol

Toastinator

@Veti

After Further Testing, It still Does the Same thing, But Not Every Time. If you have any other ideas

Toastinator

Combined Movement on this CoreXY Duet 3 Expansion 1XD Boards Driving Nema 23 Closed Loop Stepper Motors Seem to be the Issue.
This is Fine:

G1 X100
G1 Y100

This Does not work:

G1 X100 Y100

dc42

In what way doesn't that command work- what does it do?

Toastinator

@dc42

Firmware 3.2.2: G1 X100 Y100 Moves about Half X and Y. While Printing, It Layer Shifts Continuously on the same Layer.

But This Works Fine For some reason:

G1 X100
G1 Y100

Firmware 3.3Beta1 The Machine Refuses to Home. It wont Recognize X or Y on the Expansion 1XD Boards. (Both 1XD Boards were also Upgraded to 3.3Beta1)

Toastinator

In the Image, The Printer is Continuously Layer Shifting Mid Layer In a Diagonal Fashion. These are Nema 23 Closed Loop Stepper Motors, Driven from 2 Duet 3 Expansion 1XD Boards for X and Y On a CoreXY Machine. Have to Use 3.2.2 Firmware Because 3.3Beta1 Will Not Home.

dc42

@Toastinator said in When Homing, Not traveling Correct Distance 3.3 beta1:

In the Image, The Printer is Continuously Layer Shifting Mid Layer In a Diagonal Fashion. These are Nema 23 Closed Loop Stepper Motors, Driven from 2 Duet 3 Expansion 1XD Boards for X and Y On a CoreXY Machine. Have to Use 3.2.2 Firmware Because 3.3Beta1 Will Not Home.

Layer shifts when using external drivers are a sign that the M569 T parameters are not right. Don't just guess, get the specifications for minimum step time, minimum step interval, minimum direction-to-step setup time, and minimum direction-to-step hold time needed by the drivers.

I'll reply regarding the homing issue in your other thread.

Veti

@Toastinator said in When Homing, Not traveling Correct Distance 3.3 beta1:

T0:0:0:0

that sound wrong for timing

Toastinator

@Veti

I took it right from the Wiki Page.

"b This is setting T0:0:0:0 this allows the firmware to generate short pulses. in measurement these where no shorter than 0.7ns."

But I also Tried Removing it aswell, Leaving the Default.
"On the EXP1XD board the default is T2.6:2.6:2.6:2.6"

When I get home later tonight, Ill play around with Timing and see what happens.

jay_s_uk

@Toastinator you need to look at the datasheet for your drivers to determine the timing required. I suspect it will be higher than the 1XD defaults as well

Toastinator

@jay_s_uk

The Datasheet I was given does not Mention any Required Timing. It just says it accepts from 0-200Khz Pulse Frequency.

JSS57P2N Instruction manual

After Changing Timing to T5:5:5:5 and T10:10:10:10, It Seams to Move Fine, But there is Some Type Of error Accumulating. (Or somthing else, lol)

Yesterday, I was Getting Homing Errors. Today Without Changing Anything, Its Homing Fine, But Not waiting for the Hotend to Heatup before Moving. And Look at this Picture of a No Infill Cube. The Infill Filled in Slightly Wavy at the Bottom.