My Rostock Max V2 thinks the build plate is a bowl

[RURC]

I finally get the Cyclops working and then the poop hits the fan.

We were running a frog on the Rostock and the tower that holds the reels up top broke in half sending a new roll of PLA crashing down onto the bed and hitting the power switch. This was in the very beginning of the print program. Ever since then we have not been able to get any print to work. I was needing a brake from the issues we have been having so I let the printer sit for a week and a half before I got back on it. Now it is time to fix it all.

Here is what I noticed after this happened:
1. the z height changed from 392.57 to 392.65 with the same settings of 190C and 60C head and bed respectively
2. if I place a piece of paper under the head and lower the Z to 0.00 the fit is perfect. I can move the paper but feel drag.
3. if I then raise Z 1.00mm and take X + or - to 50mm it binds the paper hard.
4. the same thing happens in Y +or -, the paper binds at 50mm.
5. if I continue that to 100mm from center it becomes 100mm X- 4.2mm, 100mm X+ 3.91mm, 100mm Y- 4.7mm, 100mm Y+ 4.4

So the stepper motors think my bed is a bowl with the center as much as 4.7mm deep. I can assure you that my bed is not bowl shaped at all.

SO clearly somewhere the system lost it mind but I cant for the life of me figure this out. I have gone through the manual and I am not finding a calibration for the motors or a synchronization for them. I am extremely frustrated and might have overlooked them in my frustration.

Please Help

[Xenocrates]

I suggest adjusting your horizontal radius (section 2.5, Rmax user manual, page 31, motion calibration). If that doesn't help, let us know.

[RURC]

I suggest adjusting your horizontal radius (section 2.5, Rmax user manual, page 31, motion calibration). If that doesn't help, let us know.

OK

Going to try this tonight

[RURC]

I suggest adjusting your horizontal radius (section 2.5, Rmax user manual, page 31, motion calibration). If that doesn't help, let us know.

Just a question on this, how in the heck can what happen cause this to go out? We have days and days of printing on this machine. It just does not make since to me.

[geneb]

The EEPROM may have become corrupted, or someone screwed(ha!) around with your end stop switches.

g.

[DeltaCon]

I think no-one can make sense of that, but the description of a bowl in the bed does only make sense with an off value of the horizontal radius. Probably something else happened too. For example, reloading firmware as a countermeasure of another disfunctionality? Personally, I had a lot of issues I could not make sense of blaming on the wrong event...

[RURC]

I think no-one can make sense of that, but the description of a bowl in the bed does only make sense with an off value of the horizontal radius. Probably something else happened too. For example, reloading firmware as a countermeasure of another disfunctionality? Personally, I had a lot of issues I could not make sense of blaming on the wrong event...

The problem I have is that I got this unit as a dual filament unit. I do not have a copy of the EEPROM code for the dual usage.

[Xenocrates]

I suggest adjusting your horizontal radius (section 2.5, Rmax user manual, page 31, motion calibration). If that doesn't help, let us know.

Just a question on this, how in the heck can what happen cause this to go out? We have days and days of printing on this machine. It just does not make since to me.

The Atmega 2560 (Which the Rambo is based around) has been known to eat it's own bootloader/EEPROM on occasion. It's annoying, and frustrating, and a known issue, but it happens.

[RURC]

I suggest adjusting your horizontal radius (section 2.5, Rmax user manual, page 31, motion calibration). If that doesn't help, let us know.

Just a question on this, how in the heck can what happen cause this to go out? We have days and days of printing on this machine. It just does not make since to me.

The Atmega 2560 (Which the Rambo is based around) has been known to eat it's own bootloader/EEPROM on occasion. It's annoying, and frustrating, and a known issue, but it happens.

Anybody got any ideas about the EEPROM coding for dual extruders? If this is a corrupted code in the EEPROM how the hell am I going to fix that. I dont know that coding. Is there someone I can send a copy of the code to that can either give me a corrected form or can tell me how to upgrade the OEM code to dual extruder?

[geneb]

Did you buy the printer pre-built from someone else? If so, why didn't they include the firmware changes when they sold it to you? You might want to contact them if this is the case and get the source so you can reload it when needed.

g.

[RURC]

Did you buy the printer pre-built from someone else? If so, why didn't they include the firmware changes when they sold it to you? You might want to contact them if this is the case and get the source so you can reload it when needed.

g.

I never thought about that when we got it. I have contacted the guy we got it from and he told me that the guy that did the upgrades to it will not return his calls or emails. Also I did not know that I should ask for the BIOS. Now I do.

[Xenocrates]

That's a sign of a healthy working relationship /s

In all honesty, the dual extrusion modifications aren't that hard to do. there are several topics, and working configs on this forum already. Just use the search bar

(Nitpick, it's Firmware, not BIOS. the BIOS equivalent would be the Arduino Bootloader, which the chips also sometimes eat. Isn't technology wonderful?)

[geneb]

Nitpick to the nitpick: There is no equivalent to the BIOS in the Arduino ecosystem.

RURC, configuring a dual extruder from scratch isn't that difficult. There's a number of people here that have done it and I suspect they'd be happy to help you.

g.

[RURC]

Nitpick to the nitpick: There is no equivalent to the BIOS in the Arduino ecosystem.

RURC, configuring a dual extruder from scratch isn't that difficult. There's a number of people here that have done it and I suspect they'd be happy to help you.

g.

That's a sign of a healthy working relationship /s

In all honesty, the dual extrusion modifications aren't that hard to do. there are several topics, and working configs on this forum already. Just use the search bar

(Nitpick, it's Firmware, not BIOS. the BIOS equivalent would be the Arduino Bootloader, which the chips also sometimes eat. Isn't technology wonderful?)

Thank you both. I hope to get to this over the weekend. I will be searching the forum in detail in a hope to find what I need to do this correctly.