-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kippler support #1
Comments
Seems will wait for more time, Since I am not familiar with klipper and python, also try to looking someone help to supporting. |
hi there, working on klipper support for the sensor but cant even connect the probe for any reason. Its connected to the raspebrry PI`s I2C connector but i2cdetect cant find the device. PI SDA -> Sensor SDA device seems to work, i can see the LED when putting some metall piece to the sensor any idea? |
The device has a 5V VIN, but does the device uses a 3.3V or a 5V I2C connection. Cant find any information on it |
I tried it with an Arduino I2C scanner nd found this if the device is connected to the arduino it returns an derror for these addresses Unknown error at address 0x51 |
there is a different from the standard I2C. See this timing diagram of this sensor https://github.com/markniu/Bed_Distance_sensor/blob/main/doc/images/0220517153950.png , for increasing the speed, there is no I2C address transfer in the timing diagram that's the difference from the standard I2C.
in the platformio.ini |
ok, thank you |
this device is 5v I2C connection,but can work with normal 3.3v MCU like stm32 which most gpios are 5V tolerate |
nice it works, getting the first readings. will play a bit with it and let you know when i need more infos |
look forward to |
Python module finished :-) |
wow, nice work! |
Thats not good. I just realized that this sensor will most likely not be supported by klipper naytime soon. Problem is the unusual I2C communication the sensor uses. We cant use the inbuilt I2C micricontroller code from klipper to connect to the device, a microcontroller implementation just for this sensor seems unlikely to be approved by the klipper mantainers. So a real implementation is not likely. |
is it possible to change the firmware of the sensor to use standarized I2C communication? |
it can not be flashed firmware from the i2c port. |
i am trying to implement it atm |
yes, on a microcontroller level |
good job ! I am editing the wiki document about the calibration that maybe you needed |
yes, working on the calibration, having also some questions. will ping oyu in the nbext days |
Have updated the document which contains the calibration process. |
Hi @HelgeKeck @markniu, may I know what are the configs for Klipper implementation? |
I was wondering, could we simply use a MCU to connect the sensor to klipper, like we can do with the ADXL345 sensor (for resonance compensation)? Would it solve the issue with the unusual I2C protocol, or would it be too slow to react? |
@JayBee-git I was also thinking the same but not sure how Klipper will read the data from sensor. I'm also looking into it. |
@ashbuilds true, I know serial can be used in klipper but that would probably require to change some code. BLtouch is going through the printer motherboard which is a MCU as well, so I bet there is something that can be done here. Maybe even connecting the BDTouch to the motherboard could work? |
The output of the TCA 305 sensor chip is a simple open drain already. What is the point of using a custom protocol with a micro controller here instead of simply exposing the output of the sensor directly? I am sure you have good reasons @markniu but it would be nice if you could explain them. |
Awesome! |
yes, I also test with the pei + steel + magnet on the bed |
sorry for that delay maybe still need about 2 weeks for the support klipper software, since most of my family got the covid19 last 2 weeks and all recovery fine now. I will have more free time this month from now on. |
Here is the beta version of Klipper that support Bed Distance Sensor |
That's really cool, thanks a ton for your work! |
Is it possible to use with Mainsail? |
is there any chance for this to be included/accepted into the official klipper repo? |
I am not use the Mainsail before, but I think it's no problem to work with mainsail for that all the changed source code for BDsensor are in klipper side. |
I will commit the changed source code into official klipper github after doing more test |
The code has been pulled to klipper github: Klipper3d/klipper#6031 |
waiting for it to be approved to buy a few sensors. PS: I believe you need to sign-off with your full real name (no alias) |
That's awesome! I will try it out asap, thanks! |
@markniu I'm interested in this sensor as I find my current solution inadequate, but am not really interested in keeping a non-mainline firmware installed on my printer long-term. Do you still plan to try and submit a PR to Klipper master at some point? I don't see any commits to your klipper fork since 5/15. I am familiar with Python and C, so if there's anything specific that needs refinement on the fork, if you create issues for it I can take a look. |
@markniu @henryrgithub There is a new PR at Klipper3d/klipper#6490 (comment) that needs to incorporate some requested changes. From my feeling, if those are done, the chances would be good to get it finally into mainline! |
The main thing I see glancing over it is the effort to use a non-sensor-specific probe functions, or at least just have the functions shared with other current eddy sensors. Seems like a reasonable lift, I'll take a look at it this coming week. |
Any chance you add Kippler support?
The text was updated successfully, but these errors were encountered: