Help with configuration file(s)

Having a problem? Post it here and someone will be along shortly to help
Post Reply
redtank
Printmaster!
Posts: 53
Joined: Sat Jan 31, 2015 8:06 pm

Help with configuration file(s)

Post by redtank »

Hello,
I've been using an E3D-V6 hot end on my Rostock Max V2. It's time that I need to change the correct configuration file to allow the printer to reach 300°C and in addition, I need to find a way to correct X, Y, and Z calibration to get my prints closer to nominal values, for instance a 1" cube might be off .025" to the small side on any of directions. I know different materials have different shrink amounts, but I can do better. Can anyone tell me what configuration file needs changed and what variable in that file? Do I have to erase the entire EEprom and start from scratch like when setting up the Rostock from scratch?

Thanks!
C. Lepage
Xenocrates
ULTIMATE 3D JEDI
Posts: 1561
Joined: Wed Sep 23, 2015 2:55 pm

Re: Help with configuration file(s)

Post by Xenocrates »

I've done these modifications myself, so I might as well help you. find the MAXTEMP parameter in the
############## Hotend safety settings ######################
section, under Rostock Max. Change that to 300 or so (I would limit it to ~280, just to avoid thermistor damage, as many begin to degrade at 300, which is part of why I use PT100's). This is inside the firmware in configuration.h. Next find the
EXT0_TEMPSENSOR_TYPE
paramater, and change it to match your thermistor or whatever you're using. I use PT100's, but the correct one for the standard E3D thermistor is 8. Other sensor types like their PT100's or thermocouples take additional hardware and configuration, so let me know if you need that. I also heavily recommend one of the brand new plated copper nozzles and a silicone sock for those temperatures. Aluminum is OK, but with that much heat, you'll want to be able to move it to filament and contain it in the block better.

For the scale factor, I would figure out the shrink factor, and correct for it in the slicer rather than printer configuration, since different materials will have different ones, thus making the slicer the appropriate place to have that info, and it can make the parts come out perfectly sized each time. I might adjust the extrusion width value rather than scaling though. Up to you to play with.
Machines:
Rostock Max V2, Duet .8.5, PT100 enabled E3D V6 and volcano, Raymond style enclosure
Automation Technology 60W laser cutter/engraver
1m X-carve router

Sic Transit Gloria Mundi
01-10011-11111100001
redtank
Printmaster!
Posts: 53
Joined: Sat Jan 31, 2015 8:06 pm

Re: Help with configuration file(s)

Post by redtank »

Xenocrates,
First, thanks for the reply. So I modify the Configuration.h file, but the next question is can I upload this file (via Arduino software) by itself to the Rambo without going thru the entire erasing of the Eeprom and having to do a complete calibration over again?

C.Lepage
morgandc
Printmaster!
Posts: 280
Joined: Mon Sep 26, 2016 8:32 pm

Re: Help with configuration file(s)

Post by morgandc »

The proper method is to clear the eeprom prior to uploading the firmware. If you write down the eeprom settings you can manually enter them after wards. I hear rumors that some people don't routinely clear the eeprom before uploading firmware with just config changes, but I haven't done it.
User avatar
DeltaCon
Printmaster!
Posts: 616
Joined: Sat Nov 14, 2015 5:01 am
Location: Wessem, The Netherlands
Contact:

Re: Help with configuration file(s)

Post by DeltaCon »

As far as my experience reaches, it is no problem to overwrite your firmware with with the same firmware with changed values. Eeprom values will probably not get overwritten, but the suggested changes are no eeprom changes. I make it a habit to store the latest uploaded firmware, and change in it also the eeprom values that I changes on the machine or through mattercontrol/repetierhost or whatever software you use. That way it takes a lot less time recovering from firmware problems or experiments. Also using repetier host you can make an export of the eeprom values, to be imported later again.

The above seems to be influenced by the #define EEPROM_MODE statement in the firmware you upload. I never really understood how it works, but I managed a lot of firmware uploads nevertheless ;-) See https://www.repetier.com/documentation/ ... tallation/ for more info on the eeprom trap.
I am DeltaCon, I have a delta, my name is Con, I am definitely PRO delta! ;-)
Rostock V2 / E3D Volcano / FSR kit / Duet 0.6

PS.: Sorry for the avatar, that's my other hobby!
Post Reply

Return to “Troubleshooting”