I couldn't connect to a wifi connection that did not have a password. It would see and even remember the wifi connection name but it wouldn't actually connect. I tried (p"") and even just network name without (p). It never output an IP address. This is what I ran into when I took my 3d printer to teach that lithophane class. Luckily I had a paneldue. So the actual class went fine.

dc42 are you saying it can't display a photo at all from the sim card. I thought these LCD's are capable of showing photos. If the web interface was ever able to do it than it could send it over to the panel due as a picture. Also we could make the pictures ourselves and as a small thumb. I just have a lot of models with similar names and I have been loading it up in a model program just to make sure it's what I want before a print. It would be nice for the small thumb to display on the control page of paneldue in the blank upper right hand corner.

Are there plans for the PanelDue to have a preview of model it's printing like some of the other displays we see out there in the world?

http://www.escher3d.com/pages/wizards/wizarddelta.php

https://configurator.reprapfirmware.org/

Just a follow up. I wanted to show how close I've gotten it to be exactly what it's supposed to be. I haven't re-calibrated it since I posted the other day on 6th of Nov. I wanted to print out some brackets I made to mount something together. I have these set on lowest quality, but it's looking pretty good. Even printed four at once and they came out really close to the same… Not really a difference to talk about..

The X is a small bit off hardly noticeable, but Y and Z couldn't get more accurate lol... My first post at top talked about egg shaped holes. Looks like everything is working top notch now. thanks for everyone's help!!!!

I was just about to ask this by making a new thread. Glad you did so before me Mine keeps changing and it's annoying

@Dougal1957:

If you insist on using the Config -Overide file then you do need to load it after a boot with M501 else how does the board even know about it?

Put M501 as the last line in your Config.g if you must use but what you have found is the very reason that most of us DO NOT USE the config-Overide but prefer to hand graft the figures into the Config.g instead

Doug

Thanks for your reply!!!

I use the M501 command, but yeah good point I should just as you say hand graft the m665 and m666 commands into config.g. I do however would like to help the engineers work out bugs or improve things. I feel like I am possibly helping their product. I think of it like this. My last board and the people behind it stopped making the board and with no support at all. It was costly and an inconvenience of time. Me helping correct issues in this product would ensure that a few years from now i'll have an easy upgraded replacement Just swap out and continue.

I've always since you told me been using m500 before rebooting. More importantly like I said your auto calibration was saving the corrected homed height in the override file, but until I used the corrected height that auto calibration came up with in my config.g file the values the auto calilbration was using was off because it didn't use the corrected homed height from the override file.

I assume your auto calibration script uses only config.g (H) and not config override (H) parameter every time it runs. So if you have a config-override enabled in config.g than it should ignore config.g (H)

The simplest way to hear my findings for a fix for now would be "Make sure your config.g (H) parameter is correct before running auto calibration". A person can definitely find the correct (H) parameter by running the auto calibration, but they need to change the config.g to the new corrected height.

Again I ran my test over and over for the last 7 days every day all throughout the day and until I changed the (H) parameter to actual correct height from bed to the home position in config.g the auto calibration did not act correctly on getting the parameter values for (R)(X)(Y)(Z). Auto calibration was never using the (H) parameter in config-override.g while doing auto calibration. This is only my experience. I am just trying to help.. The important thing is that I have my printer working correctly now going by the methods I explained above.

dc42 I like this board! I do appreciate your hard work, don't forget that. It means alot to me knowing the guys who made the electronics I'm using are willing to keep making their product better

Ok guys I am here to report that I have calibrated this officially a thousand times now forward and backwards

The problem that throughout this post that threw off all values during auto calibration was due to lastly not setting the H parameter to it's height as close as possible in config.g. I kept thinking that auto calibration was handling that. It would set a corrected height but all the other values it would throw off like x and y degrees and delta radius etc.. My guess is it had a corrected height but the rest would use the config.g height… Atlas after measuring everything forward and backwards this solved the inaccurate auto calibration.

I hope this is another bug that can be remedied some how. Atleast I know now what is going on...

So what I am saying is after your first few auto calibrations on a delta and it's also true for new changes to your bed height. Look at what the height is changing to when auto calibrating from the overridefile or the m665 command. Then incorporate that into the new height in config.g. Then do auto calibration a few more times. repeating that cycle. Also be sure to reboot every time. And remember to use m500 to save last configuration etc. Use configuration override command M501 in config.g..

After setting my L parameter to exactly what I measured in both config.g and configoverride and set H to exactly what it really is from home to bed in config.g. This made the rest fall in to place. I had measured the delta radius so I now knew if the auto calibration was getting the right numbers !!!!! It's now setting the values in config override to all things within .3mm or closer. My prints are back to being right. Matching the model file pretty close...

Now hopefully the squareness/trapezoid issue will be resolved... If not then I'll continue to see whats up with that. Like every rod needs to be perfectly the same..