Repetier for RostockMax and RAMBO

[lgrijalvah]

If you have a very large discrepancy in heights at the center and edge of the build surface, multiple mm's.
The odds are you have differing steps per mm set for X Y and Z in the firmware and the EEPROM, the settings MUST match.
If the disparity is small and they match then a small adjustment to DELTA RADIUS is probably required.
The pot values he refers to are the current limiting pots on the stepper drivers, they are set in the firmware, too low and the steppers miss steps, too high and the drivers over heat and the steppers miss steps.

Thanks for your answer, i will double check those settings values and see if works.

Luis G.

[aehM_Key]

Repetier 0.83 seem's to be available.
"fixes clacks after z changes" ..whatever this means

[September]

Yes Repetier-Firmware original is at v0.83 but the SeeMECNC RostockMAX fork of the Repetier firmware is still at v0.80. (unless the version numbers are no longer the same)

I'm not certain this is a direct fork of the repetier firmware, I couldn't find the sha where it was forked from (at least one where there was little change) and it looks like it was directly uploaded so the forked links aren't on github.

Anyway I'm sure the original firmware contains everything for the RostockMAX... just probably requires a lot of configuration changes to Configuration.h that come pre defaulted in the RostockMAX version and I'm hoping the code is good minus some fixes that might not have made it back to the original firmware as yet.

I'm pretty sure that any code fixes done to the RostockMAX would eventually make their way back to the Repetier firmware and vice versa just a matter of time, merges are a nightmare. I have seen some changes accepted back.



This is something I've been meaning to question, what are the actual differences between the two firmwares. Is the primary purpose to have the Configuration.h pre-defaulted to meet the requirements of the RostockMAX to make it easier for people? With the occasionally code fixes (which as I said before, I'd imagine these would make it back to the original Repetier Firmware).


One of the reasons I'm considering using the Repetier Firmware, is that I'm currently unable to use the EEPROM to make changes, I have to do everything in the firmware. Repetier-Host (Windows) crashes most times and when it doesn't crash it doesn't read all the values correctly... I'm currently assuming something has changed between versions... I have tried back dating Repetier-Host as far back as v0.80 and still crashes and/or does't read the values correctly. Anyway if the EEPROM isn't being read correctly by Repetier-Host, I wonder what else isn't being read/written by the Repetier-Host correctly hence my main curiosity of trying the current Repetier firmware... Maybe I am using a too new version of Repetier-Host for the current release of the SeeMECNC Repetier firmware. All of which assuming the problem is in the firmware and not in the Repetier-Host.


Has anyone tried the original firmware? I'm assuming most would stick with the SeeMECNC version of the firmware as it's what they would likely support (officially)

If you have tried it did you just update the Configuration.h with the correct values for the RostockMAX?


PS No I haven't checked with SeeMECNC about the EEPROM thing as yet, it probably isn't something I'll end up using anyway and I'll use SCM to track my configuration changes... (and yes with the stock SeeMECNC firmware it crashes, it's not due to some Configuration.h change on my behalf, I didn't even look at the firmware until I found I couldn't make changes through the EEPROM).

[Jimustanguitar]

Anyway I'm sure the original firmware contains everything for the RostockMAX... just probably requires a lot of configuration changes to Configuration.h that come pre defaulted in the RostockMAX version and I'm hoping the code is good minus some fixes that might not have made it back to the original firmware as yet.

I hope that's the case. Ideally, each release of Repetier would be modified by John and posted on the download.seemecnc.com website instead of updating an old fork every time. PolygonHell may have some insight on this process as well, because he's quite the firmware ninja

I was looking at this the other day (new repetier host, new slicer, new arduino software, and new firmware are all available) and it appears that the current seemecnc version is 3 or 4 days older than the most recent commit from Repetier. The notes sound similar though, so I suspect that both versions fixed the same thing.

[Polygonhell]

I don't know what Johns policy is on this, I usually only update when there is a change that will have a significant win, there is active development in the branch, and while it's usually pretty stable, I'm reticent to tray and stay bleeding edge.
There always seems to be something subtle that causes issues in configuration.h when I merge, usually one of the defaults that happened to be correct is changed.

You can branch it yourself on Github, and make the configuration changes, it's IMO not the easiest firmware to configure but it's not that difficult if you have some familiarity with software, it took me several hours of messing about to get everything working when I first did it. It's a little easier now because there is direct support for the LCD.