Unable to read tmc uart ‘step.... PART2

General Discussion
1

Basic Information:

Printer Model: Vcore 31
MCU / Printerboard: Octopus Max Ez
Host / SBC rPi4
klippy.log
klippy01.log (24.9 KB)
klippy02.log (177.1 KB)
klippy03.log (843.8 KB)

I’m back. It’s not that my problems have been solved, it’s that after running the tests suggested in my previous post and seeing that they didn’t work… I took the middle road and switched to an Octopus MAX Ez, which has a new type of driver…

But after the work of replacing the motherboard and reconfiguring the printer…

SAME ERROR AS BEFORE.

I put here the link of the previous post, so you can see the tests done previously.
Unable to read tmc uart ‘stepper_y’ register IFCNT

This time I’m attaching three logs, so you can see the progress.

  • Klippy01.log, corresponds to an initial stage, just turning on the bed and extruder heaters.

  • Klippy02.log, I rebooted and tried to move the printer on the X axis… and the error occurred. You can see that in log klippy02.log The error is the same as the last time on the same axis: “Unable to read tmc uart ‘stepper_x’ register IFCNT”

  • Klippy03.log, I rebooted and tried again, changing a few things to test. Basically, I moved the TMC 2209 configuration from a file with an include command to the main file.

But the error is the same. I also thought this error could be caused by a damaged motor or cable. I disconnected them from the board, and nothing, same error.

Another test I did was disconnect the CanBoard and configure everything on the MCU, but THE SAME ERROR.

I honestly don’t know what to try… as I said, I changed the MCU and reinstalled Klipper and Fluidd. But the same error persists.
I ask you for help please…

The logical question would be… why did you open a new post instead of continuing with the previous one? The answer is that I changed the MCU and the logs are now clean.

I have looked in many places and have done many tests… but I CAN’T find the problem, no matter how many things I try.
I’m sorry if I’m annoying, and I apologize, but I don’t know what else to do or what to try.

Thx in advance

2

Sorry to hear about your troubles.

Could you provide:

  1. A wiring diagram showing how things are wired in your printer. I asked for this in the previous discussion but it was never provided.

  2. The steps taken to set up your Raspberry Pi and Flash the firmware into the MCU.

3

Add some info… the results of DUMP_TMC

FIRST Extruder THAT WORKS, its in Canboard

 DUMP_TMC STEPPER=extruder

8:05:44 
// ========== Write-only registers ==========
18:05:44 
// SLAVECONF:  00000200 senddelay=2
18:05:44 
// IHOLD_IRUN: 00081616 ihold=22 irun=22 iholddelay=8
18:05:44 
// TPWMTHRS:   000fffff tpwmthrs=1048575
18:05:44 
// TCOOLTHRS:  00000000
18:05:44 
// COOLCONF:   00000000
18:05:44 
// TPOWERDOWN: 00000014 tpowerdown=20
18:05:44 
// SGTHRS:     00000000
18:05:44 
// ========== Queried registers ==========
18:05:44 
// GCONF:      000001c0 pdn_disable=1 mstep_reg_select=1 multistep_filt=1
18:05:44 
// GSTAT:      00000000
18:05:44 
// IFCNT:      0000006f ifcnt=111
18:05:44 
// OTP_READ:   0000000e otp_fclktrim=14
18:05:44 
// IOIN:       21000041 enn=1 pdn_uart=1 version=0x21
18:05:44 
// FACTORY_CONF: 0000000e fclktrim=14
18:05:44 
// TSTEP:      000fffff tstep=1048575
18:05:44 
// MSCNT:      000001a8 mscnt=424
18:05:44 
// MSCURACT:   012b007e cur_a=126 cur_b=-213
18:05:44 
// CHOPCONF:   24030053 toff=3 hstrt=5 tbl=2 vsense=1 mres=4(16usteps) dedge=1
18:05:44 
// DRV_STATUS: 80160000 cs_actual=22 stst=1
18:05:44 
// PWMCONF:    c80d0e24 pwm_ofs=36 pwm_grad=14 pwm_freq=1 pwm_autoscale=1 pwm_autograd=1 pwm_reg=8 pwm_lim=12
18:05:44 
// PWM_SCALE:  00000019 pwm_scale_sum=25
18:05:44 
// PWM_AUTO:   000e0024 pwm_ofs_auto=36 pwm_grad_auto=14
18:05:44 
// SG_RESULT:  00000010 sg_result=16

