“Unable to write tmc spi ‘stepper_x’ register GLOBALSCALER”

[jan0ni]

 

Basic Information:

 Printer Model: Mellow VzBot 330
 MCU / Printerboard: STM32H723ZGT6
 

I have built my Mellow Vzbot 330 printer following the manual given on the website, now I reached the point to turn it on for the first time, when I try to click home, the klipper shuts down giving the error “Unable to write tmc spi ‘stepper_x’ register GLOBALSCALER”. Solution that I have tried is to maybe find the faulty driver, but I don’t know exactly how to do it, what I basically did was disconnect are the drivers and connect them one by one to see which one is faulty but it still gives me same error in every case even when there are no drivers connected to the main board.

 

Thanks in Advance for helping

 

 

printer (2).cfg klippy (1).log

[mvdveer]

In my experience with my VZBot, this was due to a power problem.  Do you have the high powered TMC5160 (35 - 48V or V2 which is 60V). Make sure you have set the settings on your drivers to SPI:

Then look at the power connectors. See this thread and take head of @Penatr8tor's advice on power connections on the Fly Super 8:

Quote

I would double / triple check the power wiring. On the Super 8 pro you need to connect all of the power connections along the bottom of the board like mine. You also need to have a common neutral wire running between both power supplies and watch out for the bed power on the left, the polarity is opposite of all the others. I had an issue where my steppers wouldn't buzz and I went back over my wiring and yup, forgot to tie the two PSU's together with a neutral wire.

 

 

[Glengus]

Very common problem but hard to find the solution. I battled it for ages, solution was in the stepper section of the printer.cfg . When I get home I'll grab mine and send it through if you like?

[Glengus]

Please ignore this, was just trying to help

 

I see your spi_bus line is commented out, tmc5160's need spi. See mine below, obviously I've named my pins differently and am using bus 0a instead of 1a on yours. I think if you just remove the # from the 4 spi_bus: lines you'll be on the right track. Mine uses = instead of : but you should probably stick to :

[tmc5160 stepper_x]
spi_bus = spi0a
cs_pin = pitb:MOT1_CS
diag0_pin = ^!pitb:ENDSTOP_X
run_current = 1
hold_current = 1
sense_resistor = 0.075
driver_sgt: 1

[tmc5160 stepper_y]
spi_bus = spi0a
cs_pin = pitb:MOT2_CS
diag0_pin = ^!pitb:ENDSTOP_Y
run_current = 1
hold_current = 1
sense_resistor = 0.075
driver_sgt: 1

Edited October 19 by Glengus
4 drivers rather than 2

[mvdveer]

13 hours ago, Glengus said:

I see your spi_bus line is commented out, tmc5160's need spi.

As it should be for software configuration of the SPI bus.

He has the SPI software configuration, like I have. Yours is the hardware config option.

This is my config on a fully functional VZBot AWD. Steppers X1, Y and Y1 have similar configs. You can see the spi_bus is commented out, as I use software SPI configuration like @jan0ni:

[tmc5160 stepper_x] 
#spi_bus: spi1
cs_pin: PC4
#diag_pin: PA8
interpolate: false
run_current: 1.9
sense_resistor: 0.033
spi_software_mosi_pin: PA7
spi_software_miso_pin: PA6
spi_software_sclk_pin: PA5
#driver_SGT: -64 # -64 is most sensitive value, 63 is least sensitive
driver_TBL: 1
driver_TOFF: 3
driver_DISS2G: 1
driver_DISS2VS: 1
#stealthchop_threshold: 0

As per my previous post, I still think power to the drives is the issue.

[Penatr8tor]

On 10/19/2024 at 3:31 PM, mvdveer said:

This is my config on a fully functional VZBot AWD. Steppers X1, Y and Y1 have similar configs. You can see the spi_bus is commented out, as I use software SPI configuration like @jan0ni:

Mine is also using software SPI 

[mvdveer]

On 10/19/2024 at 6:17 PM, Glengus said:

Please ignore this, was just trying to help

All help is valid - the hardware config is a valid option. We learn through responses from others and your response made me go back and look at the SPI bus configurations again. (So I learned) Sorry if I offended with my reply, I realise I sometimes come across quite harsh, but it was not intended to upset anyone and make them withdraw their post.

Keep helping please.

[Glengus]

53 minutes ago, mvdveer said:

All help is valid - the hardware config is a valid option. We learn through responses from others and your response made me go back and look at the SPI bus configurations again. (So I learned) Sorry if I offended with my reply, I realise I sometimes come across quite harsh, but it was not intended to upset anyone and make them withdraw their post.

