I just finished testing it and it's working great; it uses a $0.50 optical endstop.

Check it out, I'd love to hear some feedback!

https://www.myminifactory.com/object/3d-print-filament-progression-and-runout-sensor-optical-endstop-and-encoder-wheel-124487

@chrishamm Heyy amazing thank you for the update!

Installed 64bit on my Duet3 MB6HC + Rpi3b+ and everything running mighty fine right out the box this time -- no vnc/hdmi shenanigans like with the experimental build.

Hdmi touchscreen feels super snappy too, way more responsive than back on buster, outstanding work, now to push some plastic!

Just published the updated model using a $3 Schmitt trigger equipped arduino sensor;

Getting much more consistent reading

Check it out there

https://www.thingiverse.com/thing:4445504

Awesome Stuart, thanks for carrying on Danal's work

Looks well documented too, I'll give it a shot over the weekend.

Very neat of you to handle issues outside of your own setup too

Do you think in it's current state this could realistically be implemented as a plugin in DWC for a possible GUI?

@o_lampe Excellent question; it worked about fine for me with pretty high tolerance (ended up running 25-200%) but would still get occasional spikes at 400% triggering false positives

Then @JohnOCFII made this awesome in-depth investigation using a logic analyzer and found out that the signal was indeed noisy and implementing a schmitt trigger solved the issue; https://forum.duet3d.com/topic/19284/inconsistent-results-with-optical-encoder-wheel-filament-sensor

So I found an IR sensor that has a shmitt trigger integrated and modified the housing for it

brilliant, that would give a great second life to my old ipad; the web interface gets clunky through safari

I'll give it a shot!

@danym21

Hey man I just noticed I had this lines in my config.g here for my sensorless homing;

it seems like Stealthchop would not engage unless these are in place

; Stealthchop parameters
M915 P0 S3 F1 H134 T1 R0	
M915 P1 S3 F1 H134 T1 R0

I do not not why, but my guess would be around T parameter that controls the coolstep register according to https://duet3d.dozuki.com/Wiki/Gcode#Section_M915_Configure_motor_stall_detection

Edit: Also the Hmin parameter; for which I made a calculator here:

https://docs.google.com/spreadsheets/d/1gCapl-1CZh7Zz267W_CFtLBbBV-UMDjpXMGDIyr5oE4/edit?usp=sharing

@dc42 thoughts?

@bearer Oh boi I sense we'll be needing incremental encoder support

Would be fairly simple to implement though; "just" adding a second sensor and 2nd row of slots from the hardware point...now to add it in the code..

I use a custom Flex3Drive with absolute shortest filament path so I haven't experimented with PA either

@jay_s_uk Well I'd be damned; didn't think of removing them but these were indeed tied to my TMC5160 tuning

Also somehow missed that I had M569 set to D3...

Set it back to D2, disabled M915 and it seems to be running like a champ now, thank you very much!

Let's push some plastic now

Hi @Phaedrux , yes mounting them was the first thing I did upon reception; when the problem occured I removed the belts to insulate the gantry binding possibility and kept testing this way to prevent crashing it due to the stalls

@chrishamm Heyy amazing thank you for the update!

Installed 64bit on my Duet3 MB6HC + Rpi3b+ and everything running mighty fine right out the box this time -- no vnc/hdmi shenanigans like with the experimental build.

Hdmi touchscreen feels super snappy too, way more responsive than back on buster, outstanding work, now to push some plastic!

@chrishamm Ok great that definitely did something;

Now I can connect on both RealVNC and TigerVNC... But all I get is a grey screen in both cases

Such is the case on both duetpi and the official pi release, both updated to latest (I have them both on separate SD cards now to cross test)

HDMI display still shows on official release (still no touchscreen) and black on Duetpi

The search continues

@chrishamm interesting; just flashed latest vanila raspios bookworm and the screen works out of the box (but not the touchscreen?)

Meanwhile I'm unable to access VNC, neither through Tiger or RealVNC with both wayland and X11, even while confirmed running hmm

bump couldn't figure it out still

@chrishamm Ok I just installed it on a fresh card; A couple issues:

• My HDMI display shows a black, unresponsive screen after bootup despite showing the Duet bg and boot sequence just fine. Display manager service checked and active

• Likewise, VNC is not connecting despite the service being turned on

• I have full access through SSH though, through which I performed a git init, remote add and fetch origin in /sd to get my backup from my github backup; all is well, however...

• It appears the file permissions are all bonked out; config refuses to load with this message: Error in start-up file config.g line 29: Access to the path '/opt/dsf/sd/sys/eventlog.txt' is denied. >>> This is a know issue I previously sorted out by doing sudo chmod 777 -R /opt/dsf/sd but there has to be a better way right

Any tips on fixing these quirks? Thanks!

@chrishamm woohoo great news, will finally be able to make use of my arducam

Can the current image be fully upgraded to release when it comes out or will that require reflashing the release image?

@gloomyandy This was my first time updating from the Duet; RC1 was a fresh flash from USB, but yep I'm on Duet3 MB6HC + SBC

Just a heads up, the fw file names appear to be case sensitive, but the https://github.com/gloomyandy/RepRapFirmware/releases repo produces wrong case (Duet3Firmware_FLY36RRF where M997 expects Fly)

This is also erroneous on the docs: https://teamgloomy.github.io/fly_rrf_36_general.html

I've figured simply correcting the case on both .bin and .uf2 made the flash successful

Perhaps have GitHub produce case correct filename and reflect it in the docs for further reference?

Apart from that still happy with the board, thank you!

@jay_s_uk Well I'd be damned; didn't think of removing them but these were indeed tied to my TMC5160 tuning

Also somehow missed that I had M569 set to D3...

Set it back to D2, disabled M915 and it seems to be running like a champ now, thank you very much!

Let's push some plastic now

@jay_s_uk any thoughts on this?