Printer.CFG information and BTT Octopus V1.1 pinout for Camera, BLTouch and BTT Smart Filament Sensor

[SMURPH]

Can anyone send me the working information for the printer.cfg file and BTT Octopus 1.1 pinout for the following:

1. Printer.cfg information and location in the file for a camera?
   • Is it better to pinout through Raspberry Pi?
2. Printer.cfg information and location in the file for the BLTouch?
   • Would it be better to use the BLTouch than the Inductive probe?
3. Printer.cfg information and location in the file for the BTT Smart Filament Sensor?
   • BTT Octopus V1.1 pinout for the BTT Smart Filament Sensor?

 

[kaimjr]

1) For the camera, I would plug it into the PI. 

3) My config is a mess of mods mashed together, but I can help with the BTT Smart detector. You can use any of the free stop pins. PG6, PG9, and PG10 are usually used up for for x, y, z end stops, leaving PG11 - PG15 free. I used PG11 for the smart detector. 

######################################
##---   Filament Runout Sensor   ---##
######################################
[filament_motion_sensor btt_smartie]
detection_length: 7.0
extruder: extruder
switch_pin: !PG11
runout_gcode: FILAMENT_RUNOUT





gcode_macro M300]
gcode:
  {% set S = params.S|default(1000)|int %}
  {% set P = params.P|default(100)|int %}
      SET_PIN PIN=BEEPER VALUE=0.5 CYCLE_TIME={ 1.0/S if S > 0 else 1 }
  G4 P{P}
      SET_PIN PIN=BEEPER VALUE=0

[gcode_macro M600]
gcode:
  {% set V = printer["gcode_macro _USER_VARIABLE"].verbose %}
  {% if V %}
    { action_respond_info("Filament Change Requested!") }
  {% endif %}  
  SAVE_GCODE_STATE NAME=M600_state
  PAUSE
  G91
    G1 E-.8 F2700
    Park_Toolhead
  G91
    G1 E-15 F1000
    RESTORE_GCODE_STATE NAME=M600_state

[gcode_macro FILAMENT_RUNOUT]
gcode:
  M300 S1 P10
  M600
  M300 S1 P10

 

 

[SMURPH]

28 minutes ago, kaimjr said:

1) For the camera, I would plug it into the PI. 

3) My config is a mess of mods mashed together, but I can help with the BTT Smart detector. You can use any of the free stop pins. PG6, PG9, and PG10 are usually used up for for x, y, z end stops, leaving PG11 - PG15 free. I used PG11 for the smart detector. 

######################################
##---   Filament Runout Sensor                       ---##
######################################
[filament_motion_sensor btt_smartie]
detection_length: 7.0
extruder: extruder
switch_pin: !PG11
runout_gcode: FILAMENT_RUNOUT

gcode_macro M300]
gcode:
  {% set S = params.S|default(1000)|int %}
  {% set P = params.P|default(100)|int %}
      SET_PIN PIN=BEEPER VALUE=0.5 CYCLE_TIME={ 1.0/S if S > 0 else 1 }
  G4 P{P}
      SET_PIN PIN=BEEPER VALUE=0

[gcode_macro M600]
gcode:
  {% set V = printer["gcode_macro _USER_VARIABLE"].verbose %}
  {% if V %}
    { action_respond_info("Filament Change Requested!") }
  {% endif %}  
  SAVE_GCODE_STATE NAME=M600_state
  PAUSE
  G91
    G1 E-.8 F2700
    Park_Toolhead
  G91
    G1 E-15 F1000
    RESTORE_GCODE_STATE NAME=M600_state

[gcode_macro FILAMENT_RUNOUT]
gcode:
  M300 S1 P10
  M600
  M300 S1 P10
 

Thanks for the info. I will let you know how it goes tomorrow 

[JohnGalt1717]

When I use this code with a Voron 2.4 it freaks out with G300 in Klipper and its constantly telling me it has run out on PG11. (either !PG11 or PG11)

Does anyone have a known working configuration for a Voron 2.4?

[Simon2.4]

Hi @JohnGalt1717 and welcome to teamFDM, I invite you to post a little something about yourself in the introductions section https://www.teamfdm.com/forums/forum/39-introductions/ or better yet, show us your baby in the build diaries section https://www.teamfdm.com/forums/forum/27-build-diaries/

Here is the Github for the 'Filament Please' MOD. I looked at it and I think you will find everything you need. The cfg is in the Klipper section.

https://github.com/VoronDesign/VoronUsers/tree/master/printer_mods/JD/RefillPlease

Cheers

[JohnGalt1717]

Thanks @Simon2.4! Works nicely!  And Will do.

[claudermilk]

I just built the RefillPlease mod a couple of days ago. It is a pretty simple build, and works easily. I ended up using the example config script as inspiration and just wrote my own.