Welcome! Log In Create A New Profile

Advanced

Repitier FW compile issue

Posted by Voidus 
Repitier FW compile issue
April 09, 2013 02:12AM
Hi All

Currently using Arduino IDE 1.0.1 to compile Repitier FW 0.82 for a Gen6 board

set motherboard == 5
set heatbed to false

getting the following error on compile

---

Repetier.cpp: In function 'void setup()':
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_DDR' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.cpp: In function 'void __vector_17()':
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_WPORT' was not declared in this scope
Repetier.pde:-1: error: 'DIOHEATER_2_PIN_PIN' was not declared in this scope

---

It appears (I'm all new to this) that it is look for the declare/define for the pins of a 2nd heater? There is only 1 heat element on a Gen6 so not sure what/why it's looking for this.
Re: Repitier FW compile issue
April 09, 2013 07:06AM
Well I fixed it by adding

#define HEATER_2_PIN -1
#define TEMP_2_PIN -1

Under the Gen6 section of pins.h

Compiling happily, now to get everything moving in the correct directions, actually the X-Axis is not moving at all for some reason.
Re: Repitier FW compile issue
April 09, 2013 11:32AM
YOur HEATER_2 problem solution is good. For the next release I add some more checks if also the number extruders is reached to use the vars. With the current tests the -1 as value also has this result.

You could switch x/y pin definition in pins.h to see if it is a software settings problem. If then the y axis doesn't work it is either a wrong port(unlikely, pins are tested for 1,5 years now) or a hardware problem. You should also check if the motor connectors are right and have contact. Sometimes you push the pins a bit outside and then they have no contact.


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!
Re: Repitier FW compile issue
April 09, 2013 07:44PM
Hey Repetier!

Yah not much of a programmer./scripter, but I know enough to read through things, glad you liked my solution smiling smiley

I have the Y & Z working in both directions and frindin the Min Endstop well enough, Extruder stepper & Heater working the right way and heating fine (nothing clibrated yet)

I may have missed semething in the config but there any changes to made if the steppers are 1.9 or 0.8 degree steppers? or just adjust the steps/mm as needed.

But no response at all on the X.

I will as suggested check the physical connection for it, though it was working with the orginal firmware well enough but I may have bumped something when connecting the USBTinyISP.
It wont program via AVRISP always get the stk500 out of sync error that way.
Re: Repitier FW compile issue
April 10, 2013 10:56AM
Yes your solution worked nice around the deficit of checks. New github version has now additional tests for this, but no need to update with your trick, as it does the same.

For 0.9 degree steppers you do not need anything special. Just increase steps per mm to match it.

I also hate the stk500 out of sync error. With my now defect gen6 it often helped to hit reset to get it in sync, but not always.

The x/y toggle should show if it is a software problem. Simply because the logic for y is working ok right now and using them on the x pins should do the same.


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!
Re: Repitier FW compile issue
April 10, 2013 07:02PM
Yes the stk500 sync error is a pain, seems like a lot of people get it on the Gen6, probable design flaw as it happens so often, unfortunately the reset trick doesn't work for me.

I still have no luck on the X axis. Though I'm certain that has nothing to with the firmware, looks like the stepper is not getting power, either the stepper died (my guess) or the board is not powering (I've check it's connected well). So not a Repetier issue there.

I suspect the stepper was/is the issue, if it died and some how fed back to the board that would explain why the original FW got scrambled.

Your responses and pressence is greatly appreciated.
Re: Repitier FW compile issue
April 11, 2013 02:40AM
For a final test you could write a small script toggling the stepper pins direction,enable and step every 2 seconds. Then you could measure at the avr pins if the signals come out at the pins (after identifying them). Then you know it's not the avr output that is destroyed. That way you know at least which chip is defect. But desoldering the stepper driver is beyond the capabilities of most users. Removing SMD chips is a pain and the drivers have a heat sink connected with the board as well.


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!
Sorry, only registered users may post in this forum.

Click here to login