@my67nova:

What type of probe are you using? I was getting crazy numbers until I used a tiny micro switch

My IR probe gives repeatable trigger points to about 0.002, so that is not the issue.

@Nxt-1:

@dc42 I am using McHackney's latest FSR plate mouting system (I will attach a picture later today). If I understand you correctly there should not be any dropping back down on the FSR's, as the plate rests freely on the sensors.

@kswaid the picture in you post seems broken. I find it interesting that you use the the IR-probe and get the same results. This makes me believe that my problem is not sensor related, but something mechanical.

I changed the post to have the picture hosted on a different site, maybe it will work now. I agree that based on my similar results it does not appear to be related to plate tilt with FSR probing. I also should note that my printer seems to give nice results without grid mapping and I only tried it out of curiosity. There are some slight inconsistencies across the full bed area when printing, but then again I was unable to install the PEI without some bubbles in the adhesive tape. I had been hoping the mapping would deal with that.

FYI, I also tried reducing acceleration and probing speeds by 50% and noticed no change in behavior.

Your post made me curious enough to finally try height mapping with my machine. It is a Rostock Max v2 with tricklaser platform, arms, trick trucks, and uses DC42's IR sensor for Z probing (old version). I replaced my standard PEI covered glass with an unused glass piece for this test, sitting on top of a black painted aluminum heat spreader. My results are very similar but with greater max deviation. I get quite bad X axis banding. I haven't run enough cases to be sure but it does seem that the banding peak-peak distance tends to be a multiple of the probing pattern distance. I have also noticed a trend that max deviation increases with a greater number of probe points on my machine.

I also made sure all belts were tights, trucks were adjusted snug, pulleys set screws are tight, etc. At this point it certainly appears something is amiss with the precision of the Z tower motion.

ignore the general skew toward the Y tower and non-planar motion that I need to correct as well

Yeah, jumper is correct and I get the correct voltage on LEDA. A new panel is on the way from Filastruder and so it should be fully functional again shortly.

Spoke too soon, I guess it was simply luck that it was working because now it is dark again.

Had a hell of a time getting bossac.exe on my computer (ended up installing an old version of the arduino IDE) but finally managed to flash the updated firmware to the paneldue. Everything is back to working. I am glad I don't need to replace any hardware.

Will do. Thanks for the quick replies.

Yeah, I measure 3.3V on the controller and about 3.0 on the back of the panel where the screen print is labeled LED_A under Backlight Control. So I guess the problem must be the display. Time for an RMA or would a repair be possible? I can't say I am familiar with LCD backlight power circuits, but it can't be too complex.

I included a 4.3" PanelDue with my Duet Wifi order and finally got around to installing the system last week. When I hooked everything up it was operating basically normally except about 1 in 4 times I turned the machine on the screen would flash white and then go dark and stay that way. Over the week of use it has seen so far this problem has gotten worse to the point where it will never display an image (occasionally it will display the home screen for ~1s). The touch controls are still functional when this happens, or at least I can hear the audible feedback from menu selections. The cables and connections all look good, my power supply is stable at 12 volts, and in all other ways the Duet Wifi works perfectly. I have reseated the daughter board on the LCD header and made sure that none of the hardware has cold solder joints, a short, etc. Any ideas or did I just happen to get a dud?

Thanks,
Kyle