Well the problem with the T10 is no longer a problem, as the replacement has arrived, and working OK.But I do have a problem that I cant figureout.The nozzle just keeps pushing into the bed, no matter what Z offset I put in.I will try to reload Marlin to see if the problem is with that.But any suggestions will be much appreciated..Thanks

Pro's and Con's.Pro's, in general it is a great system all round, I love it.Con's, the main one for me is the fact that I can't use the Bluetooth keyboard, the Android one Sucks big time, hides up some of the things you are trying to change.The size of the adjustment buttons, is a major drawback which the Bluetooth keyboard would fix, needed if you have large fingers, or a lady with long nails.This is being sold as a going product, so it should take priority, over the free Mattercontrol, as far as I am concerned once you sell it in what type of form, it is no longer free. Would anybody buy the blank tablet.If anything turns me away from this it will be this factor.

Sussed it. Printer is on ttyUSB0 not on ttyASM0Still getting errors though:Attempting to connect to: 192.168.1.14 on port 2323Connected to: 192.168.1.14 on port 2323->Communication State: AttemptingToConnect->N1 M110 N1*125->N1 M110 N1*125<-echo:Unknown command: "ÿû,ÿú,
"->Communication State: Connected->N1 M110 N1*125<-ok<-echo:Unknown command: "S0"<-ok->N1 M110 N1*125<-echo:Unknown command: ""<-ok->N2 M114*37<-ok<-X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0<-ok->N1 M110 N1*125<-ok->N2 M115*36<-FIRMWARE_NAME:Marlin SkyNet3D-V2.3.2 (Github) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:SkyNet3D EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff<-ok->N3 M114*36<-X:0.00 Y:0.00 Z:0.00 E:0.00 Count X:0 Y:0 Z:0<-ok->N4 M104 T0 S0*37<-ok->N5 M105*34<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N6 M105*33<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N7 M105*32<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N8 M105*47<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N9 M105*46<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N10 M105*22<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N11 M105*23<-ok T:16.2 /0.0 B:16.4 /0.0 @:0 B@:0->N12 M105*20<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N13 M105*21<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N14 M105*18<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N15 M105*19<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N16 M105*16<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N17 M105*17<-Error:No Line Number with checksum, Last Line: 16<-echo:Unknown command: "0"<-ok->N18 M105*30<-echo:Unknown command: ""<-ok->N19 M105*31<-Error:Line Number is not Last Line Number+1, Last Line: 16<-Resend: 17<-ok->N17 M105*17<-Error:No Line Number with checksum, Last Line: 16<-echo:Unknown command: "0"<-ok->N18 M105*30<-echo:Unknown command: ""<-ok->N19 M105*31<-Error:Line Number is not Last Line Number+1, Last Line: 16<-Resend: 17<-ok->N17 M105*17->N17 M105*17<-echo:Unknown command: ""<-ok->N18 M105*30->N18 M105*30<-echo:Unknown command: ""<-ok->N19 M105*31<-Error:Line Number is not Last Line Number+1, Last Line: 16<-Resend: 17<-ok->N17 M105*17<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N18 M105*30<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N19 M105*31<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N20 M105*21<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N21 M105*20<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N22 M105*23<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N23 M105*22<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N24 M105*17<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N25 M105*16<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N26 M105*19<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N27 M105*18<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N28 M105*29<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N29 M105*28<-ok T:16.3 /0.0 B:16.4 /0.0 @:0 B@:0->N30 M105*20<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N31 M105*21<-ok T:16.2 /0.0 B:16.4 /0.0 @:0 B@:0->N32 M105*22<-ok T:16.4 /0.0 B:16.4 /0.0 @:0 B@:0->N33 M105*23

:oops:

Ryan,I have sorted the probe problem, it seems it did not like two statements at the head of the start gcode, namelyM10y64 S and M104 S, removing these solved the problem.Other problems are with the support, these do not break away very well, they were ok before this update.Also fixed in the earlier update, the bluetooth Keyboard, does not work in this later version.Also mention earkier opening files in the cloud, does not work on the T10, but ok on the desktop computer.The next two problems are most likely settings, so if someone could give me an idea it would be great.Flat surfaces on the bed print very rough, walls are fine.Printing tube, the bottom few layers swell out to a height of around 3 mm.Tried to load the gcode file as a zip file but it did not work, so will send it via email.

Does 1.5 address the issues with intel chipset video cards?

That turns out to be true, but it does not alter the fact that the given figure of 0,6 recommended in the help file, is misleading, a more appropriate figure would be 0.1.

@michael-petitclerc , thanks so much for your assistance.

@CDNBACON The patch was not released to the Stable build yet so you will have to update to the Alpha version of the software to get the patch. Let us know if you do happen to still have issues after upgrading to the Alpha. Thanks!

Thanks for the feedback. We have an issue in GitHub for the re-slicing and will git it fixed for the next release. We are also working to improve support, now that we have this new system. You should still be able to create support everywhere. If there is a specific model that is not generating support correctly, filing an issue in GitHub and attaching or linking to the model is the best way to let the developers know. We know you come to depend on our software working correctly, and that it is very problematic when there are bugs. We will work to correct these things as soon as possible. Thanks again, Lars.

Hi Lars,the Alpha is already installed and printing PokeBall bottoms. I am liking all the new features!!!!Thanks again for your great support!!!!

Yes I calibrated them.using a calibration cube.

@michael-petitclerc Done.

Sorry. We tried to replicate your issue using our Flashforge Creator Pro, but we were not able to do it. Maybe there is some difference between the Flashforge and the CTC that we are not aware of. Without having one here for testing, there is not much we can do.

@rsteel517 how do we manage z offset with this gcode?

Okay here we go. I put things back together and started calibrating again. Test cube: A little elephant foot action, some gaps in the top layer. Then a benchy: This is the worst side, odd dents, seems like an extrusion/temp issue maybe. The Mini Torture Test (https://www.thingiverse.com/thing:2975429 ) Not great, for comparison here is one from my Anet A8: Plans: up retraction to 6mm from 4mm AND to move this to a calibration thread. Thank you all for your help!

Now my wilson is printing great since the update. MatterControl, thanks for the input,i am now a control freak

Not sure how those high values could have gotten in there, but I'm glad you have it worked out now.

@wpsdlulz, does MatterControl still show that it is connected to the printer at that point? Can you move the printer manually through the motion controls? If you could post a print log from a failed print, it might shed some light on what is going on.

At the moment MatterControl does not work this way. I created a feature request for this, so it will be up to the dev team as to whether or not they want to proceed with making this happen: https://github.com/MatterHackers/MatterControl/issues/1861