Keep helping please.

No offence taken. If these posts come up in searches it will be great for others. I couldn't get the software way to work on my fsyetc PITB V1 but eventually found this config worked for me. A different use case but still spi. I've been considering changing all my steppers to 48v tmc5160 so will likely be back here scratching my head soon!

[jan0ni]

Hi everybody,

Thank you so much for the responses and sorry for my late reply. I'm currently powering my Drivers with 48V, but still facing the issue. And when I try to uncomment spi_bus it gives me this error (see picture 1 & 2).

 

Pic 1

 

 

Pic 2

[Penatr8tor]

@jan0ni Looks like you need to comment out the spi_bus: spi1A line.

Below is mine

[jan0ni]

@Penatr8tor Yup, that just brings me back to the first problem that I began with: 

[Glengus]

41 minutes ago, jan0ni said:

Hi everybody,

Thank you so much for the responses and sorry for my late reply. I'm currently powering my Drivers with 48V, but still facing the issue. And when I try to uncomment spi_bus it gives me this error (see picture 1 & 2).

Pic 1

Pic 2

Sorry, I was leading you in another direction with the uncommenting spi_bus: , probably best to stick to the advice others are giving.

[Penatr8tor]

4 minutes ago, jan0ni said:

@Penatr8tor Yup, that just brings me back to the first problem that I began with: 

Welp... At least your checking off boxes.

[jan0ni]

@Glengus No worries, any input is welcomed and as @Penatr8tor said atleast checks off some boxes.

 

[Penatr8tor]

So, I did some searching around the interwebs and it seems to be one of two issues. Either a faulty driver board or power supply related.

@jan0ni 

Have you measured the power at the driver board? 

Have you disconnected the "X" driver board and tried powering up to test is the "X" 5160 driver board is good or not.

[jan0ni]

Right now I took out UART based driver tmc 2209 and connected them and now I recieve this error: 

[jan0ni]

Oh yes, I have tried by taking out X driver out, but it gives the same error. By measuring Power? you mean, using a Multimeter to see if the power is coming at the pins of the driver? But, that does not make real sense because as soon as I click the HOME key, it just prompts me with error and klipper shuts down. Just saying, btw I'll try now something with multimeter to understand what's happening.

15 minutes ago, Penatr8tor said:

So, I did some searching around the interwebs and it seems to be one of two issues. Either a faulty driver board or power supply related.

@jan0ni 

Have you measured the power at the driver board? 

Have you disconnected the "X" driver board and tried powering up to test is the "X" 5160 driver board is good or not.

 

Edited October 22 by jan0ni
Wrong Understood

[Glengus]

13 minutes ago, jan0ni said:

Right now I took out UART based driver tmc 2209 and connected them and now I recieve this error: 

Hmm, so you went to tmc2209's and compatible printer.cfg and got this? Is that what you mean? Did you change any jumpers? Can I assume only 24v now?

[jan0ni]

@Glengus Yes, 24V with compatible printer.cfg. And, I also changed the jumpers on my board compatible to UART.

 

printer (3).cfg

Edited October 22 by jan0ni

[Glengus]

Casting a quick eye over that i don't see anything obvious. I trust you've triple checked the pin definitions against a source document for your exact board? Sorry I don't have a way forward!

[jan0ni]

Yup! I have, gonna do it one time again. But, I guess there is something wrong with the board because I changed a complete set of motors and drivers with SPI and UART and it just keep giving the error.

[Glengus]

3 minutes ago, jan0ni said:

Yup! I have, gonna do it one time again. But, I guess there is something wrong with the board because I changed a complete set of motors and drivers with SPI and UART and it just keep giving the error.

Any chance you can borrow a spare? Worth trying a mcu reflash if you havent already, I did see an alert in one of your pics. Have you tried with the motors unplugged?

[Penatr8tor]

5 minutes ago, jan0ni said:

Yup! I have, gonna do it one time again. But, I guess there is something wrong with the board because I changed a complete set of motors and drivers with SPI and UART and it just keep giving the error.

When you've run out of the obvious stuff to check... it generally ends up meaning that your main board is compromised aka fried.

If it were me, I would double check the firmware and if the problem didn't go away... I would probably be shopping.

Fortunately, a new Fly Super 8 Pro is only about $60 USD so not too hard of a hit.

[Glengus]

I think I've had that IFCNT tmc error when I've mis-slotted or had no driver installed too btw

[jan0ni]

Just now, Glengus said:

I think I've had that IFCNT tmc error when I've mis-slotted or had no driver installed too btw

yes, that's true, even if you take all of them off, it just gives error.