and now Stepper X, that NOT WORK

Without restart after error

DUMP_TMC STEPPER=stepper_x

Unable to read tmc uart 'stepper_x' register IFCNT Once the underlying issue is corrected, use the "FIRMWARE_RESTART" command to reset the firmware, reload the config, and restart the host software. Printer is shutdown

After restarting printer

DUMP_TMC STEPPER=stepper_x
 
// ========== Write-only registers ==========
18:09:12 
// SLAVECONF:  00000200 senddelay=2
18:09:12 
// IHOLD_IRUN: 00081313 ihold=19 irun=19 iholddelay=8
18:09:12 
// TPWMTHRS:   00001250 tpwmthrs=4688
18:09:12 
// TCOOLTHRS:  00000000
18:09:12 
// COOLCONF:   00000000
18:09:12 
// TPOWERDOWN: 00000014 tpowerdown=20
18:09:12 
// SGTHRS:     00000000
18:09:12 
// ========== Queried registers ==========
18:09:12 
!! Unable to read tmc uart 'stepper_x' register GCONF
4

Not what I’m asking for.

1 Like
5

Sorry, I didn’t pass it on to you, because I thought changing the MCU would solve my problems, but no…

I’m attaching the photos.

One thing I do believe is that if changing the MCU persists, the problems may persist… it’s possibly a Klipper configuration error…

Foto 01
Foto 011920×3413 304 KB

foto 03
foto 031920×3413 496 KB

foto 02
foto 021920×3413 398 KB

6

As far as my understanding goes, the EZ drivers have quite a history of being DOA.

7

To flash Klipper, I followed the manufacturer’s instructions. I’m writing it from memory, so maybe I missed something.

1- I connected to RPi via Telnet.
2- I updated the Klipper repositories.
3- Using Make Menuconfig and the manufacturer’s options, I created the Klipper image.
4- I copied and renamed it firmware.bin to a microSD card.
5- I inserted the microSD card into the Octopus and, with the power supply connected, turned it on.
6- I waited a minute or two, I don’t remember, and checked that the file that was previously called firmware.bir was now called firmware.cur.
7- I reinserted the microSD card into the Octopus.
8- To verify that it was working, I connected to RPi via Telnet and sent an LSUSB, where I saw that the name had changed to something long with “…klippy…” in it.

8

what is DOA?

In my tests, one of the ones I’ve done has been:

1- With the drivers installed and the motors wired, move the printer. The result is the aforementioned error.
2- In case the error was caused by a motor or the wiring, the second test was to disconnect the motors from the motherboard, but leave the drivers on, and move the printer. The result was the same error.

And the last test:

3- In case the fault was with the drivers, try removing them from the motherboard and instructing the motors to move. The result is the same error.

This makes me think it’s not a hardware failure, since it produced the same error with the Octopus Pro, and it produces the same error with and without drivers…

9

DOA = Dead On Arrival

We have put together a comprehensive article on this error. Unfortunately, a lot of individual factors contribute to this issue. See Unable to read tmc uart 'stepper' register IFCNT

It is practically absolutely certain that it is a hardware issue local to your installation. If not, this and other places dealing with Klipper would have been flooded with reports about it.

This is to be expected. If you remove the driver, with what should Klipper communicate?

1 Like
10

Yes… I’ll go over it all again tomorrow, I’m sure it’s some nonsense that I’ve overlooked, and I’m boring you all…