Roxy-3D
commented
7 years ago @lrpirlet I don't know what a M133 command is. But the G29 W in the second link says you have a 9 x 9 mesh. I looked at the various G29 T commands you gave it. I do not think the mesh data is changing. I think data is getting lost as it is being transmitted to Repetier Host.
Probably, we should be using map type 0 to debug this for several reasons. First, that outputs more characters and does it with less delays between the title or header characters. And secondly, that is more human readable so it will be easier to see if data got lost.
I use PronterFace and do not see a problem. There are a couple of things we can try to get the map to print out better and not lose data. First you can try changing in Configuration_adv.h to have
#define TX_BUFFER_SIZE 32because that will cause
void unified_bed_leveling::display_map(const int map_type) {
...
#if TX_BUFFER_SIZE > 0
MYSERIAL.flushTX();
#endif
safe_delay(15);Waiting for the RS232 Transmit Buffer to flush will probably slow things down enough you don't lose data.
The other thing you can do is change that safe_delay(15) to safe_delay(50) in the display_map() function to slow the map generation down enough you don't lose data.
And I hesitate to ask this... Because it is a total pain in the @$$. But you could try installing PronterFace and use that. Like I say... I use PronterFace and do not see the problem.
We can also try lowering the baud rate in Configuration.h but that would be a very last ditch thing to do.
/**
* This setting determines the communication speed of the printer.
*
* 250000 works in most cases, but you might try a lower speed if
* you commonly experience drop-outs during host printing.
*
* :[2400, 9600, 19200, 38400, 57600, 115200, 250000]
*/
#define BAUDRATE 57600Please let me know what you see as you change things. OK?
lrpirlet
repetier
apelly
davidelang
jbrazio
github-actions[bot]
Background
I am using the latest bugfix-1.1.x (0b6b7c9) to build my firmware for my Prusa i3 printer...
Configuration.h is the only customized file and is accessible from https://github.com/lrpirlet/Marlin/tree/lrp-2-jun-2017 under https://github.com/lrpirlet/Marlin/blob/lrp-2-jun-2017/Marlin/Configuration.h
I issue an M133 S30 to avoid "echo:busy: processing" in the middle of mu disered output... I Issue G28, G29 P0 followed by G29 P1... I issue G29 W to log the G29 characteristics... All the above without any problem...
Issue I send G29 T1 several time and got different results... or rather I DO MISS some values at DIFFERENT places in each of the outputs.
extracted from https://github.com/lrpirlet/Marlin/blob/lrp-2-jun-2017/logs/Repetier_log.txt please find here the evidence for G29 T1... G29 T0 also missbehave...
Questions
Does anyone else see that behavior???
Since the difference between the 3 commands G29 T1 is just a different time, could we see some interrupt misshandling... I am completely at lost, and would appreciate some help...
Last but not least,
Thanks in advance.