Page 1 of 1
z0 question
Posted: Wed Feb 27, 2013 2:27 pm
by rs50pilot
New Max build using Rambo 1.1b
polygonhell's firmware
I am trying to set Z0.
I heated the nozzle to 240
Bed to 90 which takes forever (20 mins) and I have a 30 amp 12v power supply gonna see if I can get more voltage out of it.
Anyhow, G28 the axis move real fast and when they hit the limits and then back up it seems as if they they are traveling in rapid when they back up to kit the limits again?
When I used the stock firmware g28 would rapid to the limits hit them, then feed slowly to hit the limits again.
Seems as if it is to fast and I am not getting a accurate trip of the switch.
I will use the feeler and the z height in the the host software says 1.20mm so I subtract that from the value in the config H.
G28 again and Z0 is still above the spot where it is supposed to be. So I will adjust it again in the config h. It was only off by .9 from 1.20 the first time I set it.
Now in order to change the config H for the z height I do have to exit repeiter and go to the arduino IDE to make the change?
On the repeiter site it says you can use or diable the eeprom and send a command (dont have my notes with me) to tell the software to use your config h settings and not the eeprom.
My main problem is that when I exit repeiter to change the config H value I have to turn off the bed which drops about 10 C in the time it takes to make the change and get back into the host software to continue the calibration. Then I have to wait for the bed to get back to temp before I can measure Z0 again. It's making me crazy.
So it there another way to change the setting and keep the bed hot?
Re: z0 question
Posted: Wed Feb 27, 2013 3:50 pm
by aehM_Key
Enable EEprom-Mode and change the values with Repetier Host in the EEprom directly.
Re: z0 question
Posted: Wed Feb 27, 2013 4:14 pm
by gabrielk
in configuration.h you can find something like this to slow down second move when homing. i change my factor to 16
// For higher precision you can reduce the speed for the second test on the endstop
// during homing operation. The homing speed is divided by the value. 1 = same speed, 2 = half speed
#define ENDSTOP_X_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Y_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Z_RETEST_REDUCTION_FACTOR 2
i
Re: z0 question
Posted: Wed Feb 27, 2013 6:09 pm
by rs50pilot
Thank you guys for the info,
So to be sure I can change EEPROM_MODE 1 to say MODE 2
Open the Repetier give a M502 command (if I remebered that right) and it will switch to use the mode 2
then the M205 to give a list of the commands
Then if I want to change say
EPR:3 3 40.00 X-axis steps per mm
I would enter
M206 T3 P3 X 50.00 then hit enter.
and this would change the x-axis steps per mm to 50.00?
Also do I have to give the M502 command everytime I open the host software?
Re: z0 question
Posted: Wed Feb 27, 2013 6:17 pm
by Polygonhell
Repetier host has a nice dialog box where you can edit all the EEPROM values.
On a Mac the hot key is Cmd-E I'm sure on Windows it's similar.
Re: z0 question
Posted: Wed Apr 10, 2013 4:41 pm
by skyspy
Hi!
I changed to Polygonhell's firmware because it is the only way to get my LCD working.
But now my z0 position is more than 20 cm above the bed level. And I just don't know which value I have to change.
Here's what I've tried so far: (My Z_HOME_POS with the Marlin firmware was 373.0)
Configuration.h:
#define X_MAX_LENGTH 373.0
#define X_MAX_LENGTH 373.0
#define X_MAX_LENGTH 373.0
I also tried to change these values in the Firmware EEPROM Configuration in Repetier Host.
But nothing changed.
Please help!
Thanks,
Sigi
Re: z0 question
Posted: Wed Apr 10, 2013 4:46 pm
by cambo3d
skyspy wrote:Hi!
I changed to Polygonhell's firmware because it is the only way to get my LCD working.
But now my z0 position is more than 20 cm above the bed level. And I just don't know which value I have to change.
Here's what I've tried so far: (My Z_HOME_POS with the Marlin firmware was 373.0)
Configuration.h:
#define X_MAX_LENGTH 373.0
#define X_MAX_LENGTH 373.0
#define X_MAX_LENGTH 373.0
I also tried to change these values in the Firmware EEPROM Configuration in Repetier Host.
But nothing changed.
Please help!
Thanks,
Sigi
you also need to change your print settings for it to show in the host program. not just eeprom
but even if you do that, host display of z height isn't accurate. you have use m114 to exact position.
Re: z0 question
Posted: Wed Apr 10, 2013 4:51 pm
by skyspy
Sorry I forgot to mention that I also did adjust the printer setting in Repetier host. But no matter what I do, the carriage stops at the same height (approx. 20 cm above the bed).
Re: z0 question
Posted: Wed Apr 10, 2013 4:56 pm
by cambo3d
skyspy wrote:Sorry I forgot to mention that I also did adjust the printer setting in Repetier host. But no matter what I do, the carriage stops at the same height (approx. 20 cm above the bed).
your probably not using eeprom then, the eeprom values override the firmware values. looks like your using firmware to change the values. rep firmware default is eeprom.
to do this change your z heights in eeprom menu in rephost, you can do this as long as you didn't disable eeprom mode.
Re: z0 question
Posted: Wed Apr 10, 2013 5:02 pm
by skyspy
Well - that's the strange thing. It does neither work if I change it in configuration.h with arduino 1.0.3 nor when I change the values in eeprom menu in rephost. As far as I understand this either the values from configuration.h or from eeprom should work depending on which mode I use.
Re: z0 question
Posted: Wed Apr 10, 2013 5:10 pm
by cambo3d
skyspy wrote:Well - that's the strange thing. It does neither work if I change it in configuration.h with arduino 1.0.3 nor when I change the values in eeprom menu in rephost. As far as I understand this either the values from configuration.h or from eeprom should work depending on which mode I use.
ok well you need to decide how you want to change those values first. remember if your using firmware you need to disable eeprom mode, if your doing it in rephost leave eeprom enabled. can't have a mix of both but i'm assuming you know this already.
try this:
reflash firmware with the defaults.
go into rephost and do your z height adjustment again.
once it reaches zero, depending on your z height you will need to add/subtract numbers from the eeprom numbers. Then. rehome, and jog to zero and see how close you got.
you might have to do this several time until your close.
Re: z0 question
Posted: Wed Apr 10, 2013 5:28 pm
by Bill Havins
Look at line 130 in the Configuration.h file. Does it read: #define MICRO_STEPS 8? If it does, change it to: #define MICRO_STEPS 16, re-compile, uplaod to your RAMBo, and try again.
(I don't think I saw this adjustment in your description, above. The 1.1+ RAMBos use 16 Micro Steps instead of 8. Maybe this will help,...or not.)
Good luck!
Bill
Re: z0 question
Posted: Wed Apr 10, 2013 5:30 pm
by cambo3d
Bill Havins wrote:Look at line 130 in the Configuration.h file. Does it read: #define MICRO_STEPS 8? If it does, change it to: #define MICRO_STEPS 16, re-compile, uplaod to your RAMBo, and try again.
(I don't think I saw this adjustment in your description, above. The 1.1+ RAMBos use 16 Micro Steps instead of 8. Maybe this will help,...or not.)
Good luck!
Bill
true dat bill.. diffinitely make sure your steps are set right
Re: z0 question
Posted: Wed Apr 10, 2013 6:39 pm
by cassetti
Bill Havins wrote:Look at line 130 in the Configuration.h file. Does it read: #define MICRO_STEPS 8? If it does, change it to: #define MICRO_STEPS 16, re-compile, uplaod to your RAMBo, and try again.
(I don't think I saw this adjustment in your description, above. The 1.1+ RAMBos use 16 Micro Steps instead of 8. Maybe this will help,...or not.)
Good luck!
Bill
That will ONLY work if you have eeprom disabled. I thought simply defining microsteps in the configuration.h would work. Pulled my damn hair out before I figured out wth EEPROM was. I agree with Cambo3d - download a fresh copy of polygonhell's firmware, and re-flash your rambo. Start fresh and edit the eeprom values through repetier-host
Re: z0 question
Posted: Sat Apr 20, 2013 9:28 am
by skyspy
#define MICRO_STEPS 16
This was the key to success!
(And I also had to double the setting for the Extruder Steps per mm.)
Thanks!
Sigi