New belt status test, completely different belt values.  

RE: New belt status test, completely different belt values.

Do you also get the same numbers with a full selftest on the new firmware?

RE: New belt status test, completely different belt values.

Yes, self test or standalone belt test delivers the same result

RE: New belt status test, completely different belt values.

Weird, there were experiments with changing the speed used for the test (which affects the numbers) but these were not in the final version that was merged for this reason.

When I tested it on my own printer prior to it being merged the numbers before/after were the same... maybe something else changed afterwards.

/shrug. 

RE: New belt status test, completely different belt values.

I adapted my belts to the new values, I had to shift several teeth in the belt, so it is really a very different setting. Now I’m printing a large object, to see how it works. Seems to work fine for now. 

RE: New belt status test, completely different belt values.

keep in mind those numbers measure motor load and not actual belt tension. There are a lot of things that contribute to motor loading such as bearings and speed. They can be an indicator of belt tension issues, but should not be taken as canon for that. 

So if your prints were fine before, I would not take too much stock in the actual numbers.

For example, mine generally read around 210-220 because I have 0.9 degree steppers. 

RE: New belt status test, completely different belt values.

Is the higher the number, the higher the current draw?

RE: New belt status test, completely different belt values.

With 0.9 steppers on X and Y I have X 167  and  Y 186  Measured skew 0.01 if this makes any difference.

RE: New belt status test, completely different belt values.

The lower the number, the higher the current draw. 

The belt test value comes directly from the "Stallguard" register in the TMC2130 - and the other use for this register is the crash detection. 

Essentially, if the value in the register is 0, then the DIAG (crash detect) pin is set high (and your printer detects a crash). 

(Ergo, tuning stallguard/crash detect tweaks will also affect the belt tension numbers, and you want to tune SG such that your register is a ways above zero unless it is obstructed. I think this is why PR has the suggested range value; if you are too far above, CD may not work reliably, and if you are too low then you will get false crash senses.)

RE: New belt status test, completely different belt values.

Thanks vintagepc. I'm running the latest 3.9.0 but with the TMC setting and skelestruder alterations from Guys 0.9 branch ported over since he's too busy with important work for now which is much more important than maintaining firmware. 

RE: New belt status test, completely different belt values.

I can confirm that the numbers being outputted are much lower now than before the firmware update, without any change to the printer. I know this because I spend a lot of time doing belt tension and running the self test just before the update and I had reached a stable point with both X and Y very close to 260. Now I'm getting values around 200.

RE: New belt status test, completely different belt values.

Tweaked my firmware and belts and now have X 198  and Y 214 yet at the end of the Belt Test it shows selftest failed which it also did previously, yet if I carry out full Selftest which includes fans homing etc, everything passes.

Any idea what is going on? and what should I check?, anything in particular from the pronterface output during these tests? or where in the firmware does it compare values returned during testing against what is supposed to be correct.

Thanks

RE: New belt status test, completely different belt values.

The belt (axis) test fails if the length of the axis doesn't match either what's expected or the value from the two measurement passes it does (i.e. value from left dir != value from right dir). 

Usually that means belt slop or a loose pulley. I don't know what that means in the context of Guy's firmware, given his stallguard tweaks. I am running stock with my own 0.9s. 

RE: New belt status test, completely different belt values.

That is fine and I can see the results and if the value is too high the printer will fail the self test with a loose pulley message, I have tested this by slackening the tension, but this error is strange, the self test runs, completes without any issue waits approx. 30s I guess then states self test failed. This only occurs in the separate Belt Test routine, but does not fail during the complete self test routine which includes the belt test as part of it.

It's not actually stopping me printing, just seems like a glitch at the end of the belt test routine.

Any pointer to where the test routine is in the code so that I can debug this myself please.

I'll try stock stall guard settings tomorrow.

Thanks.