How about a readout on the printer after the LiDAR determines the PA so we can see what value it’s using.
3 Likes
Same idea I was thinking about. If using the AMS with non-BambuLab-materials it is testing one material only. And it is difficult to take influence, witch one of the slots will be checked.
So, by taking the results from the LiDAR and put them into the maerial presets would be a great way to ashure best print quality.
Even better, if the X1 would communicate with Bambu Studio and update the presets (after asking the user)
Anybody in developpment-department who can take care on these firmware-feature propositions?
Thank you!
4 Likes
Exactly, seems like it would be pretty easy to implement.
1 Like
Applies not only for dynamic pressure, but also flow factor. I believe it is measured too before test stripes are scanned for dynamic pressure results.
And numbers from mesh bed leveling would be nice as well.
Generally speaking, for me it would be sufficient if the log files exported to SD card were not encrypted. I’m sure they contain all the information we need.
1 Like
It would be nice if it would be that way - but even the potential ‘silent’ fail and not working on textured PEI let me to OrcaSlicer and its build-in calibration tools.
Once I run the filaments through it, I don’t need Lidar etc anymore.
Anyway - we may still hope for the future.
1 Like
Same here. LiDAR might be a nice thing, if it would work. May be it does work with certain type if print plates, but who knows. If LiDAR does not detect plausible numbers, it will use default values. Which are probably ok as well, but not the best you might get. Therefore, I am also using OrcarSlicer’s configuration stuff. As for showing the values detected, best option (and easiest) is to open up the firmware and enable M503 command which, as per Marlin, “prints a concise report of all runtime-configurable settings (in SRAM) to the host console. This command reports the active settings which may or may not be the same as those stored in the EEPROM.” This is the usual method to obtain data from printer.
If only there was anything like host console on X1C. 
If the FW would be open, you can use pronterface for that.
1 Like
Agree, it would be very nice to get some information about the sensor measurements! At LEAST there should no things like “silent fails”. If for example the lidar scan fails and fallback values are used, they should at least be set-able.
The best solution would be an integrated filament (or spool) management tool. For example the problem with lidar and the PEI sheet: You can run the lidar and flow measurements on the standard cool plate (where lidar works most of the times), store the values in the spool database, and use these values until a user triggered re-analysis.
Just my two cents, but I think a LOT of users (especially the “pro” ones) would be very thankful for such improvements. Especially because the data is already “here”, only the presentation to the user is missing…
Thank you!
1 Like
Totally agree here. Ive seen people able to calibrate value for the AMS per filaments, but it’s lacking on the X1C without the combo. We don’t know the value used and unable to store the value, although understandable that the idea is calibration per print. But by being able to know the value of the lidar vs manual calibration, I think this would help advance user to get the best value that would yield better prints.
1 Like
Hopefully they will implement this. If they even read these requests…
I had this same request a couple months ago and another user basically told me I was a moron. I think it would be a lovely addition to the software!
In all honesty though, I had asked for this politely because i’m still not convinced this “microlidar” actually functions the same way that it was marketed.
Jeez, I only started printing 1 week ago and can’t believe this critical information can’t be read? I love what they’ve done but this is a no-brainer feature. Been searching the web be nothing.