smarteffector sensivity - unable to change it

tomasf

@c310 The second part of the S parameter is supposed to be 255 minus the value. Try M672 S131:124.

garyd9

@tomasf said in smarteffector sensivity - unable to change it:

@c310 The second part of the S parameter is supposed to be 255 minus the value. Try M672 S131:124.

@tomasf, you might be thinking about M672 S105.

@c310 has it correctly for reverting the sensitivity of the firmware. Has the sensitivity been changed via M672 S105? If not, I don't think it will respond to a revert command. If that still doesn't work, try to power down the machine for 10 seconds or so and powering it back up.

tomasf

@garyd9 Oops. Yes, you're right.

c310

@garyd9

i powered down printer, tried different sensitivity - but no effect with LED. @dc42 please advise on smarteffector...

even with M672 S105:1:254 and vice versa M672 S105:254:1 sensitivity does not change (i tried it with fingers

Dougal1957

@c310 said in smarteffector sensivity - unable to change it:

in the documentations it is mentioned that after sending " M672 S131:131" LED should flash 5 times. my does not flash at all. However LED itself works: when i probe the bed with hands - LED flashes when nozzle touches the bed. And it does flashes twice when boot.

in my case smarteffector is configured before G31 in RRF3.2.2 by M558 P8 C"zprobe.in" R0.4 F1200

should i replace smarteffector board or it is still can be reprogrammed ???

Check your M558 command I think it needs the Zprobe.mod pin defining for you to be able to adjust the sensitivity.

"Note that RRF3 requires the pin names defined in M558 as well, so you must add C"zprobe.in+zprobe.mod"." (from the Smart effector docs on Commissioning)

hth

Doug

Lihyon

are you using a duet board with your smart effector ?
dropping the StrainEffector-v2.01.hex into my duet helped me to get the sensivity saved
https://github.com/Duet3D/SmartEffectorFirmware/releases/tag/2.01

c310

@Dougal1957 thank you! adding zprobe.mod resolved my issue!

c310

@Lihyon did you just uploaded it to system folder ? does it need to stay there or after reboot it can be deleted?

dc42

In order to be able to adjust the sensitivity of a Smart Effector connected to as Duet 2 running RRF, you need the following:

Pin Z_MOD on the Z probe connector must be connected to the MOD pin on the Smart Effector.
If you are running RRF3 then you must declare the MOD pin in the M558 command, for example:

M558 P8 C"zprobe.in+zprobe.mod" H3 F1000 T12000 R0.2

You must send the correct M672 command.

If those conditions are met then you should see the expected number of flashes from the green LED immediately after sending the M672 command.

However, if your Smart Effector has version 2.0 firmware installed then the new sensitivity will not be saved to flash memory, so it will revert to standard sensitivity if you power down and up again. This is fixed in the 2.01 firmware. The new firmware has to be flashed to the effector using a AVR-ISP. USB-ASP, TinyISP or similar.

garyd9

@dc42 said in smarteffector sensivity - unable to change it:

However, if your Smart Effector has version 2.0 firmware installed then the new sensitivity will not be saved to flash memory, so it will revert to standard sensitivity if you power down and up again. This is fixed in the 2.01 firmware. The new firmware has to be flashed to the effector using a AVR-ISP. USB-ASP, TinyISP or similar.

Is there any ability to verify the current firmware loaded on the smart effector (from the Duet using gcode commands)?

(I believe I have older firmware as I often have to re-set the sensitivity after power cycles.)

If I replace my smart effector with a new one, is there any way to ensure it has the newest firmware on it already?

dc42

@garyd9 said in smarteffector sensivity - unable to change it:

Is there any ability to verify the current firmware loaded on the smart effector (from the Duet using gcode commands)?

Not like that, but you can check it like this:

Use the M672 command to change the sensitivity, and verify that the green LED flashes 4 times to indicate that it has accepted the command
Power the effector off and on again, and count the number of flashes of the green LED. If it is 3 times, then the effector is using a custom sensitivity, so it has the v2.01 firmware. If it flashes twice then it is using the default sensitivity, so it has the old firmware. If it flashes 6 or 7 times then it is still initialising and you should wait until it flashes 2 or 3 times.

Your effector can be reprogrammed by someone with a suitable programmer or an Arduino, and spring-loaded pins. Which country are you in?

garyd9

@dc42 said in smarteffector sensivity - unable to change it:

@garyd9 said in smarteffector sensivity - unable to change it:

Is there any ability to verify the current firmware loaded on the smart effector (from the Duet using gcode commands)?

Not like that, but you can check it like this:

Use the M672 command to change the sensitivity, and verify that the green LED flashes 4 times to indicate that it has accepted the command

Power the effector off and on again, and count the number of flashes of the green LED. If it is 3 times, then the effector is using a custom sensitivity, so it has the v2.01 firmware. If it flashes twice then it is using the default sensitivity, so it has the old firmware. If it flashes 6 or 7 times then it is still initialising and you should wait until it flashes 2 or 3 times.

Your effector can be reprogrammed by someone with a suitable programmer or an Arduino, and spring-loaded pins. Which country are you in?

I'm in the US, and I'm sure I could get filastruder (or another auth reseller) to reprogram it if I'm willing to ship it (and be without a printer for > a week.) However, I'm not entirely sure what version of the firmware it's actually using so a reprogram might not do any good at all. The problem is that it it's not consistent.

I'd start another thread for this, but I think my issue very closely relates to the @c310 is experiencing:

There are times when my smart effector seems to lose its sensitivity setting. This usually happens after a power loss, but not after every power loss, and I'm not even 100% certain that it relates to power loss. When this happens, my Smart Effector shows symptoms similar to what @c310 reports.

For me, this is easy enough to determine because I have cheap linear rails. With a non-custom sensitivity, the smart effector triggers from normal movements. With a custom sensitivity, it works perfectly. When this happens, running either form of M672 (M672 S105:90:165 OR M672 S131:131) does nothing whatsoever. No Smart Effector LED flashes at all.

When I'm in this state, if I power down the machine, wait a few seconds, and power it back up, if I'm lucky, I get the normal non-custom sensitivity flashes. Then reprogramming it with M672 works as expected. If I change to a custom sensitivity and power down, and power back up, I get the 3 flashes (1 flash, pause, 2 flashes) as expected. Everything is fine for a few days.

Then, a few days or weeks later (usually after a power outage), I notice that my custom sensitivity has been lost and once again the smart effector stops responding to M672 commands.

(Part of the reason that I usually only notice this issue after a power outage is that I rarely run G32/G29. I usually do an autoconfig, save via M500, then a G29 and then only use G28 in my prints. After a power outage, I'm forced to run G32 again in order to use the mesh compensation - so I'll notice the smart effector sensitivity bad.)

dc42

@garyd9, from the symptoms you describe I am fairly sure that your effector has the old firmware, and reprogramming with version 2.01 firmware would fix it.