Rep.FW: H-bot setting not working for 1 extruder

Hi,

I am observing a strange behavior with the latest release of Repetier Firmware (ver. 0.91):

I have an H-bot (DRIVE_SYSTEM=1), and 2 extruders (NUM_EXTRUDERS=2). This configuration works fine so far.

Now, after changing just NUM_EXTRUDERS=2 to NUM_EXTRUDERS=1 (ceteris paribus), and uploading the firmware to my Megatronics v2.0, I observe that my coordinate system is shifted 45deg. It seems that the setting "H-Bot" is not being active anymore.

Is this a bug?

The printer is controlled over Rep.Host (ver 0.95F), and the num. of extruders in the settings of the host-SW is adjusted so that it is the same as in the firmware.

Thanks.

Host settings can not change firmware coordinate system.

We haven't touched the cartesian code for month so no, we haven't changed anything or at least it wasn't by intention. Also I find it strange that the numbe rof extruders influences that as extruders have nothing to do with drive system setting. I also think a 45 degree rotation is not possible. I think it switched to drive system 0 for some reason with you latest update. In that system only one motor per axis is driven giving 45° moves for h-belt systems.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!

Quote
repetier
Host settings can not change firmware coordinate system.

We haven't touched the cartesian code for month so no, we haven't changed anything or at least it wasn't by intention. Also I find it strange that the numbe rof extruders influences that as extruders have nothing to do with drive system setting.

Agreed - I find this strange too.

Quote
repetier
I also think a 45 degree rotation is not possible. I think it switched to drive system 0 for some reason with you latest update. In that system only one motor per axis is driven giving 45° moves for h-belt systems.

The firmware behaves like if it was in DRIVE_SYSTEM=0 for less than two extruders - which represents a 45deg rotation compared to an H-Bot. However, the firmware is still in the setting DRIVE_SYSTEM=1.

I have tested this:
1) NUM_EXTRUDERS=2 (everything else the same) --> upload firmware --> control with Rep.Host and movements are unproblematic
2) NUM_EXTRUDERS=1 (everything else the same) --> upload firmware --> control with Rep.Host and movements are problematic (behaves like a normal cartesian robot)
3) NUM_EXTRUDERS=2 (everything else the same) --> upload firmware --> control with Rep.Host and movements are unproblematic

..very strange to me

As a Megatronics 2.0 owner who gets a headache trying to follow the nested "#ifdef hell" in ui.h fixing the support for this board and a full graphics display, let me throw in my two cents and say that I wouldn't be surprised if this was one or more conflicting #if statements unintentionally setting the wrong defines for this board/drive/extruder combination. Up until now, I was wondering if I was the only person who has ever tried to run V0.91 on a Megatronics 2.0 board, because it doesn't seem to be well tested from my experiences.....

The GLCD is only preconfigured for RUMBA and RAMPS. For other boards you have to modify pin assignment accordingly. With the increasing number of combinations we definitely need a better concept to handle this more transparent. But how solve to 15 controller types implemented with 24 boards = 360 combinations so far and every month adding new boards and controllers.

---

Repetier-Software - the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server - the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!