Same as you pressing pause on the screen. Understand that the DIY solution and the Raise 3D filament sensor do the same thing, work the same way because the RAISEPACK LCD firmware is what commands the pause, what controls the action. The mainboard is just following gcode.All the FSR Marlin firmware version does is when that filament sensor also plugged into the endstop ports, just like the DIY solution triggers, then the mainboard sends to the LCD the pause gcode command. The LCD enters it's pause routine sending more gcode commands and stopping the print just as if you have touched the LCD and commanded a pause. Yes, you can run the load and unload filament just like any other pause.

Again, DIY solution and Raise 3D solution are the same thing. Yes, the sensor might be a different device, but the functionality by design is the same.

WOW!!! I just realize how expensive the F.Run-Out-Sensor is. 84€ for the sensor while the Main Controller board is 99,9€This is just plain unfair! It's like buying a car tor 100 and then buying a spare tire for 30

Anthonyvanv wrote:Also, Vicky, the runout sensor mount was 100% designed to mount to the top of the extruder.

You are right that the original design of the part is designed to mount onto the top of the extruder. But after several tests, we found that the trigger didn't work properly every time and digged out that the issue should be related to too short distance for the software to react.To improve the working accuracy, it will be more recommended to be installed above filament spools to ensure enough react time. We apologize for this confusion to you.

Anthonyvanv wrote:Also, Vicky, the runout sensor mount was 100% designed to mount to the top of the extruder.

You are right that the original design of the part is designed to mount onto the top of the extruder. But after several tests, we found that the trigger didn't work properly every time and digged out that the issue should be related to too short distance for the software to react.To improve the working accuracy, it will be more recommended to be installed above filament spools to ensure enough react time. We apologize for this confusion to you.

So what does this mean for your new PRO models that have it above the extruder?

Vicky@Raise3D wrote:You are right that the original design of the part is designed to mount onto the top of the extruder. But after several tests, we found that the trigger didn't work properly every time and digged out that the issue should be related to too short distance for the software to react.To improve the working accuracy, it will be more recommended to be installed above filament spools to ensure enough react time. We apologize for this confusion to you.

So what does this mean for your new PRO models that have it above the extruder?

The Pro2 series printers are not using the same firmware as N series printers, which doesn't include this issue. So on Pro2 series, the Filament Run-out sensor is installed above extruder by default.

I have had this happen the only two times I have run out of filament mid-print: The printhead does not resume where it left off. Instead it resumes about 20 mm from where it left off. At first I thought that it simply was not extruding immediately, but the second time I saw plainly that it positioned itself about 20 mm from the point it ended off and started extruding almost immediately -- there was a very small lag before the filament came out. See picture below. When I manually pause, I do not see this 20 mm gap.

I would be really curious to see if there there any difference in the result of the open source community made FSR firmware VS the Raise 3D FSR firmware. The Raise 3D sensor should work with both, it might just take a little testing to understand the correct options within the open source firmware. I say this because it's a simple matter of binary state. Either the sensor line is high or low, compared to filament present VS filament out. The open source firmware variant supports either combination (N.0. VS N.C.) logic or switch config.

Based on what you are saying, it appears to be how the triggered event is handled. Example would be, one lets the motion planner complete the last 16 planned segments in the buffer, the other method kills it at the buffer thus why you might see a loss of what is likely the 16 segments. I say this because you are printing a curve. A curve is not a curve in current gcode,it's a polygon, so that segment looks in my opinion to be about what I expect to match the known 16 segment buffer.I think key understanding, is, you presented the best possible scenario. If you were printing infill- especially infill without any coast enabled, then that could be 16 lines of infill skipped.

I think this warrants more detailed technical testing. In truth, this has nothing to do with the sensor itself and everything to do with the firmware. The sensor just kicks off the event- what happens next is all firmware logic between the raise touch and Marlin.

I installed the sensor yesterday, and already encountered a print failure directly caused by the tolerance on the pass through being too tight. a small imperfection in the filament caused it to be completely impossible to pull the filament any further, even by hand. Additionally, the added feed resistance from the sensor made it so that I had to increase the voltage of the drivers for the bondtech extruder in order to avoid skipped steps.

I had similar issues but no feed failures. I noticed the drag on the filament is way too strong. It is from the crazy angle that the tubes have to bend when you mount the sensor on the printer. It actually bends and creases the Bowden tubes. How do I know this?I removed my sensor because of this and noticed the tubes were creased.

Raise sent me a file to print of a new design of the mounting block. It seems better but I have yet to mount it. When I took my sensor apart to put the newly printed mounting block apart, a piece was broken off the sensor board. I am hoping they send me another one soon. I will then try to re mount the sensor with the new design mounting block that I printed. It does seem to shallow the angle on the tubes so it may work but I have to wait for the sensor.

I have been impressed with the raise 3d so far but this sensor seems to be a bit of a debacle. It causes way too much drag on the filament, installing it can be tough because of this and it damages the Bowden tubes. Also the instructions want us to switch the left and right spool feeding, so the left spool is for the right extruded and the right for the left extruded, which to me, makes no sense, but you can fix this by switching the way the 2 wires from the sensor are attached to the main board

I actually notice the drag even without the tubes attached, it is an inherent property of the sensor itself. I currently have the sensor mounted off to the side with short segments of filament in both of the feed paths so it is basically disabled without having to uninstall it entirely...