Im more than willing to try to reverse engineer the probing hardware and software that bamboo labs uses.
I have spent the last three hours trying to figure out what sensor they are using. They might use some sort of light triangulation. Not probable that they use lidar. These type of sensors at the accuracy needed are too costly and would account for 2/3 the cost of their printer. Or depending on the probe would be the entire cost of the printer.
Reversing their probe would be something like:
- Figure out what probe they are using.
- Connect this to the PI wire or USB. Obviously the Arduino cant handle this processing.
- Write the Python Script. This is not hard. Chat GPT and fiver outsourcing can accomplish this.
- Integrate script into config file.
- Calibrate probe.
- Design PA routine of some kind similar to Bamboo with scanning of the test print. Chant GPT and outsourcing can accomplish this.
- Test and tune.
Their bed sensing and PA sequence is really the major thing that sets their printers apart from the rest.
What type of probe are they using? Can someone that has a Bamboo printer supply a picture of their chip to get the manufacturing codes off of it.
I’m also interested in this topic and have tried to find out the kind of the sensor and also if Ali provides a similar one, unfortunately without result. Crealities K1 seems to have a similar system but also without any closer informations.
Hey @linuxpaul .
Ive found this link for the Creality K1 Max Firmware. This might shed some light in what is going on?
They state the following about the SBC:
“K1 Max adopts the smart Creality OS. It features a straightforward UI,
and syncs data and commands with PC, phone, Cloud, and add-on modules.
The snappy dual-core 1.2GHz CPU powers high-speed printing with ease.
The 8G ROM stores up to 400 model files and enables quick writing and reading.”
It sounds like they are using an ARM processor. I doubt they dumped money into developing their own OS and are utilizing debian or something at their core.
I downloaded the .img file and tried to mount it in a windows machine. I received an error. Which is not necessarily a bad thing and could mean that the file is formatted in FAT32. That should be a good indication that this is a pi image somehow.
I dont have a PI on me at the moment. My raspberry pi4 is across town. Ill have access to it in a few days. Anyone else have a way to see if they could install the Creatlity image on an ARM board of some kind?
update: this sensor looks amazing.
There are a number of things that make the optoNCDT 1220 impractical for 3D printers.
According to the datasheet and operating instructions:
- Power required is 2W
- Input Voltage range is 11V to 30V (24V seems to be the design point)
- Interfacing is more than just connecting three wires and power:
** RS-422 Serial with textCommands with responses (the default is in German which is good for some people here, but I presume it can be changed).
** Analog output of 4mA to 20mA (which is easily enough converted to a voltage and then I would compare it to an expected voltage rather than read the analog value)
- Dimensions of 20mm x 30mm x 46mm puts it on the large size for sensors
** It uses a triangulation technique so there has to be a clear light path of 40mm or so long
I’ve requested volume pricing for the product and will pass it along when I get a reply.
Thanks for the awesome insight!
This is the closest sensor I can currently find in my investigations. Most of the forums suggest that their is either a newer lidar technology that provides more precise positioning or Creatly/Bambo are using a triangulation sensor of some kind. Then letting the marketing departments run with the idea.
This might be a little large. Most hot end set ups seem to be big enough to support this sensor? I think my hotend is about 35mm deep with fans and such.
Ive also reached out to this company to try to get more information on variations and cost.
Just got a quote back: the optoNCDT 1220 is $1,359 for one, $1,311 in quantities of 100.
Pity, it’s an interesting part.
@mykepredko Thanks for the info!
Sounds like this is not the sensor of choice. Dang. Well Im not sure how to figure this out at this point?
We can at least rule this sensor out.