Advanced Search

Pushed a change to Master to use 64 bit integers for hm2 quadrature
encoder count values rather than 32 bit, Seems to work as expected.
(32 bit ints cause a wrap at  a count of 2147483648)

(looped back a stepgen at 30 M counts/sec to the encoder
input to test, still took a while...)

Hmm ok that confirms it. I did most of my octopus functionality testing on the octopus v1.1, I didnt like the buzzer on the pro. The octopus PRO has level shifters on the UART lines. When I jumper the TMC UART line to another pin, it configures fine. That is the only thing I can think of. But this overlaps with another issue Im having with another board, that also has a level shifting circuit on the UART line.

Scott, if you can provide input/assistance on this issue, it would be appreciated.

Im trying to support this mellow flyCDY3 board, but the uart isnt working. I tried changing the baudrate, but no luck. Thankfully my buddy mdroberts is much smarter than me, so he collected some data for me on the issue.

It looks like i cant upload the excel file he made, but here is what he said

Further to the TMC2209 read-back. I used the scope UART decode feature to confirm that the programmed values sent to the TMC2209 seem reasonable and consistent with the registers, but the TMC2209 doesn't put any data out after a register read is requested. The sequence after resetting the board is provided in the attached.

I just don't see any output from the 2209 when a register read is done.

You should remove the e-mail, spam incoming

Looks like Francisco got it.

Rob

Who's the lucky winner?

I've just implemented this for myself.

I already have autoprobe routines that set g54 parameters for X, Y, and Z. I augmented my autoprobe functions to log the x and y values of every completed probe, along with the g54 offsets in effect at the time.

When I have a rotated part, I touch it twice, along a surface that's parallel to its twisted X axis. That gives me two new log entries. I have a script that reads those entries, and calculates d = atan ( (y2 - y1) / (x2 - x1) ), after correcting the x and y values with the offset information.

The script prints the result in degrees. In fact, the script simply prints the necessary g-code: "G10 L2 P0 R $angle", which I then pasted into the MDI window.

andypugh wrote:

And it's true, I think. For example we really could so with a section on toolchangers. 

And Ethercat now it can be installed without breaching licenses
And how to optimise later distributions