Knomi v2 vs Eddy Coil conflict

Basic Information:

Printer Model: Voron 2.4 r2
MCU / Printerboard: Manta MP8 v2 + CB1
klippy.log
klippy (14).log (174.1 KB)

My equipment:
Voron 2.4 board Manta-M8P v2 + CB1, head Stealthburner with EBB SB2240,
Eddy Coil ,Knomi v2
Eddy coil is connected to the i2c on the EBB SB2240 board (you may have a question how? SB2240 does not have i2c the solution can be seen in another discourse called “Manta MP8 v2 shutdown: i2c timeout”)
Knomi v2 is connected as usual via wi-fi
Eddy coil is configured, works fine, scans and levels the table!
I noticed that when Eddie is turned on, Knomi loses Wifi

SO
Eddy coil is connected to the i2c on the EBB SB2240 board
Knomi v2 is connected as usual via wi-fi
I disconnect the 5v power supply from Eddy Coil
Knomi appears Wi-Fi
@mykepredko I know you have knomi
video problem

I have two Knomi’s on my printers, one on my Voron 2.4 and the other on a home brew bedslinger. I am not using Eddy Coil at this time time. Sorry.

You’ll probably have to look around to see if anybody has a similar problem.

When you start a question in “General Discussion”, always include your klippy.log.

And so the first thing that came to my mind is a weak 5v power supply!
I checked what power the SB2240 board provides 4.95v.
It seemed to me that this might not be enough for a Wi-Fi receiver!
and so I found a 5v step-down converter and changed the setting resistor 10k to 9,53K to raise the power supply.

in the end I got 5.15v. but it didn’t give any result!
still when turning on Eddy on Knomi the Wi-Fi is weak or not at all

this is 100% a problem not in the Klipper settings!
config will not help! because this is a problem of not displaying and connecting to the printer! this is a problem of connecting Knomi to the Wi-Fi router! because Wi-Fi weakens on Knomi

Knomi must first connect to the router to get a network, only then it connects to the printer!
if there is a problem connecting to the printer, this error is displayed by knomi differently
now it just searches for Wi-Fi! it seems that as soon as I bring knomi into the aluminum case of the printer, it immediately loses Wi-Fi

it feels like the printer’s aluminum frame is interfering with the wi-fi signal! but for some reason Eddie is involved in this! because as soon as I turn it off, the wi-fi appears!

It’s convention, highly recommended and often required.

Please always include your klippy.log.

I’ve been looking for a similar problem everywhere! But it seems I’m the first one who installed an eddy coil next to a knomi! Since everyone installs an eddy usb
maybe the eddy usb circuit is different and there is less interference

ok added klippy log

I searched for a long time for the reason before I decided to turn off Eddy Coil!
At first I thought there was a conflict between the СB1 and Knomi antennas, I turned off the СB1 antenna, but to no avail! I replaced the Knomi antenna, but to no avail! I changed the Knomi firmware, but to no avail! I connected a separate 5V power supply to Knomi, but to no avail! The problem can only be solved by turning off the Eddy power supply

Let’s say Knomi is bothered by Eddy electromagnetic interference! But Eddie only emits magnetic fields when he works! I even thought about making it so that Eddy turns on only when he works! But this needs to be programmed, install a relay that will turn on Eddy power only when he executes a work macros

what I think: take a free pin from SB2240 and program it so that it turns on only when Eddy executes macros or commands like

PROBE_EDDY_CURRENT_CALIBRATE CHIP=btt_eddy
QUAD_GANTRY_LEVEL
BED_MESH_CALIBRATE METHOD=scan SCAN_MODE=rapid
PROBE_ACCURACY

i.e. in fact I want to give 5V power to Eddy only when it participates in these cycles, otherwise it should be turned off
as I understand it, I need to get into the code and add on/off pin to all these commands at the beginning and at the end of the code! right???
or so that before starting i2c on SB2240 the pin is turned on.
or somehow write the code so that everywhere where the LDC1612 sensor is involved, before using it, the pin on SB2240 connected to the transistor switch is turned on!
Please tell me how to implement this crazy idea more easily) because I am not a professional in programming!

it turns out there is some potential on the Eddy power wires! when I lightly touch the negative power supply of Eddy, Knomi starts to catch Wi-Fi!!!
Sometimes you just bring your hand close to the wires, without even touching them, and the signal appears

Knomi has an internal network test! When you press the Reset button 3 times, the test is turned on and it shows that the signal is really very weak!!!


There is definitely a need for a magic glass ball, to debug WiFi on Knomi.
There can be a bad antenna design that can be placed over the ground.
There carbon fancy cage which definitely blocks RF.
Or, maybe there is no common GND between everything on the head.

Nothing I can suggest here, but if you are sorely sure that ldc1612 is a reason why Knomi lost WiFi.

TLDR,
I checked the datasheet, and ldc1612 can be returned to sleep mode.

But I’m not sure it will help because on a fresh start eddy sensor should just sleep, before homing sequence, and only after the start of the homing sequence, it can start to affect something.
So, your videos with lost connection after power on look weird.

it’s not carbon) it’s abs printed on a carbon plate)

I changed the antenna to another one, no result

It’s a pity that there is no electrical diagram of Eddy(((
My opinion is that Eddy coil is the cheapest, it doesn’t have a microcontroller and it’s not known who controls the LDC1612 chip inside! Maybe it emits something

@ nefelim4ag
Can you please look at the firmware code for Knomi v2??? It’s publicly available! Maybe there in the Wi-Fi library you can boost the signal or change the range!?!?!?

Nope, this is far over Klipper or anything related to it.

I’m thinking of buying a 4-Wire FAN and connecting the SB2240. for blowing the extruder
and use the Fan1 transistor output on the SB2240 to turn on and off the 5v Eddy.
The biggest question remains how to programmatically implement turning on and off the Eddy when all the commands associated with the Probe are used