Dreaming to use the BTT Sensor with E3V2-UBL-BLTouch-15x15-v4.2.2-v1.3.5

[BlueWings172]

Hello

I am using the E3V2-UBL-BLTouch-15x15-v4.2.2-v1.3.5 firmware and I have a BIGTREETECH Smart Filament Sensor that has been sitting on my desk for 2 months now because I don't know how to compile firmware.

Can anyone offer any assistance ? My objective is to obtain a E3V2-UBL-BLTouch-15x15-v4.2.2-v1.3.5 firmware that can work with the sensor.

thanks !

[Cal-LF]

Have you thought about the https://www.patreon.com/jyers to get a custom FW? I'm thinking @jyres can add the BTT smart sensor if it isn't already available.

[salymy10000]

#1248

[BlueWings172]

Have you thought about the https://www.patreon.com/jyers to get a custom FW? I'm thinking @jyres can add the BTT smart sensor if it isn't already available.

That's a great idea.

I have just registered as a patreon to backup this project. Hopefully this helps getting the BTT to work with the E3V2-UBL-BLTouch-15x15-v4.2.2-v1.3.5 firmware.

[Cal-LF]

@BlueWings172 Reach out to @jyres if you have any questions. I hope you get the sensor working with your setup. I use the manual mesh 4X4 FW and the sensor work well. Although I have not had it trip other than by testing it.

[BlueWings172]

@Cal-LF & @Jyers

Thanks so much guys for your great help!

I did receive a link to a shared folder on dropbox so this is actually working !

[Jyers]

Thanks so much for deciding to support my work! I really hope you enjoy the auto-compile service 😄

As always, feel free to reach out if you need any help at all!

[BlueWings172]

Hi Jacob It is absolutely my pleasure to be backing very talented and innovative developers like you. I have tried the auto compile service and I really love the idea behind it. That said I must be doing something wrong because I couldn't find the bin file in the shared folder even after 24 hours. Can you please let me know what I'm going wrong ? Thanks so much. Regards Saleem

…

On Mon, Aug 2, 2021, 8:16 PM Jyers ***@***.***> wrote: Thanks so much for deciding to support my work! I really hope you enjoy the auto-compile service 😄 As always, feel free to reach out if you need any help at all! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1239 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APXI73JJJQOJ2XVJWTCQQO3T23HGVANCNFSM5BIVVLVQ> .

[Jyers]

So sorry you were having trouble. I checked my logs and it seems that the issue was the fact that you had a folder and a simplified config both named the same. Looks like you've removed the folder now, so you should get a binary soon. Sorry for the confusion, I'll have to add a catch for that situation to the script.

[BlueWings172]

I have removed the folder but that did not work. I also have renamed the file to a short name without any special characters but that also did not work. Do you have any suggestions? Thanks

…

On Tue, Aug 3, 2021 at 6:51 PM Jyers ***@***.***> wrote: So sorry you were having trouble. I checked my logs and it seems that the issue was the fact that you had a folder and a simplified config both named the same. Looks like you've removed the folder now, so you should get a binary soon. Sorry for the confusion, I'll have to add a catch for that situation to the script. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1239 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APXI73MLRDVURGWPJ6SINDLT3AF6JANCNFSM5BIVVLVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[Jyers]

Sorry for all the confusion, seems like the issue may have been on my end. Either way it seems you now have a binary file 🥳

[BlueWings172]

Hey man Thanks so much for your great support ! I do see a bin file in Dropbox! I will test it and let you know the result. Thanks again

…

On Wed, Aug 4, 2021, 4:03 PM Jyers ***@***.***> wrote: Sorry for all the confusion, seems like the issue may have been on my end. Either way it seems you now have a binary file 🥳 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1239 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APXI73MDNO2XG54J3DG3NX3T3E3ARANCNFSM5BIVVLVQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

[BlueWings172]

After ordering a crimping kit, figuring out the correct wire order and figuring out that you need to change the sensor setting to High, it worked.

That said, there are two issues:

1-After you are notified that the filament ran out and asked by Octoprint to change the filament, the sensor is ignored from that point on and if the filament runs out again during that print there will be no action or notification. In fact, what is surprising is that the checkbox for the filament sensor in the firmware becomes unchecked after the initial filament runout notification. Therefore, the sensor is automatically disabled and will not trigger in the next prints until the box is manually checked again which will be undone by the very next filament runout trigger. (yes, I have clicked on Store Settings when I enabled the sensor).

2- The filament runout notification is displayed on the LCD screen but you can only resume by clicking the message on Octoprint. Would be great if you can resume the print after changing the filament from the printer without having to go to the pc and resume from there.

Thanks for your help.