Change motor settings and PID value's in this version?

[truenorthtrader]

Hey!

I'm trying Polygonhell's Repetier as I heard it's worth trying.

I changed some values like the height but having trouble finding this similar setting from the Marlin config
#define DEFAULT_AXIS_STEPS_PER_UNIT {106.666, 106.666, 106.666, 584.0} for my board steps
and where to input PID tuning results

I have the 16 step 1.1b board and it's obviously at 8 steps in the settings

If anyone can direct me for the 16 step settings change that would be awesome
thank you,
Anthony

[Polygonhell]

#define MICRO_STEPS 8

change it to 16 for RAMBO 1.1

[truenorthtrader]

Thank you that was the first thing I tried but didn't change anything, still going 5mm for 10mm move.

What about the Axis steps for each motor and PID tuning or is it not necessary with your program?
thank you!

[mhackney]

PID tuning just tunes the PID for the hotends and heated bed. It is not going to affect motion.

Make sure you understand how to use the EEPROM feature if you are using Repetier Host. Even if you make changes to the firmware, they may be overriden by the EEPROM values.

Code: Select all

/** \brief EEPROM storage mode 

Set the EEPROM_MODE to 0 if you always wan't to use the settings in this configuration file. If not,
set it to a value not stored in the first EEPROM-byte used. If you later want to overwrite your current
eeprom settings with configuration defaults, just select an other value. On the first call to epr_init()
it will detect a mismatch of the first byte and copys default values into EEPROM. If the first byte
matches, the stored values are used to overwrite the settings.

IMPORTANT: With mode <>0 some changes in configuration.h are not set any more, as they are 
           taken from the EEPROM.
*/
#define EEPROM_MODE 1

[truenorthtrader]

Ahh I see. I'm new to this so I guess I'll stick with the original Marlin then.
thanks!

[mhackney]

No reason to do that. With the EEPROM you can actually make changes without having to compile and upload. A lot faster for fine tuning.

Go up to the Printer menu and choose EEPROM to see the list. Close to the top you should see:

X-axis steps per mm: 106.67
Y-axis steps per mm: 106.67
Z-axis steps per mm: 106.67

I have a v 1.1 board/16 microsteps so those are the values. Change yours to this if they are not by clicking on the # and entering text (they are editable fields).

You also need to find:

Extr.1 steps per mm: 584.00

closer to the bottom of the list

[Flateric]

Another line that I am not totally clear on is this one....

// Microstep setting (Only functional when stepper driver microstep pins are connected to MCU. Currently only works for RAMBO boards
#define MICROSTEP_MODES {8,8,8,8,8} // [1,2,4,8,16]

Now, if you are running rambo v1.1 do you replace the 8's with 16's?

What would be the correct setting for Rambo v1.1?

I really like this firmware overall, although I have not printed a thing yet. My Max is calibrated to the ends of perfection however, LOL.

I wonder if my first print will be any good after all this prep.

LOL, god I hope so, but likely I have overlooked some newbie thing most certainly.

[truenorthtrader]

I changed those microstep modes from 8's to 16's and it didn't do anything.

I can't get it to work, when I make those changes, it goes into a test mode heating the hot end whenever I restart it and can't get out of it.

[mhackney]

You most likely are not setting the values in EEPROM. Look at the values in EEPROM under the printer menu and see if the steps per have been set there. If not, you can either disable using EEPROM or learn how to cause the values to update when you upload the firmware. The instructions are in the Configuration.h file:

/** \brief EEPROM storage mode

Set the EEPROM_MODE to 0 if you always wan't to use the settings in this configuration file. If not,
set it to a value not stored in the first EEPROM-byte used. If you later want to overwrite your current
eeprom settings with configuration defaults, just select an other value. On the first call to epr_init()
it will detect a mismatch of the first byte and copys default values into EEPROM. If the first byte
matches, the stored values are used to overwrite the settings.

IMPORTANT: With mode <>0 some changes in configuration.h are not set any more, as they are
taken from the EEPROM.
*/
#define EEPROM_MODE 2