Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Converting from old marlin #1979

Closed
boelle opened this issue Apr 27, 2015 · 32 comments
Closed

Converting from old marlin #1979

boelle opened this issue Apr 27, 2015 · 32 comments

Comments

@boelle
Copy link
Contributor

boelle commented Apr 27, 2015

So had time to get the latest marlin installed

copy and pasting settings from the 2-3 year old copy of marlin got me going but now i'm a bit stuck

this old one:

#define X_MAX_LENGTH 221
#define Y_MAX_LENGTH 221
#define Z_MAX_LENGTH 390.65

// The position of the homing switches. Use MAX_LENGTH * -0.5 if the center should be 0, 0, 0
#define X_HOME_POS X_MAX_LENGTH * -0.5
#define Y_HOME_POS Y_MAX_LENGTH * -0.5
#define Z_HOME_POS Z_MAX_LENGTH

is no where in the new config....

should i use these?

#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS 221
#define Y_MAX_POS 221
#define Z_MAX_POS 390.65

and how do i set them so that center of bed is 0,0 ?

@nophead
Copy link
Contributor

nophead commented Apr 27, 2015

You make MIN_POS -110.5 and MAX_POS 110.5 to get 0 in the middle.

@boelle
Copy link
Contributor Author

boelle commented Apr 27, 2015

thanks....

@boelle
Copy link
Contributor Author

boelle commented Apr 27, 2015

mostly a note for self, but when i ran pid auto tune for the bed (not an option in old marlin) it ended up with this:

PID Autotune finished! Put the last Kp, Ki and Kd constants from below into Configuration.h
#define  DEFAULT_Kp 176.72
#define  DEFAULT_Ki 13.59
#define  DEFAULT_Kd 574.51

have it not forgotten bed after the underscore ?

@boelle
Copy link
Contributor Author

boelle commented Apr 27, 2015

almost there....

i can do G28 and it homes.... but it will try and move past the endstops....

config as of now: http://pastebin.com/zPG4Pefw

cant figure if something should ignore the endstops

@boelle
Copy link
Contributor Author

boelle commented Apr 27, 2015

maybe this in Configuration_adv.h:

#define ENDSTOPS_ONLY_FOR_HOMING // If defined the endstops will only be used for homing

?

@nophead
Copy link
Contributor

nophead commented Apr 27, 2015

For Mendel90 the endstops are outside the print volume, so once homed the
soft limits should prevent them ever being hit again.

On 27 April 2015 at 21:16, Bo Herrmannsen notifications@github.com wrote:

maybe this in configuration_adv:

#define ENDSTOPS_ONLY_FOR_HOMING // If defined the endstops will only be
used for homing

?

Reply to this email directly or view it on GitHub
#1979 (comment)
.

@boelle
Copy link
Contributor Author

boelle commented Apr 28, 2015

oh... forgot to set soft limits :-/

ie they are set to false right now...

@thinkyhead
Copy link
Member

#1989

@boelle
Copy link
Contributor Author

boelle commented Apr 28, 2015

:-D the man is on fire... fast fix

@boelle
Copy link
Contributor Author

boelle commented Apr 28, 2015

btw.... will prob be able to test auto level to late tomorrow or weekend. only need to rebuild my extruder and do some minor mod's to my electronics

@boelle boelle closed this as completed May 7, 2015
@thinkyhead
Copy link
Member

@boelle Great. Maybe we can do some video-based leveling debugging…. 🪲

@boelle
Copy link
Contributor Author

boelle commented May 8, 2015

yep, just need to wire up the servo and touch switch

@boelle
Copy link
Contributor Author

boelle commented May 8, 2015

home at last....

Q: are there a M119 equilant for testing the touchprobe?

i have changed the pins file for my board so it now looks like this:

http://pastebin.com/HXz4bAPy

i know i use M280 PX SX to set the pos of the servo

2015-05-08 7:00 GMT+02:00 Scott Lahteine notifications@github.com:

@boelle https://github.com/boelle Great. Maybe we can do some
video-based leveling debugging…. [image: 🪲]


