Early RRF 3.3beta files available

dc42

@evomotors, please do the following:

Use M115 to verify that 3.3beta is installed on all the boards
Run M122 B# for the main board and each expansion board to clear the stats
Run a test print that demonstrates the problem
Generate a M122 report from the main board and each expansion board, and post them here. It needs to be the first M122 from each board after running the print. If you don't want to run the entire print, you can pause the print, wait for everything to stop, and then run the M122 reports.

The "steps commanded" and "steps done" figures on the expansion boards should be equal, indicating that every step commanded over the CAN bus has been executed.

dc42

For anyone using this 3.3beta firmware on a EXP1XD board:

We have found and corrected a problem with setting the step pulse width, and updated the EXP1XD firmware at the link I gave at the start of this thread. So please update your EXP1XD boards to this new firmware. The new firmware reports build time 17:18:18 in M122 and M115.

Nuramori

I didn’t see it, so I’d figure I’d ask....does this beta (or a near future 3.3 beta) allow for auto PID tuning with a toolboard?

dc42

@Nuramori said in Early RRF 3.3beta files available:

I didn’t see it, so I’d figure I’d ask....does this beta (or a near future 3.3 beta) allow for auto PID tuning with a toolboard?

Not yet, it's next to be implemented when some remaining issues with expansion boards and high CAN message rates have been fixed.

Nuramori

Are these updatable with AP “apt upgrade” if we’re on the unstable branch?

Phaedrux

@Nuramori said in Early RRF 3.3beta files available:

Are these updatable with AP “apt upgrade” if we’re on the unstable branch?

Considering that it's a dropbox link, probably not available on the unstable package server yet.

aleohl

Will test it out straight away, good job!
I and everyone in my team are very impressed by your swift action in regards to our issues with step pulses. I hope we can figure it out together, both for us and, of course, the community.

Would it make any difference if you had remote access to Atmel ICE kit connected to our devices? If so just send me an email!
Also, do you think it would help us anything if I hook it up and does some trial-and-error to see if I can get more verbose logs or something like that?

aleohl

Great improvements!
Not possible to say by this time if the issue is completely resolved or just great improvement. We will do some more testing.

Thanks @dc42 and team for your great effort and speed!
I try to follow along with the changes in the code base, good way to learn the inner workings.

symekutz

So I'm confused M303 is not implemented but in the changelog it says it is.

[Duet 3 expansion/tool boards] Heater tuning is now implemented (M303) along with heater feedforward

When I try it I get:
Error: M303: remote heater auto tune not implemented

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J1F2-3SN6P-1U6QG
Used output buffers: 1 of 40 (18 max)

m122 b21
Diagnostics for board 21:
Duet TOOL1LC firmware version 3.3beta (2021-01-21 11:34:37)

So I'm a thinking the changelog is ahead of the code?

Let me know if I missed something please.

dc42

Download the official 3.3beta1 release from github.

symekutz

@dc42 It's running now thank you!

dc42

Locking this thread because the early beta files have been superseded by the official 3.3beta1 release on Github.