3
$\begingroup$

I have a Lotmaxx Shark v2, which has developed the problem of constantly saying the filament has ran out when it hasn't. I've narrowed down the issue to the main board, and tried to work around the problem:

  • Installed new sensor (which is just a switch), no effect.
  • Checked the cable continuity all the way to the pins that plug into the main board, that was fine.
  • Added M412 S0 to the top of my G-code file to try to disable the sensor.
  • Set FILAMENT_INVERTING in the firmware configuration.

If, for whatever reason, the main board is damaged, I'd love to just disable this sensor. I don't really need it. Also unused is the second extruder set, so if I can't disable the sensor maybe I could configure the printer to use extruder #2 all the time instead of extruder #1?

$\endgroup$
2
  • $\begingroup$ you'd have to install new firmware that simply has no sensor. $\endgroup$
    – Trish
    Commented Jan 29 at 0:45
  • $\begingroup$ Or perhaps your firmware provides an option to disable it without reflashing. Mriscoc firmware for Ender 3V2 for example has that. Did you check advanced settings of your firmware? $\endgroup$
    – Bob Ortiz
    Commented Jan 29 at 7:37

1 Answer 1

2
$\begingroup$

Via firmware

Looking at your M412 - Filament Runout link, it says that it requires FILAMENT_RUNOUT_SENSOR.

Try disabling FILAMENT_RUNOUT_SENSOR in the firmware by commenting out (//) the following line, in Configuration.h, like so

//#define FILAMENT_RUNOUT_SENSOR

From Filament Runout Sensor

//#define FILAMENT_RUNOUT_SENSOR
#if ENABLED(FILAMENT_RUNOUT_SENSOR)
  #define NUM_RUNOUT_SENSORS   1     // Number of sensors, up to one per extruder. Define a FIL_RUNOUT#_PIN for each.
  #define FIL_RUNOUT_INVERTING false // Set to true to invert the logic of the sensor.

...

Via UI

Watch this video, The BEST Ender-3 V2 Firmware EVER?! MRiscoC Professional Firmware, at 2:43,

It shows the Filament sensor can be disabled via the UI:

Filament settings on printer UI

$\endgroup$
2
  • 1
    $\begingroup$ Thank you for the help and advice. I've dug into it... it seems my printer is using some ancient version of Marlin and is tricky to get working on a current version, based on what I've found on GitHub. So, I'm going to poke at building Marlin for it this weekend, but will probably end up ordering a new mainboard. In any case, thanks! $\endgroup$
    – Brad
    Commented Feb 2 at 0:03
  • $\begingroup$ That's a real shame that there isn't a Marlin upgrade path. BTW, If you have some useful links about the ancient Marlin and your board, then it might be useful for someone else, who is experiencing the same issue, if you posted them as an answer (maybe quoting the relevant parts). Also, knowing the version number (if there is one) of your ancient Marlin could be very useful. $\endgroup$
    – Greenonline
    Commented Feb 3 at 23:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .