Page 1 of 1

New Rumba Board

Posted: Sat Apr 23, 2016 9:40 am
by Ziggey
So I'm upgrading to a rumba board for the diamond hotend. I have a Rostock max V2 and I"m wondering what the best firmware is to run this. I have been reading both and can't really see the ups and downs of both boards. Anyone want to give me the heads up on what one is better or have had better luck with?

Thank you,
Zig

Re: New Rumba Board

Posted: Sat Apr 23, 2016 10:43 am
by Eaglezsoar
I think that the best firmware to run would be the Repetier firmware. With the deltas like the Rostock we have found that Marlin firmware
produces jerky movements and is not recommended.
The latest firmware that SeeMeCNC recommends is at seemecnc.com under the downloads tab.
Best of luck with your upgrade and we are here to help if you have the need.

Re: New Rumba Board

Posted: Sat Apr 23, 2016 11:29 am
by Nylocke
I would recommend using the config tool to make your own version of the firmware, but that may be a challenge if you aren't familiar with steps per mm of each tower and stuff like that. The version from SeeMe (if its still .91) is built for the RAMBo, and while you can change the board def to RUMBA, I think there are some special tweaks that may have been made to support certain fans in pins other than their default and it may not get changed properly.

Re: New Rumba Board

Posted: Sat Apr 23, 2016 1:53 pm
by Eaglezsoar
Nylocke wrote:I would recommend using the config tool to make your own version of the firmware, but that may be a challenge if you aren't familiar with steps per mm of each tower and stuff like that. The version from SeeMe (if its still .91) is built for the RAMBo, and while you can change the board def to RUMBA, I think there are some special tweaks that may have been made to support certain fans in pins other than their default and it may not get changed properly.
Thank you Nylocke, I assumed that the user would know that pins, etc would need changed when updating control boards but I should not make
those assumptions. Thanks for the reminder.

Re: New Rumba Board

Posted: Sat Apr 23, 2016 5:58 pm
by Windshadow
What is the difference between the RAMBo and the RUMBA boards? is there a basic reason you are not using the RAMBo?

And Eagle Don't tell me one is a Stallone Movie Franchise and the other a Dance that was popular in Cuba before I was born :D

Re: New Rumba Board

Posted: Sat Apr 23, 2016 6:09 pm
by Nylocke
The RUMBA has built in support for 3 extruders vs the 2 of the RAMBo, which is what they want for the diamond

Re: New Rumba Board

Posted: Sat Apr 23, 2016 7:17 pm
by Eaglezsoar
Windshadow wrote:What is the difference between the RAMBo and the RUMBA boards? is there a basic reason you are not using the RAMBo?

And Eagle Don't tell me one is a Stallone Movie Franchise and the other a Dance that was popular in Cuba before I was born :D
One is a Stallone Movie Franchise and the other a Dance that was popular in Cuba before you were born. :D

Re: New Rumba Board

Posted: Sun Apr 24, 2016 2:00 am
by Ziggey
So I have finally got my full graphic display to work with the board. How do I go about changing the pins I have read a few forums online already and Can't seem to get this to compile... Any suggestions? Whats the best way to change the pins to the rumba board in short...

THank you for all the help so far.
Zig

Re: New Rumba Board

Posted: Sun Apr 24, 2016 4:07 am
by Eric
Ziggey wrote:So I have finally got my full graphic display to work with the board. How do I go about changing the pins I have read a few forums online already and Can't seem to get this to compile... Any suggestions? Whats the best way to change the pins to the rumba board in short...

THank you for all the help so far.
Zig
In "Configuration.h", near the top of the file you'll find MOTHERBOARD defined, along with comments telling you what value to set it to for different boards, including Rumba. This causes "pins.h" to map the correct hardware pin numbers for your board. That should take care of it unless you need to do something special.

To use multiple extruders, you'll want to change NUM_EXTRUDERS to the right number.

If you set up a fresh copy of the firmware with the configuration tool, the above should already be set.

Re: New Rumba Board

Posted: Sun Apr 24, 2016 2:07 pm
by Ziggey
Ok so under motherboard i put 80 (for rumba) it doesn't let me compile after that. I get this error message

In file included from HAL.h:79:0,
from Repetier.h:249,
from Commands.cpp:22:
Commands.cpp: In static member function 'static void Commands::emergencyStop()':
fastio.h:29:39: error: 'DIOHEATER_BED_PIN_WPORT' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
fastio.h:29:68: error: 'DIOHEATER_BED_PIN_PIN' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:17:30: note: in definition of macro 'MASK'
#define MASK(PIN) (1 << PIN)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
fastio.h:29:96: error: 'DIOHEATER_BED_PIN_WPORT' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
fastio.h:29:126: error: 'DIOHEATER_BED_PIN_PIN' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:17:30: note: in definition of macro 'MASK'
#define MASK(PIN) (1 << PIN)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
Error compiling.
In file included from Repetier.h:113:0,
from Commands.cpp:22:
Configuration.h:19:0: error: unterminated #ifndef
#ifndef CONFIGURATION_H
^
In file included from HAL.h:79:0,
from Repetier.h:249,
from Commands.cpp:22:
Commands.cpp: In static member function 'static void Commands::emergencyStop()':
fastio.h:29:39: error: 'DIOHEATER_BED_PIN_WPORT' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
WRITE(HEATED_BED_HEATER_PIN,0);
^
fastio.h:29:68: error: 'DIOHEATER_BED_PIN_PIN' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:17:30: note: in definition of macro 'MASK'
#define MASK(PIN) (1 << PIN)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
WRITE(HEATED_BED_HEATER_PIN,0);
^
fastio.h:29:96: error: 'DIOHEATER_BED_PIN_WPORT' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
WRITE(HEATED_BED_HEATER_PIN,0);
^
fastio.h:29:126: error: 'DIOHEATER_BED_PIN_PIN' was not declared in this scope
#define _WRITE(IO, v) do { if (v) {DIO ## IO ## _WPORT |= MASK(DIO ## IO ## _PIN); } else {DIO ## IO ## _WPORT &= ~MASK(DIO ## IO ## _PIN); }; } while (0)
^
fastio.h:17:30: note: in definition of macro 'MASK'
#define MASK(PIN) (1 << PIN)
^
fastio.h:48:25: note: in expansion of macro '_WRITE'
#define WRITE(IO, v) _WRITE(IO, v)
^
Commands.cpp:1423:5: note: in expansion of macro 'WRITE'
WRITE(HEATED_BED_HEATER_PIN,0);
^

Not sure what is going wrong here.
I zipped up the firmware so if anyone is interested you could have a look.

Thank you for any explanation possible.
Zig

Re: New Rumba Board

Posted: Sun Apr 24, 2016 10:27 pm
by Eric
Ah, you've run into the joys of trying to use a custom branch of software that's only tested against the specific hardware the vender sells. e.g. Rambo.

The immediate problem is that HEATER_BED_PIN isn't defined in the RUMBA section of pins.h. You could add it, but this may not be your only gotcha.

I'd suggest going to repetier.com and downloading a current version of the firmware using the configuration tool. It's probably the easier path.

Re: New Rumba Board

Posted: Thu Apr 28, 2016 1:28 am
by Ziggey
OK, I did the config. tool, uploaded it and there are still a few glitches.
LCD Full Graphic smart display RepRap
- The problem with this is it only allows me to scroll down one line then goes back up. Its really annoying, but I did mannage to change the temp of the bed and hotend with the LCD screen along with the fan.
Motors
- I can't seem to get my motors to move. I have tried inverting the endstops and changing the values but nothing seems to work very well. I have the Max V2 trying to get the Rumba board going. I know I read something about this but couldn't find the particular form on it.
I'll attach a copy of my Config.h and pins.h just in case someone wants to take a look at it. I am able to control the temp for bed and extruder along with the fan on matter control. Seems to work just fine.

Anything input would help. THank you,
ZIg

Re: New Rumba Board

Posted: Thu Apr 28, 2016 6:32 am
by Eric
My first thought about your motors is whether you've set the current limit on the 8825 drivers. It's a tiny potentiometor on each driver board. (Your old Rambo had digipots that were set via firmware, so this is new to you.) If it's set too low, your motors won't have enough current to move. Too high (above the motor current rating) risks killing the motor. Anywhere inbetween is a compromise between how much motor power you need for the task and how hot your motors run. When I say hot, I'm talking about temperature.

See http://reprap.org/wiki/Pololu_stepper_driver_board for a writeup.
Or if you like videos, https://www.youtube.com/watch?v=89BHS9hfSUk.

My other thought is whether you ever had the driver boards in backwards when you had your earlier problems. If so, you may have killed them.

Hope that's helpful...