Tmc connection error marlin

Comments

collect2: error: ld returned 1 exit status
*** [.pio/build/BIGTREE SKR MINI/firmware.elf] Error 1

Send: M122
Recv: 		X	Y	Z	E
Recv: Enabled		true	true	true	false
Recv: Set current	1200	1200	1200	980
Recv: RMS current	1160	1160	1160	939
Recv: MAX current	1636	1636	1636	1324
Recv: Run current	20/31	20/31	20/31	16/31
Recv: Hold current	10/31	10/31	10/31	8/31
Recv: CS actual	10/31	10/31	10/31	8/31
Recv: PWM scale	24	25	24	10
Recv: vsense		0=.325	0=.325	0=.325	0=.325
Recv: stealthChop	true	true	true	false
Recv: msteps		16	16	16	16
Recv: tstep		max	max	max	max
Recv: pwm
Recv: threshold	49	49	82	31
Recv: [mm/s]		100	100	3	30
Recv: OT prewarn	false	false	false	false
Recv: OT prewarn has
Recv: been triggered	false	false	false	false
Recv: off time	4	4	4	4
Recv: blank time	24	24	24	24
Recv: hysteresis
Recv: -end		2	2	2	2
Recv: -start		1	1	1	1
Recv: Stallguard thrs
Recv: DRVSTATUS	X	Y	Z	E
Recv: stst		*	*	*	*
Recv: olb
Recv: ola
Recv: s2gb
Recv: s2ga
Recv: otpw
Recv: ot
Recv: 157C
Recv: 150C
Recv: 143C
Recv: 120C
Recv: s2vsa
Recv: s2vsb
Recv: Driver registers:
Recv: 		X	0xC0:0A:00:00
Recv: 		Y	0xC0:0A:00:00
Recv: 		Z	0xC0:0A:00:00
Recv: 		E	0x80:08:00:00
Recv: 
Recv: 
Recv: Testing X connection... OK
Recv: Testing Y connection... OK
Recv: Testing Z connection... OK
Recv: Testing E connection... OK
Recv: ok P63 B31

Комментарии к статье

tmc2208 v3.0 + skr 1.3 «tmc connection error» мое решение

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Купил у bigtreetech плату и драйвера.

Драйвера «DYI» для подключения по UART.

При установке с marlin 2.0 прошивка выдавала ошибку «tmc connection error».

Нигде не нашел дельного ответа, кто-то меняет драйвера, кто-то добавляет какие-то строки в прошивку.

Я же решил проверить сначала железо. С платой все отлично.

А вот с драйверами вышла накладка. Смотрим даташит на камень:

Проверяем схему драйвера:

Тут явно видно лишний резистор.

Запаяв перемычку J2 согласно инструкции и выпаяв резистор R1 все заработало.

Подпишитесь на автора

Подпишитесь на автора, если вам нравятся его публикации. Тогда вы будете получать уведомления о его новых статьях.

Отписаться от уведомлений вы всегда сможете в профиле автора.

Источник

[BUG] SKR 2: TMC connection error if DISABLE_DRIVER_SAFE_POWER_PROTECT commented-out (i.e. protection is enabled) #22701

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

In Configuration_adv.h , one finds this section:

This is the normal state. But, it also keeps TMC drivers from working at all.

At first I couldn’t figure out why, then I looked at the SKR 2 schematic today (my board is a Rev. B and matches it):

_{MOT_POWER is the control line from the µC, PGND is the power supply ground rail.}

Clearly, the driver power control MOSFET Q1 cuts the ground connection to the motor drivers when it’s turned off. I mean, ALL of the driver modules’ ground circuits, the lot of them, and not just whatever’s needed for motor power (though I’m not sure if a TMC chip «splits» its grounding in this fashion, not that it matters)

No ground to the driver means unreliable UART comms, which means TMC connection errors (UART generally requires both +V and ground) or gibberish data being fed to the drivers.

It also means trying to turn a motor on can start to BURN UP the chip! I’m guessing here that the motor drive circuitry is trying to pull a ground reference through the rest of the driver chip from somewhere else inside it other than its primary ground rail. I am 100% certain that this is what killed three of my TMC2208 drivers.

In my not so humble opinion, this is a major hardware design flaw. However, that’s out of Marlin’s hands.

If I uncomment that line, the drivers work, UART works, etc., presumably because the ground connection is turned on by default in this case. However, my TMC2208’s then can’t be disabled — idle timeout and M84 do nothing on them (my two A4988’s do turn off, however). I’m not sure why that is, but Marlin’s doing it, as they start out turned off, and only turn on when Marlin finishes its boot logo animation.

Marlin appears to be calling upon the TMCstepper code until before it does its anti-SNAFU checks and has turned the power control circuit on.

So, don’t try to query the drivers, and definitely do not allow any STEP/DIR/EN output to a driver that doesn’t report all good, until after the anti-SNAFU code is happy and the Q1 power control circuit has been turned on, and thus chip has a valid ground reference.

If that means that some user can’t print anymore because some other issue makes their drivers throw UART errors (that they’ve perhaps been ignoring), then so be it. They need to fix their hardware. If they’re in a hurry, they could of course put those axes into A4988 or standalone mode.

Bug Timeline

Unknown timeline, but new to me since I’m working with new hardware.

Expected behavior

As described above.

Actual behavior

Bad UART comms causing TMC connection errors, high risk of driver burn-out.

Источник

TMC2208 [TMC CONNECTION ERROR] #17

I configured marlin and SKR1.3 to work in uart mode but i have the same message on the display.
The driver are BIGTREETECH TMC2208 SKU:UUU001758
The board is SKR V1.3, i follow the instruction here: https://www.youtube.com/watch?v=oaXfXkPYHpw
But i have the same message on display.

Attached a photo of my driver.

Here is the output of my M122:
X Y Z E Enabled false false false false Set current 800 800 800 800 RMS current 1436 1436 1436 1436 MAX current 2025 2025 2025 2025 Run current 25/31 25/31 25/31 25/31 Hold current 12/31 12/31 12/31 12/31 CS actual 0/31 0/31 0/31 0/31 PWM scale 0 0 0 0 vsense 0=.325 0=.325 0=.325 0=.325 stealthChop false false false false msteps 256 256 256 256 tstep 0 0 0 0 pwm threshold 0 0 0 0 [mm/s] — — — — OT prewarn false false false false off time 0 0 0 0 blank time 16 16 16 16 hysteresis -end -3 -3 -3 -3 -start 1 1 1 1 Stallguard thrs DRVSTATUS X Y Z E stst olb ola s2gb s2ga otpw ot 157C 150C 143C 120C s2vsa s2vsb Driver registers: X 0x00:00:00:00 Bad response! Y 0x00:00:00:00 Bad response! Z 0x00:00:00:00 Bad response! E 0x00:00:00:00 Bad response! Testing X connection. Error: All LOW Testing Y connection. Error: All LOW Testing Z connection. Error: All LOW Testing E connection. Error: All LOW ok

The text was updated successfully, but these errors were encountered:

Have you solder bridged the option pads on the TMC2208 driver boards to connect the UART pin on the TMC2208 to the UART driver board pin ?

I made no solder, I place jumpers in the board and attached these drivers.
I have no idea of what to solder/connect

Try soldering these two little pads together on each of your TMC2208 driver boards ..

I asked also to the supplier, and he give me that image as reference for soldering two pins.
Are the same or i am confused?

oh ok, go with what they say. If that doesn’t work try the other two pads.

Nope, i soldered these pads but the trouble still remain.
And now its difficoult for me de-solder and solder the other two pads.
Do you think i could solder every three pads?
I send photos, please tell me if you see something wrong.

You soldered the pads BigTreeTech said to solder. Try soldering the pads I showed you instead.

