tpbh

About

Username
tpbh
Joined
Visits
6
Last Active
Roles
Member

Comments

  • Success. Thank you! I want to put the layer on my LCD screen. With M117 however it only briefly flashes on is there a way to keep it permanently on the screen for prints where the filament to be changed so I can monitor via web cam.
  • Thanks will try this. Fingers crossed.
  • Ok Thanks I didn't have that enabled in my config.h so will try later. Do I need to 'Enable G10/G11 retraction and filament change and allow jam detection' in the config tool. It seems to have settings for filament change i.e homing, X Y head posit…
  • I am sending it as a post processing script in simplify 3D and the code is changed at the correct level in the gcode (I have checked).
  • I print from an SD card and I use my LCD to control prints. So yes I want to change the gcode before I insert the SD card so the print pauses at a particular layer and then restart the print from the LCD. But when I insert M600 at the correct layer …
  • Interestingly when I lash version 0.29 I have 128kb of space but when I flash 1.0 it says I only have 64kb! Not sure why that is?
  • Ok will try. Would I be best to do that with G1 X 100 Y 100 then G32 or would I set that position in the configuration tool in the homing section?
  • Sorry I meant change the bed co-ordinates when probing. As my bed position is fine for printing, but when I activate G32 the X axis 0 position is more like X60. This is what is wrong. If I correct the P1-3 co-ordinates so they are ‘legal’ they run o…
  • No matter what I disable, LCD, SD Support, heated bed etc etc there is not enough space. Is there no way to change the internal probing co-ordinates in the firmware of version 0.92?
  • I’m just clutching at straws. So I assume now there is no way I can change these internal co-ordinates for probing in the firmware? Other than hope the Dev 1.0 has correct ones?
  • Yep suspected that☹️ Will play around and see. Can you comment on my suggestion of using g code in the probing start code to reset the X0 co-ordinate just before probing with a G92? Also could you check my host printer setting image …
  • Worked out error above loading dev 1.0 (Z probe pin was incorrect) But won't load to board here is my error message: Arduino: 1.8.5 (Windows 10), Board: "Sanguino, ATmega1284 or ATmega1284P (16 MHz)"C:\Users\tpbha\Desktop\STARTT Firware\Archive\Ne…
  • Just a thought in addition to above - would it be possible in the zprobe start code to locate the extruder to point 0,0 (ie G1) and set the co-ordinates to 0,0 with something like a G92 just prior to the G32 S2 ??? What I mean is just before the pro…
  • Just to check here is my host settings, but please see previous comment regarding the Dev 1.0 version problem. Thanks
  • Ok so I tried recompiling the 0.92 version from scratch. still probing incorrectly. I also input the probing co-ordinates as suggested my MartinH, so the first probe (@ X45) starts probing 2/3rds of the way across the bed at Y10. so XO probing point…
  • Is this the stable Dev software? As I have had issues here trying to flash the firmware which I posted on the forum. But I’ve had no response. See bellow: ‘I am having issues with bed levelling and I wanted to try the development firmware via t…
  • Hi Yes pretty much. Only difference is Home z is 123, as I have z max homing otherwise z0 would be 123 above the bed. And only other difference is Print area width is 150 as the -9 is not in the bed. Other wise Home 0 is at the front left bed.
  • Thanks for the input. Xmin Pos -9 is where the x min stop is ie 9mm to the left of the bed. So bed is at 0. I need XMax to be 158 so the extruder reaches the end of the bed (Right). The probe is unfortunately 47mm to the right of the ext…
  • I home to Z, X, Y. I did try the option you suggest but with Z Max homing it went up & down too much, so as Repetier Suggested I went with just Z, X, Y. I'm not sure whats happening. I can get my Z Probe height, but the 1st layers aren't good, i…
  • Thank you. I think my probe and my extruder don’t match up. My extruder has no offset (I.e X0, Y0 on the front left corner of the bed as you face it) my probe is offset to my extruder (X47, Y4). When I G1 X0 Y0 Z0 the extruder is at the front …
  • In addition to this question. I note that when I set my probing co-ordinates the X axis is centred on the middle of the bed ie the centre is 0, but the Y axis is 0 at the front of the bed. For everything else 0,0 is at the front left of the bed as y…
  • What should I do? Accept G32 height and change host? Even though working height (measured from z Max Home down to the bed) is different??
  • Sorry in EEPROM the new height is 132.048 the height shown on printer LCD 128.52 ( this is with the bead coating subtracted (3.53)
  • I’m still having a problem. I set the Z height both in EEPROM and the host. I also have my bed coating set. The calibration for the z probe height is loaded to EPROM. and all is set. I then perform a G32 S2 Following completion of homi…
  • I think it would be worth a video like was done for the Delta bed levelling. As I don’t seem to be the only one having these issues. I know the instructions are pretty clear, but sometimes for those of us less mathematically gifted a picture/video s…
  • Thanks. Here’s hoping my next print is levelled.
  • Yes ENDSTOP_Z_BACK_ON_HOME 2 has been set. So after many tweaks by using the bed coating function I have now achieved a good print. I just hope it continues without needing any further adjustment. (It took about 3 hours of homing to ZMAX and then to…
  • I assume I have done my calibration calculation correctly. I’ve had real issues correcting z probe height. I’ve tried taking z to 10mm off bed and stepping down to find the difference. When I set this into my EEPROM Z probe height it makes no differ…
  • I’m still having issues. I just can’t seem to calibrate my z probe correctly. I have followed your instructions both here and the online z probe calibration instructions. My printer is now doing all movements as it should. I have also physi…
  • In fact I have done a G30 following a change in EEPROM as per the online instructions this was following a G31 to verify the probe. It made no difference.