Reply to this email directly or view it on GitHub
#1979 (comment)
.

@thinkyhead
Copy link
Member

M119 might work for the probe. If not we need to add it in.

@boelle
Copy link
Contributor Author

boelle commented May 8, 2015

oki.. btw my config: http://pastebin.com/mrXadjJ1

2015-05-08 15:44 GMT+02:00 Scott Lahteine notifications@github.com:

M119 might work for the probe. If not we need to add it in.


Reply to this email directly or view it on GitHub
#1979 (comment)
.

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

first problem... servo does not move

sure its a software problem but not sure where

2015-05-08 15:44 GMT+02:00 Scott Lahteine notifications@github.com:

M119 might work for the probe. If not we need to add it in.


Reply to this email directly or view it on GitHub
#1979 (comment)
.

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

M119 does not report status on the z probe either... only XYZ

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

hmm... doing autotune for the bed and hotend

bed was ok

but not during hotend autotune the extruder fan led flashes together with the hotend

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

M106 and M107 work fine thou... so not a wiring issue

bed cooling fan can also be controlled manual

will check if everything else works but assume so far that they do

@nophead
Copy link
Contributor

nophead commented May 9, 2015

Does your fan share the 12V wire with the heater, as per Mendel90? If so
maybe the heater is wired with the wrong polarity, in which case turning it
on will turn the fan off.

On 9 May 2015 at 12:02, Bo Herrmannsen notifications@github.com wrote:

M106 and M107 work fine thou... so not a wiring issue

bed cooling fan can also be controlled manual

will check if everything else works but assume so far that they do

Reply to this email directly or view it on GitHub
#1979 (comment)
.

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

Yes, i have chekced it thou and work fine when i turn things on and off in pronterface.

will check again thou

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

doooh.... yes wired in wrong :-( slap in face

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

nope it was right... me not reading schematics right

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

slap in face turned out check i double checked it was wired in wrong

still wondering why the servo will not move

@fmalpartida
Copy link
Contributor

I'll try our tonight the new de branch during the hangout. On Thursday the
M851 command was broken.
El 9/5/2015 13:42, "Bo Herrmannsen" notifications@github.com escribió:

slap in face turned out check i double checked it was wired in wrong

still wondering why the servo will not move


Reply to this email directly or view it on GitHub
#1979 (comment)
.

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

well i have just downloaded the lastest copy but have no clue why the servo is not moving

@boelle
Copy link
Contributor Author

boelle commented May 9, 2015

fresh copy on my config: http://pastebin.com/9hXCtrku
pins file: http://pastebin.com/2BYjaQj8

@boelle
Copy link
Contributor Author

boelle commented May 10, 2015

as promissed an update....

i updated to latest IDE and figured how to get the old MCU/AVR in there... then did a compile
then i found out that in fact i only needed to add the bootloader file as the fuse settings turned out to be the same. it took at lot of compare using an online fuse calculator. first entering everything for the old MCU... then selecting the new one and efter the same settings... what a relief.

then i only had to edit my pins file (pins_ omca .h something) so that it would not say upps if i picked the new MCU or the old one...

now i only have to replace the chip itself and burn bootloader etc

@thinkyhead
Copy link
Member

Good news! I haven't gone anywhere near the bootloader stuff (yet) so I still find it quite mysterious.

@boelle
Copy link
Contributor Author

boelle commented May 11, 2015

now bad news:

avrdude: verification error, first mismatch at byte 0x1f000
0xff != 0x0c
Error while burning bootloader.
avrdude: verification error; content mismatch

@boelle
Copy link
Contributor Author

boelle commented May 11, 2015

scratch it... i went back to ide 1.0.6

at least i can burn bootloader for the 644 there and upload a sketch...

@boelle boelle removed T: Development Makefiles, PlatformIO, Python scripts, etc. C: Documentation T: Feature Request Features requested by users. PR: Improvement Needs: More Data We need more data in order to proceed Bug? False Alarm Bug: Potential ? Bug: Confirmed ! labels Jun 29, 2015
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants