Rat Rig Community [Unofficial]•17mo ago

The value 'my_sensor' is not valid for SENSOR

Getting this error after installing a BTT smart runout sensor. I have it plugged into the circled slots, set to PG15 (tried !PG15, same error). Printer config is attached. Appreciate any ideas.

printer4.cfg

37 Replies

blacksmithforlife•17mo ago

That's because you named it Filament_Sensor not my_sensor

ptegler•17mo ago

need to include your printer.cfg for analysis so we can see what/why the error is being thrown. ...but an error like that means the way/test/format you name your sensor is simply invalid.

blacksmithforlife•17mo ago

he did, it is attached as printer4.cfg

ptegler•17mo ago

doooohL!

VauschOP•17mo ago

Oh was it supposed to be changed? I just copied it from the macros page. I'll try that.

blacksmithforlife•17mo ago

well, you are telling your slicer that it is called my_sensor so either change it to be named that in your config, or change it in your slicer to match your config

VauschOP•17mo ago

Oooohhh OK thank you. Sorry one last thing: Where do I change it in the slicer? Prusaslicer 2.6 in this case?

blacksmithforlife•17mo ago

Where did you put my_sensor? That's where you need to change it

VauschOP•17mo ago

I didn't. it was that way by default

blacksmithforlife•17mo ago

my_sensor doesn't show up anywhere else in your printer.cfg. so that is coming from another place where you are specifying the sensor

VauschOP•17mo ago

Weird. Cuz I literally did nothing except copy the code from the macros page. Could it be in another cfg file?

blacksmithforlife•17mo ago

Did you add another config file? Ratos by default doesn't have a filament runout sensor setup

VauschOP•17mo ago

Nope. Tho since I installed the OS I have always gotten a "Filament sensor undetected" whenever it starts up. And I've reinstalled the OS twice.

blacksmithforlife•17mo ago

That makes no sense. Are you sure you didn't edit another file?

VauschOP•17mo ago

Positive.

blacksmithforlife•17mo ago

https://github.com/search?q=repo%3ARat-OS%2FRatOS-configuration%20my_sensor&type=issues my_sensor doesn't exist in Rat-OS.

GitHub

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

VauschOP•17mo ago

Eeeyup. Didn't find anything like it online either.

blacksmithforlife•17mo ago

So when you say you have reinstalled Rat-OS, what exactly did you do? Maybe you are restoring something and that has the my_sensor expectation?

VauschOP•17mo ago

Well I was getting an issue with it repeatedly so I took the microsd card out of the pi, formatted it, reflashed the OS to it and reinstalled everything including the mainboard drivers. After which it was a few versions back so I updated everything on the config menu.

blacksmithforlife•17mo ago

and reinstalled everything

What does that mean? Rat-OS doesn't have you install anything

VauschOP•17mo ago

Installed Updates I meant. My bad. But yeah I get the "no sensor detected" even immediately after I install it.

miklschmidt•17mo ago

In the custom start gcode settings. I don't know why it's there by default, it is however commented out in the default presets. Please post a screenshot of the error

VauschOP•17mo ago

The error is the title. The "no sensor detected" isn't an error so much as just a quick heads up it does before any print starts. It'll print after that. Probably because of the custom gcode

miklschmidt•17mo ago

Screenshot whatever you're talking about, it's not obvious what you're describing.

VauschOP•17mo ago

Alright. Lemme start a print Gotta put a beacon on this thing or get that small space macro. probing takes longer than some prints.

miklschmidt•17mo ago

Okay i can already say if you don't get the error/warning/whatever before it gets that far, then it's definitely your slicer configuration.

VauschOP•17mo ago

Yeah I found the gcode you mentioned and it had the 'my_sensor' line in it. I changed it to 'Filament_sensor' but I haven't plugged the BTT back in

miklschmidt•17mo ago

You can up the probe speed:

[probe]
samples: 1
speed: 15
lift_speed: 30

[bed_mesh]
speed: 800

[z_tilt]
speed: 800

[probe]
samples: 1
speed: 15
lift_speed: 30

[bed_mesh]
speed: 800

[z_tilt]
speed: 800

This already helps a ton

VauschOP•17mo ago

Oh good to know. does it retain accuracy?

miklschmidt•17mo ago

If you have the performance config enabled you can increase your z_speed too

[printer]
max_z_accel: 1000
max_z_velocity: 50

[printer]
max_z_accel: 1000
max_z_velocity: 50

Depends on the probe, 15 mm/s is fine with a SuperPinda

VauschOP•17mo ago

Bltouch

miklschmidt•17mo ago

Oh yeah then no 😄 You want to keep speed at 7 The rest you can still do And also you can enable touch probe mode.. Lemme find the config

VauschOP•17mo ago

Yeah I see what it was. I had the start gcode including ";enable this if you have a BTT Smart Filament Sensor SET_FILAMENT_SENSOR SENSOR=my_sensor ENABLE=0" active in the start gcode.

miklschmidt•17mo ago

[bltouch]
stow_on_each_sample: False
probe_with_touch_mode: True

[bltouch]
stow_on_each_sample: False
probe_with_touch_mode: True

I think that's how it works. Yep that's the one

VauschOP•17mo ago

I changed it to 'Filament_sensor' instead of 'my_sensor'. I'll plug it back in and test it. Just to be extra sure I should run a reverse bowden tube between the sensor and the extruder to reduce the slack, right?

miklschmidt•17mo ago

yes

VauschOP•17mo ago

thank ya.

Gaming

Programming

The value 'my_sensor' is not valid for SENSOR