RRF 3.1.1 M572 breaks M591

gnydick

Also, there's something wrong with the tracking.

The console output is not incrementing. This happens a lot.

gnydick

@dc42 Can you please give some guidance here? I described many problems with using a pulsing filament sensor, but you've yet to give an example of a hardware configuration that will actually work, since it seems like pressure advance is going to break it no matter what.

dc42

I don't know of a hardware configuration that will work. I only added support for pulsing filament sensors because some users asked for it. My guess is that if you specify a long enough comparison distance, it will work reasonable well, but you will have to extend the upper range of allowed measurement to handle the case of backwards motion. For example, instead of allowing 70% to 130% movement, maybe you would need to allow 70% to 180%.

The code attempts to ignore extruder-only movement by default, so that retracts and reprimes are not counted. This should make it ignore the majority of pulses received due to backwards movement, although not backward movements at the end of printing moves when high pressure advance is used. Feel free to review the code, it's possible that it's buggy.

gnydick

@dc42 it's the PA movements that send it way over the top. Can you fix that so it knows how to deal with those?

dc42

How much PA are you using?

gnydick

@dc42 0.09, but it's also the other things I was mentioning, like the dial jogging back and forth during short extrusions and retractions in high detail areas. All sorts of weird motion corner cases where the edge of the window in the encoder just happens to end up right on the edge of the sensor, so it wags back and forth.

gnydick

@dc42 If the PA is not taken into account for pulsing sensor, is it taken into for the more precise sensor types that can detect retract v. exrude?

gnydick

there was well over 100mm of extrusion

1:03:06 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
1:02:42 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
1:02:14 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
1:01:57 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
1:01:30 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
1:00:59 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no calibration data
12:59:15 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no data received

gnydick

it finally triggered. I don't get it. over 31.5mm? The Drive 1 on the UI showed 200.

1:08:24 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 1.300mm/pulse, allowed movement 80% to 120%, check every 15.0mm, no data received
1:08:18 AMPrinting resumed
1:08:16 AMM24
1:08:12 AMM591 D1 L1.3
1:07:57 AMM591 D1
Pulse-type filament monitor on pin e1stop, enabled, sensitivity 10.000mm/pulse, allowed movement 80% to 120%, check every 15.0mm, measured sensitivity 1.311mm/pulse, measured minimum 760%, maximum 765% over 31.5mm
1:07:55 AMPrinting paused at X154.7 Y138.5 Z3.2 U0.0
1:07:52 AMResume state saved

dc42

@gnydick said in RRF 3.1.1 M572 breaks M591:

@dc42 If the PA is not taken into account for pulsing sensor, is it taken into for the more precise sensor types that can detect retract v. exrude?

Yes.