Switching to Latest Repetier Firmware

[Flateric]

Eagle my friend, I think you sell yourself short and don't give yourself enough credit for what you do actually know but perhaps are slightly unsure of about. Besides, wouldn't an eaglezsoar be up in the clouds looking down at us, LOL. Kidding...

(Oh and crap on a stick I just remembered I promised to mail you something at the very moment I started typing this reply, sorry about that, I will get back on that for ya! Now back to regularly scheduled reply)

I am not referring to the arduino utility or anything such as that. I am referring to the firmware options from within repetier host itself. The v0.90 version has alot more configurable options from within the host that you can not only change without reflashing, but change mid-print, or during the print in progress. If you are really careful and only make tiny changes during the print you can hit the ok or submit after tweaking the numbers a little and see the result in real time and actually fine tune it so nicely by doing so. Just by watching the print head movement in progress.

And never ever feel that you can't smack me in the head and say, "Hey, Flatty! That's as clear as mud! Be more detailed damnit!" or ask any question you may have.

I do prefer to answer questions out here in the forums however, that way the questions and answers may help others in the future.

[Eaglezsoar]

Eagle my friend, I think you sell yourself short and don't give yourself enough credit for what you do actually know but perhaps are slightly unsure of about. Besides, wouldn't an eaglezsoar be up in the clouds looking down at us, LOL. Kidding...

(Oh and crap on a stick I just remembered I promised to mail you something at the very moment I started typing this reply, sorry about that, I will get back on that for ya! Now back to regularly scheduled reply)

I am not referring to the arduino utility or anything such as that. I am referring to the firmware options from within repetier host itself. The v0.90 version has alot more configurable options from within the host that you can not only change without reflashing, but change mid-print, or during the print in progress. If you are really careful and only make tiny changes during the print you can hit the ok or submit after tweaking the numbers a little and see the result in real time and actually fine tune it so nicely by doing so. Just by watching the print head movement in progress.

And never ever feel that you can't smack me in the head and say, "Hey, Flatty! That's as clear as mud! Be more detailed damnit!" or ask any question you may have.

I do prefer to answer questions out here in the forums however, that way the questions and answers may help others in the future.

Hey Flatty! When are we going to get the auto-level for our Rostock Max. I am tired of waiting! The other boys with their deltas are doing it with Marlin. I am about ready to get a petition going or maybe a million man march on the Indiana headquarters (if
I can find a million men). I am tired of waiting and one of you first class programmers work out the code, give it to Part Daddy and make this thing work! Headquarters is waiting for the code, and Gene took away my donuts! I will revolt who wants to join me?
I'm not interested in the tiny little tweaks you can do from the LCD (actually I am), I want the big boy -AUTO LEVEL- I have arisen, taken flight and am using my eagle eye vision to keep an eye on you guys that are supposedly "working on it" - NOT GOOD ENOUGH! The Rostock MAX is the best and it should have the best
features of any Delta!!!! GeneB, quit playing around with that Orion and mail me a donut, all this flying around makes me hungry.

[geneb]

The "other deltas" are doing auto-level after perfectly configuring their PRINTER_RADIUS, removing the need for the auto-level in the first place. You're after auto-radius and frankly, it could be a while. It doesn't appear to be a priority with the folks that are doing work on the various firmware branches.

g.

[Eaglezsoar]

The "other deltas" are doing auto-level after perfectly configuring their PRINTER_RADIUS, removing the need for the auto-level in the first place. You're after auto-radius and frankly, it could be a while. It doesn't appear to be a priority with the folks that are doing work on the various firmware branches.

g.

I guess I'll have to stay hungry!

I did my best to get a rise out of you! For a guy who likes to throw things you sure are mellow. Have fun with the new Orion and let us know
what you think about it. I am interested in how well it handles detailed prints and how it does at doing the .1mm or smaller prints.

[barnett]

I've been trying for the last bit here to upgrade from 0.80 to either 0.81 or 0.90 and I can't get it to compile after I drop in my uiconfig.h, pins.h and change the configuration.h values. I keep getting "DIO76_DDR isn't declared in this scope" and this:

"uiconfig.h:304: error: 'DIO76_DDR' was not declared in this scope
uiconfig.h:304: error: 'DIO76_PIN' was not declared in this scope
uiconfig.h:304: error: 'DIO76_WPORT' was not declared in this scope"

It repeats that same message for DIO70 through to DIO78. I don't know enough about debugging in the arduino environment to figure out the problem. I looked into the fastio.h where all those variables are listed but I didn't see anything out of the ordinary.

I suspect it might have something to do with the SD support functions. I know I'm missing something I just can't figure what.

Any suggestions?

Do you have Arduino Mega 2560 selected in Arduino Tools|Board?

[PurpleDrank]

I've been trying for the last bit here to upgrade from 0.80 to either 0.81 or 0.90 and I can't get it to compile after I drop in my uiconfig.h, pins.h and change the configuration.h values. I keep getting "DIO76_DDR isn't declared in this scope" and this...

Do you have Arduino Mega 2560 selected in Arduino Tools|Board?

Yes, I just came across an issue on GitHub and it looks like I have to fiddle with the uiconfig.h. I'll try that solution after my print in progress finishes and report back with the link to it if it works.

[Eaglezsoar]

If you've got an easy way to compare the text between the main Git and the download.seemecnc.com branch, I'd be very curious to know what's different.

I'm about to upgrade as well and haven't decided which Git to commit to.

http://winmerge.org/ looks like a good program to compare 2 files and display the differences.

[dpmacri]

I finally got around to trying the developer branch, version .90 firmware. I went through Configuration.h, pins.h and uiconfig.h, comparing to the version that I had been using and making the changes that seemed to make sense. After building/updating the firmware, though, I've run into an issue. I just get the REPETIER_VERSION and the UI_VERSION_STRING showing up and the RAMBO appears to be hung. Occasionally a few square show up under the two strings mentioned. But nothing else works

I re-installed the previous version and got things back up and running, but I'm curious if anyone has seen anything similar (or can someone using the firmware post their three .h files)?

[daftscience]

https://github.com/daftscience/myrepetier

you can use pins.h and uiconfig.h as is. But I would recommend just modifying the latest configuration.h.

[dpmacri]

https://github.com/daftscience/myrepetier

you can use pins.h and uiconfig.h as is. But I would recommend just modifying the latest configuration.h.

Thanks, daftscience! There are some differences, but I think it's primarily due to updates in the development branch. I'm wondering if I just picked up an unstable state of the 0.90 tree. I'm not sure how to go about debugging this without getting into the code and trying to figure out what it's doing I'll take a look at that when I get a chance.

If anyone else has pulled a recent snapshot of the 0.90 development branch (626Pilot perhaps? ) can you share any changes you've made to get it to work with your Rostock MAX?

Thanks,
Dean