You need to apply 12 or 24v for it to work

I have the same issue
the jumper on the driver is soldered and works properly with FTDI serial to USB
but not on skr 1.3 board powered by USB or 12v from power supply

Hi, i’ve soldered the pads together (because i have not good skill) and now it works!
Thanks to all of you!

Источник

[BUG] [Bugfix 2.0.x] TMC Connection Error when using TMC2208 with DUE. #15821

Description

Trying to test TMC2208 with DUE and I’m getting TMC Connection Error.
The TMC2208 drivers are good for sure as they work standalone, and I can connect to them via serial using a ftdi adapter + Script Communicator. If I move the rx/tx lines from the ftdi board to the DUE I get the connection error message on the display.
I tried with two different TMC2208, and I also tried using any serial1/serial2/serial3 ports but nothing.
The serial ports are working for sure as I tested with the serial console.

M122 reports this:

I have the resistor between RX/TX lines.

The text was updated successfully, but these errors were encountered:

Can anyone else with a DUE and TMC2208 confirm this?

@bob808 i assume this is still an issue?

Yes, at least for me.

This is what’s on RX/TX when talking to tmc2208 via ftdi with scriptcommunicator:

And this is what’s on RX/TX when DUE is trying to talk to tmc2208:

@bob808, those look so different because the top picture is a read, and the bottom picture is a write.

Try capturing while executing an M122 command, to capture some reads through Marlin.

Here’s how it looks when issuing M122 X

The two consecutive commands are constant retries to the tmc2208, they happen constantly. In the middle is the M122 command.
This is the first info in the M122 command:

@sjasonsmith do the new captures make any bells ring?

I just realized that the bottom picture shows a slave address of 1 being sent, when for a 2208 this should always be zero. The CRC is correct for those bytes, which tells me that address was intentionally sent, and this isn’t just a timing error.

My first guess was that Marlin was misconfigured for a TMC2209 with a slave address set, but that is not the case according to the posted configs.

@bob808, are you sure the configs you posted are what you are currently running?

Can you also make sure you are using the latest version of bugfix-2.0.x? If Marlin or TMCStepper is actually causing a slave address to be added that is not in your configuration file, this issue would be much more widespread.

I’ll try again, I did tinker with the settings since and I want to test again fresh, just to make sure.

I used a fresh version from a couple of days ago, only modified Configuration.h, Configuration_adv.h and the pins file, all added in the archive.
config.zip

Still doesn’t work, TMC connection error on display, serial says:
Testing X connection. Error: All LOW
And logic analyzer shows this as the first command after issuing M122 X

Also just to make sure I removed the cables from the DUE and I inserted them into the FTDI just the same as into the DUE, and used scriptcommunicator and could read the tmc2208.

OK, that looks better, it has a ‘0’ for the slave address, as it should.

Where are your probes attached? Their position relative to any resistor(s) in the line is important.

Where is the resistor attached? There should be a resistor between the TMC UART pin and your TX pin. There should be a direct connection between the TMC UART pin and the RX pin (no resistor).

When I see a valid read command going out with no response, it makes me think that the resistor is connected to RX instead of TX.

Also, can you verify that you are powering your stepper drivers? If you are only powering with USB they will not respond.

Right now it seems like a possible wiring problem. This is what I would expect to see if the resistor it attached to the RX pin instead of the TX pin.

I don’t have HV, I feed it 5V, and seems to be able to talk with scriptcommunicator. But I can add the required higher voltage.
I have a 1K resistor between RX/TX.
Ah, ok, had RX/TX swapped. Just noticed, I wanted to be sure it’s ok before finishing my reply 🙂
Thank you for your help!
I think I tried swapping RX/TX before but apparently it was that extra bit that was messing things up then.

Glad to hear it worked! I have a Due here, but I don’t have a shield I can actually use with it, so I wasn’t able to try it myself!

