Error all low

Ответы на вопросы

So I am using the latest bugfix. Drivers are getting plenty of juice. I think I figured it out. When I bought these drivers, I did not know that there were jumpers on the boards. I bought these boards back when they were still fairly new, and had not tried to implement them. The original TMC2130’s did not have jumpers. These are not original and the retailer I got them from provided no info on this. Looking at the same board now has documentation that was not available at the time. Mine came setup for stand alone mode.

Having the old version up is confusing. I think you should just have the latest drivers and latest config file examples because the firmware you have up will not even compile due to its age and the progressment of marlin.

I still do not know if they will work, but I can say the firmware is compiling as expected. It attempts to connect to the TMC2130’s through SPI but the drivers are being jerks right now due to them being in stand alone mode.

I compiled for standard A4988, configured board jumpers to step mode and popped in some A4988 drivers. I did confirm that the board is working well.

Thanks for trying to help. I will use your micro step advise. I’ll reconfigure the stepdrivers, board and firmware tonight and give it a try. I really hope these things work. Let you know.

[BUG] Z connection. Error: All LOW #15939

because of noone can help me i post myproblem here maybe it is a bug.

I have the following hardware:
mks gen l Version 2
tmc2208 V 2

When i connect via ponterface or it is as error in my lcd at after boot there comes an tmc connection error.

In ponterface -> Z connection. Error: All LOW

when i do an an

SENDING:M122
echo:SD init fail
echo:SD init fail
X Y Z E
Enabled false false false false
Set current 800 800 800 800
RMS current 795 795 1436 795
MAX current 1121 1121 2025 1121
Run current 25/31 25/31 25/31 25/31
Hold current 12/31 12/31 12/31 12/31
CS actual 12/31 12/31 0/31 12/31
PWM scale 21 22 0 22
vsense 1=.18 1=.18 0=.325 1=.18
stealthChop true true false true
msteps 16 16 256 16
tstep max max 0 max
pwm
threshold
[mm/s]
OT prewarn false false false false
off time 3 3 0 3
blank time 24 24 16 24
hysteresis
-end -1 -1 -3 -1
-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 0xC0:0C:00:00
Y 0xC0:0C:00:00
Z 0x00:00:00:00 Bad response!
E 0xC0:0C:00:00
Testing X connection. OK
Testing Y connection. OK
Testing Z connection. Error: All LOW
Testing E connection. OK
Disconnected.

You can see that the z stepper weird settings.

With an M906
X driver current: 800
Y driver current: 800
Z driver current: 800
E driver current: 800

I exchange the stepper driver with an working from board that did not solve the problem it is the same.

I set the voltage for xyz to 0,760 and for z at 0,900

Is some on there that can help me ?

Thanks in advance

Description

Steps to Reproduce

Required: Please include a ZIP file containing your Configuration.h and Configuration_adv.h files.

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Additional Information

• Provide pictures or links to videos that clearly demonstrate the issue.
• See How Can I Contribute for additional guidelines.

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

Источник

TMC2208 X connection. Error: All LOW #21

TMC2208 X connection. Error: All LOW

But same Stepper will work in Y,Z or E. So Stepper ok.

X will work with TMC2130 in SPI mode or TMC in Standalone mode. Think it may be the X-UART jumper pins ?. How can i test. Have 12V and USB to Raspberry PI plugged in and powerd up ok.

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

I have the same trouble for X only.But instead of All LOW i have ALL HIGH.
I havent changed anything, the problem occured over night at the last boot.

i have orderd a new board and 5 more TMC2208 to test if its the board or me lol.

i have orderd a new board and 5 more TMC2208 to test if its the board or me lol.

Did the new board and drivers work?

i have orderd a new board and 5 more TMC2208 to test if its the board or me lol.

Did the new board and drivers work?

Sorry haved not fitted yet. still useing the same TMC2208’s in standalone mode lol.

https://www.youtube.com/watch?v=duNHOPlh2Pg&t=688s
The only thing I’d change from this video is
#define SERIAL_PORT_2 = 0
I haven’t done 2208s but I have my 2130’s in SPI running. Consider the new TMC2209’s, the goodness of 2130s in a cooler running and uart capable package.

@pauleley
You way want to check your 2208 step sticks how the TX/RX pins are routed on your sticks.
May be there is another 1k ohm on the stick getting in line with the 1k ohm on the SKR TX internally.
You would need a good meter with a resistance mode verifying wich step stick port is wired directly to the TMC pin.
The use of these ports of the step stick is vendor dependend. So it’s not an SKR problem but compatibility with potential non-Bigtree sticks.
The difference of your XYZ channels may be a small variation in the serial resistores causing only one channel failing.

See my TMC2209 post for an option to fix this with a unusual jumper setting in the SPI jumper field.

Same Issue here . BUT for all my 2208′ s

SENDING:M122
X Y Z E
Enabled false false false false
Set current 600 600 600 600
RMS current 1049 1049 1049 1049
MAX current 1479 1479 1479 1479
Run current 18/31 18/31 18/31 18/31
Hold current 9/31 9/31 9/31 9/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
[mm/s]
OT prewarn false false false false
OT prewarn has
been triggered 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

Any guesses?? I have soldered the patch underneath the stepstick.

Источник

Testing X connection. Error: All LOW #92

Trying to set up TMC2130.

Compiled successful and run M122.

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 thresh.
[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 8 8 0 0
uStep count 0 0 0 0
DRVSTATUS X Y Z E
sg_result 0 0 0 0
stallguard
fsactive
stst * * * *
olb
ola
s2gb
s2ga
otpw
ot
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

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

Please close your unneeded tickets before open the next one.

both are valid issues

How have you powered the mainboard?

12v.. I also flashed the firmware on your git and I get the same error.

The problem I see is that there is more in the platformio.ini from this firmware. Stock marlin FW is this:
[env:STM32F103RC_btt]
platform = $
extends = env:STM32F103RC
extra_scripts = buildroot/share/PlatformIO/scripts/STM32F103RC_SKR_MINI.py
build_flags = $
-DDEBUG_LEVEL=0 -DSS_TIMER=4 -DHAVE_SW_SERIAL
monitor_speed = 115200

And this is the entry in the one from this git.:
platform = ststm32
board = genericSTM32F103RC
platform_packages = tool-stm32duino
build_flags = !python Marlin/src/HAL/STM32F1/build_flags.py
$ -DDEBUG_LEVEL=0 -std=gnu++14 -DHAVE_SW_SERIAL -DSS_TIMER=4
build_unflags = -std=gnu++11
extra_scripts = buildroot/share/PlatformIO/scripts/STM32F103RC_SKR_MINI.py
src_filter = $ +
lib_deps = $
SoftwareSerialM=https://github.com/FYSETC/SoftwareSerialM/archive/master.zip
lib_ignore = Adafruit NeoPixel, SPI
monitor_speed = 115200

But when I use the one from this git, it will not compile. I feel as though some driver or dependency is not downloading.

I used the bugfix version from GitHub Marlin and your configuration files and only changed the platform.ini (STM32F103RC_btt) and it compiled successful on my system.

It compiles just fine. BUT TMC2130 will cont connect. It obviously compiles if I am able to do an M122 command through pronterface and give you the output. I need to get it to connect to TMC2130. That’s the problem.

Use this in platformio.ini and it will not.

But the driver registers and connection status looks like they do not get enough power. Disconnect the 12v and use USB power only and i believe you will get the same m122. As an advice i would also start with 16 microsteps and hybrid treshold off. My setup with 24v and btt tmc2208 works great.

So I am using the latest bugfix. Drivers are getting plenty of juice. I think I figured it out. When I bought these drivers, I did not know that there were jumpers on the boards. I bought these boards back when they were still fairly new, and had not tried to implement them. The original TMC2130’s did not have jumpers. These are not original and the retailer I got them from provided no info on this. Looking at the same board now has documentation that was not available at the time. Mine came setup for stand alone mode.

Having the old version up is confusing. I think you should just have the latest drivers and latest config file examples because the firmware you have up will not even compile due to its age and the progressment of marlin.

I still do not know if they will work, but I can say the firmware is compiling as expected. It attempts to connect to the TMC2130’s through SPI but the drivers are being jerks right now due to them being in stand alone mode.

I compiled for standard A4988, configured board jumpers to step mode and popped in some A4988 drivers. I did confirm that the board is working well.

Thanks for trying to help. I will use your micro step advise. I’ll reconfigure the stepdrivers, board and firmware tonight and give it a try. I really hope these things work. Let you know.

Источник

[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.

Источник

So I recently put an SKR v1.3 and TMC2225 steppers on my printer. I started getting a TMC Connection Error when starting up the printer. When I did a M122, I got an «ALL LOW» error on Z2. I swapped the driver with E0 and now I am getting ALL LOW on E0 and Z2. So I swapped again to Z1 and now all three say ALL LOW. My guess is I have a fried driver that has now fried my board but I want to confirm what is bad (the board or the drivers or both). The board is setup for UART (all jumpers removed from the stepper connections except the red UART pins).

Thanks!

Other observations:

• I also noticed that whatever driver is connected to E1 seems to get warm. Not hot but warmer than the other drivers. So maybe it’s the E1 port frying the drivers?
• I changed Z, Z2 and E0 to be in standalone mode and moved the correct jumpers. Z1 and E0 work. Z2/E1 is still not working.
• #define NUM_Z_STEPPER_DRIVERS is set to 2
• At no point did I power the board by USB
• So I swapped the Z1 and Z2 drivers in standalone mode and the other/Z1 stepper stopped working. So one of the drivers is definitely bad. I put in my old DRV8825’s and at least have it working/functional. I did try putting E0 back to UART mode and it had the same TMC Connection Error. So either I fried the driver or fried the board UART mode, not sure.
• I took one of the marginal TMC2225 drivers (one of the two where I can use in standalone mode in Z1, Z2 or E0 but won’t do UART without an error) and put it in my Y axis spot and it seems to function correctly in UART mode. So my guess is I have a bad TMC2225 that destroyed something related to UART for the Z1, Z2/E1, and E0 ports on the board

Edited 6 time(s). Last edit at 03/13/2021 06:48PM by heatvent.

Hello everybody,

because of noone can help me i post myproblem here maybe it is a bug.

I have the following hardware:
mks gen l Version 2
tmc2208 V 2

When i connect via ponterface or it is as error in my lcd at after boot there comes an tmc connection error.

In ponterface -> Z connection… Error: All LOW

when i do an an

m122

SENDING:M122
echo:SD init fail
echo:SD init fail
X Y Z E
Enabled false false false false
Set current 800 800 800 800
RMS current 795 795 1436 795
MAX current 1121 1121 2025 1121
Run current 25/31 25/31 25/31 25/31
Hold current 12/31 12/31 12/31 12/31
CS actual 12/31 12/31 0/31 12/31
PWM scale 21 22 0 22
vsense 1=.18 1=.18 0=.325 1=.18
stealthChop true true false true
msteps 16 16 256 16
tstep max max 0 max
pwm
threshold
[mm/s]
OT prewarn false false false false
off time 3 3 0 3
blank time 24 24 16 24
hysteresis
-end -1 -1 -3 -1
-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 0xC0:0C:00:00
Y 0xC0:0C:00:00
Z 0x00:00:00:00 Bad response!
E 0xC0:0C:00:00
Testing X connection… OK
Testing Y connection… OK
Testing Z connection… Error: All LOW
Testing E connection… OK
Disconnected.

You can see that the z stepper weird settings.

With an M906
X driver current: 800
Y driver current: 800
Z driver current: 800
E driver current: 800

I exchange the stepper driver with an working from board that did not solve the problem it is the same.

I set the voltage for xyz to 0,760 and for z at 0,900

Is some on there that can help me ?

Thanks in advance

Description

Steps to Reproduce

Required: Please include a ZIP file containing your Configuration.h and Configuration_adv.h files.

1. [First Step]
2. [Second Step]
3. [and so on…]

Expected behavior: [What you expect to happen]

Actual behavior: [What actually happens]

Additional Information

• Provide pictures or links to videos that clearly demonstrate the issue.
• See How Can I Contribute for additional guidelines.

Hello, I recently tried upgrading to TMC2209 for my Thinker S V2. It works if I use the HEX file provide, however I need to compile my own to configure Filament Runout and BLTouch. However, when ever I do this, Marlin report «TMC Connection Error» on boot up. The stepper work, but using Sensorless homing fails. If I run GCode M122 I get the following.

Recv: Driver registers:
Recv: X 0x00:00:00:00 Bad response!
Recv: Y 0x00:00:00:00 Bad response!
Recv: Z 0x00:00:00:00 Bad response!
Recv: E 0x00:00:00:00 Bad response!
Recv:
Recv:
Recv: Testing X connection… Error: All LOW
Recv: Testing Y connection… Error: All LOW
Recv: Testing Z connection… Error: All LOW
Recv: Testing E connection… Error: All LOW

I’ve made sure I update the Thinker Rambo config to have setting for Serial and I’m not sure what else to try, help please.

If anyone want to take a look at the config files, they can use my repository here for bugfx 2.0.X
https://github.com/dapostol73/Marlin/tree/bugfix-2.0.x