Inconsistent results with optical encoder wheel filament sensor
-
@JohnOCFII dunno I don't understand why firmware is not reading those pulses if they are around 0.2V and 3.2V they should be read properly on the input pin. Maybe @dc42 can shed some light on what might be happening, and how to test/debug. I'm clueless at this point
-
@JohnOCFII Those are perfect values for this sensor and the Duet should have no problems detecting them as pulses.
I'll take a look deeper and we can see what the waveforms look like when you have the logic analyzer.
-
The Logic Analyzer arrived! Here's some data.
-
@JohnOCFII that looks ok, signals are more/less clean ... should work 1/1
if you grab a longer piece, do you see that during constant extrusion move signals are evenly spaced as one would expect?
levels seem ok, ~3V and ~0V, timing seem ok .. using the "extruder endstop" input is the only other idea I have.. don't see why would that make any difference but I use the encoder endstop input and it works for me
... now I still have some variance but I never reproduced this with many impulses and still "no data" on the sensor reading... @dc42 wrote that part of the code iirc and he should be able to say what might be wrong, the code for the pulse sensor itself, I looked month or two ago (and for laser sensor too) and I did not find anything weird there but.. -
That waveform looks OK.
Can you try commanding something like a 120mm extrusion slowly and then turn the wheel so that you have 100 notches pass and see if you get near the right amount of detected extrusion?
While capturing using the Saleae so we can also see the signal?
If you could then post the Saleae capture file anyone can download the Saleae software and take a look at it with you.
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
Can you try commanding something like a 120mm extrusion slowly and then turn the wheel so that you have 100 notches pass and see if you get near the right amount of detected extrusion?
With the unit assembled, I can't visually see the encoder wheel. I can certainly run 120mm and we can see what the Logic Analyzer sees.
If you could then post the Saleae capture file anyone can download the Saleae software and take a look at it with you.
So far, my Saleae experience is connecting lead 0 and ground to the ground and signal connection to the optical sensor. I hit the big green button to start capture.
I need to do a bit more reading to see if there is anything else I should be setting up for a good capture.
Progress might be slow until Sunday, but I'll do what I can to make progress.
I really appreciate your hanging with me on this, @arhi and @alankilian
John
-
@JohnOCFII You don't need to connect lead #0 to ground.
You can just connect one of the GND leads to ground and lead #0 to your signal and then you can turn off the other signals for capture.
You can capture as slowly as the analyzer will run to make your capture files small.
Make sure you're set to 3.3 Volts also.
Then green-arrow and extrude.
Stop and File->Save Capture and you can post it.SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
You can just connect one of the GND leads to ground and lead #0 to your signal and then you can turn off the other signals for capture.
Yes that is what I did - I described it poorly.
You can capture as slowly as the analyzer will run to make your capture files small.
Make sure you're set to 3.3 Volts also.
Then green-arrow and extrude.
Stop and File->Save Capture and you can post it.Sounds good. I've been slammed with meetings the last couple of days. I'll see if I can set this up tonight.
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
Then green-arrow and extrude.
Stop and File->Save Capture and you can post it.I set up a capture during a vase mode cylinder print. Speed was 15mm/sec doing the vase. This was about the first 1/3rd of a 30 minute print. I know this isn't quite as controlled an example as a pure feed of 1000mm, but I needed to run the print anyway.
I captured this using the new Saleae Logic alpha software, version 2.3.13.
The capture is about 390 MB compressed (on disk). It's got both the digital and analog capture. I suppose I could have turned off the analog and saved some space.
Here's a link to the capture file: https://1drv.ms/u/s!ApuOkxTDmZEzgfznb3Mf2-ULLBN65XQ?e=cKZycH
And here's a timelapse: https://youtu.be/FcXaF9faE70
John
-
@JohnOCFII that singnal is uber ugly and need to be debounced
look at your capture here:
question is if duet sees this many impulses but it's seen some of them for sure ... you need to add some debouncing circuit between duet and that encoder
-
I agree that it's the slow rise-time of the signal causing multiple events to be detected.
I didn't realize you were going to get one full pulse every six seconds.
So, how to deal with it?
A good way to do it would be to add a "Schmitt trigger" inverter chip. Would wiring up one IC to power and your signal be too intimidating?
You could also try just doing a resistor-capacitor debounce circuit and it might work until your wheel stops at just EXACTLY the wrong place and then your print will fail.
Here's a beginner explanation on the math you can use to decide resistor and capacitor values:
https://www.allaboutcircuits.com/technical-articles/switch-bounce-how-to-deal-with-it/
Here's one from more of an expert:
http://www.ganssle.com/debouncing.htm
http://www.ganssle.com/debouncing-pt2.htmIt would also be possible to make some firmware changes (As described in Ganssle part 2. Probably listing 1 since we've got a very powerful processor.)
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
A good way to do it would be to add a "Schmitt trigger" inverter chip. Would wiring up one IC to power and your signal be too intimidating?
Fascinating!
Wiring up a solution would be a fun challenge. Finding the "recipe" of correct components, etc., will be the difficult part for me.
I'm curious what others trying to use an optical sensor are seeing? I don't think @fractalengineer ever saw the wild results I'm seeing. Do I just have a particularly bad batch of optical sensors?
Anyway, I'll read through those links in more detail when time permits.
Thanks to you both!
John
-
I am not sure ST alone will be a solution with a bounce so long. I think a comparator is something you'd wanna add here with ne555 circuit for proper debouncing ... on the other hand, instead of all that you could use some attiny44 or pic12f508 or something similar and make programmable debouncing circuit that one would embed in the sensor... in that case you could see what's the output of the laser/magnet sensor as they communicate with duet instead of just sending pulses
-
@JohnOCFII I think adding a "sample frequency" parameter to the filament motion sensing code would be useful to the largest number of people.
I'll download the code and see if I can make any suggestions there.
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
@JohnOCFII I think adding a "sample frequency" parameter to the filament motion sensing code would be useful to the largest number of people.
I'll download the code and see if I can make any suggestions there.
As I mentioned WAY up thread, I think all we really need to know is "is the wheel turning?" If yes, assume everything is fine. If no, tell the Duet to pause. Only variable is how long does the state of "not turning" need to be present before pausing?
John
-
@JohnOCFII Can you just set the "Over" amount to a huge value?
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
@JohnOCFII Can you just set the "Over" amount to a huge value?
Hmm... Perhaps.
Here's another odd data point. The two very first runs I did were within 200%. After than, I had days of testing where it would go from 30% to 3000%. But then, I started seeing those crazy high numbers, we'll above 10,000%. I do wonder if I'm chasing multiple issues.
-
@JohnOCFII Is this the wheel that you have applies the sticky copper tape to and cut out windows?
The sharper the windows are, the better results you'll get.
You might also try taping copper tape to both the emitter and receiver and only have a narrow (1/16 inch) slot in the copper cover. That and a narrow (1/16 inch) opening windows in the encoder wheel might help.
-
@alankilian said in Inconsistent results with optical encoder wheel filament sensor:
@JohnOCFII Is this the wheel that you have applies the sticky copper tape to and cut out windows?
The sharper the windows are, the better results you'll get.
You might also try taping copper tape to both the emitter and receiver and only have a narrow (1/16 inch) slot in the copper cover. That and a narrow (1/16 inch) opening windows in the encoder wheel might help.
It is. It seemed that that test didn't change results, leading me to believe the regular printed wheel was doing an acceptable job of breaking the light beam. Perhaps I switch back to an encoder wheel without the copper tape. I could also move back to the wheel with more spokes (the one on the right in this photo).
-
@JohnOCFII you can try other wheels, problem is just how the edge is created by that endstop and how it is interpretted by the duet... since there's obviously no signal conditioning from endstop and since it looks like duet is not doing any software debounce easiest thing would be to create a debounce circuit on the input