I finished designing mine and apparently everything should work.
I have 3xUART capable driver slots (hardware UART), all 5 capable of SPI. One with UART has two connectors for motors, for Z axis.
8 thermistor inputs, one max31865 sensor.
6 PWM fans, 3 of which can be powered by 24V/12V/5V
2 servos and one bltouch connector
3 endstops
two extruder heater connections, car fuses for VMOT/extruders/bed. poly fuses for lower current rails. bigger mosfets are properly driven, most comms are also buffered, and I managed to get it pretty decent on two layers:

Everything should work. I’ll see when I get it.
Oh, and I’m using two of those small dc/dc converters for 12V/5V to servo. If they burn I can just replace them. But they should be fine.
Also put an esp8266 socket for when some code for spi gets out. I can still use it on rx/tx as it is but the file transfer is slow af. Added the SPI connection to SD for future code.

@bob808 nice looking board are the files for that published anywhere? i assume its a shield for a due

i tried to make a Ramps-FD v2.2 but i gave up on it as it was to expensive and to much surface mount

not yet.
I tried remaking a ramps-fd but I figured I should start from scratch since I have a different configuration.
Basically all pins are used/broken out or both. I think there’s one pin left (for filament runout sensor) if using software SPI for tmc drivers/max31865. I have a jumpered setup for that. if using hardware then there’s 3 extra pins left.
there’s also a precise voltage reference for the analog stuff, and I tried to keep it somewhat isolated. I don’t know how much that matters, hope I find the time to take a look at the performance between with and stock.
ground looks like this:

there are a few unconnected tracks that show but I was lazy in correctly labeling the different 5V supplies etc.
being 2 layers and 100mmX100mm it’s pretty cheap to make. and the surface mount stuff is not that hard to solder. I’ve used 0805 smallest parts.
edit: yes, it’s for DUE.
as cost I think the max31865 chip is the most expensive. there’s 3x hc125 buffers, 1x74HC02 for properly driving the extruder/bed mosfets, and the extruder/bed mosfets should have a low rds on.
used AOD240 for bed (for 220W bed at 24V that is 9A and a bit, and mosfet would generate about 0.3W heat) and AO4430 for extruders (for a 2.5A heater, mosfet generated heat is irrelevant).
voltage reference could drive up cost depending on precision.
there’s also an eeprom, with footprints for both dip and sop footprints
both sevos + data to bltouch + display data line are buffered with a hc125 powered by 5V.
display encoder is translated with resistors, to 3.3V, so I can use the stock ender 3 display on 5V.
the other two display lines are driven at 3.3V, and the whole display works on 3.3V anyways so shouldn’t be a problem.
z-probe stop is buffered to 3.3V, mosi/sck for tmc spi is buffered, and the whole SD SPI is also buffered. so comms should work.
also max31865 is 2/3/4 wires selectable. I only got a two wire atm but wanted to have the option of using a four wires variant later on.
for the two buck converters I’m using these things:

they cost around 1$ and they can be set for either any of the fixed voltages on the back, either can be adjusted with a small pot on the top side. they brag about being 3A output capable, but I wouldn’t trust them for more than 1A. they also have an enable pin. and they are 24V input capable. pretty small as well.
one is for 5V needed for servo and bltouch and the optional 3 fans. the other is a 12V one powering (if wanted) the three fans, and permanently supplying VIN to the DUE. If needed, this one can be set to anything between 12V (max supply for VIN on DUE) and 6V or so, using it’s adjusting pot. This way there’s nothing I can’t pwm on the three fan headers (voltage wise).

I am really curious if I will be able to directly control a lower powered 405nm laser diode with the 5V regulator. I won’t be needing bltouch or any servo so I can adjust that converter to something comfortable for a 100mA laser diode. I got one that’s rated for 190mA or so, running it at 100mA would be more than enough for presensitized pcb work. as it happens this diode runs at about 5V for 100mA. sure there might be some drift but there’s plenty room both ways for presensitized pcb. I’d be practically using my fun 405nm pointer for this.

Источник