Version 2 Compilation Errors

lmcbmai

I'm following the instructions from https://docfirmwarev2.repetier.com/ and trying to compile firmware version 2 (the very 1st time). I am getting errors that are most likely caused by incorrect settings in my Configuration file. I'd appreciate any help/guidance.

My IDEX printer has two X motors, one Y motor, two Z motors and 2 extruder motors. So, 7 motors in total. Each motor is connected to its own driver on Ultratronics Pro board. 'Dual X Axis Printer' configuration sample published here https://docfirmwarev2.repetier.com/config/printer_type/ contains the following

#define NUM_AXES 5 // X,Y,Z and E for extruder A,B,C would be 5,6,7

Why this example contains 5 axes? Dual X printer should have at least two X, one Y, one Z and 2 extruder motors. So, the number should be 6 or higher. If not, than what is the meaning of AXES in this context?

Other 2 settings that are puzzling me are

#define MOTORS <br/> { &XMotor, &YMotor, &ZMotor, &AL1Motor, &AL2Motor }

#define MOTOR_NAMES <br/> { PSTR("X"), PSTR("Y"), PSTR("Z"), PSTR("Adj. 1"), PSTR("Adj. 2") }

I tried to replace the last 2 entries in each of these lines with with A, B, C and D, but getting several errors like this:
<blockquote class="Quote">src\motion/MotionLevel3.h:113:9: error: 'AMotor' was not declared in this scope

Prior to this I was getting several Servo related errors, nevertheless I defined NUM_SERVOS as 0. Here are couple of them:

src/Configuration_io.h: In constructor 'Servo1Class::Servo1Class()':
src\io/io_servos.h:36:18: error: 'servoMicroseconds' is not a member of 'HAL'
HAL::servoMicroseconds(slot, neutral, 1000); <br/> ^
src/Configuration_io.h:179:1: note: in expansion of macro 'SERVO_ANALOG'
SERVO_ANALOG(Servo1, 0, Servo1Pin, 500, 2500, 1050)
~~~~~~_~~

I was able to get rid of these errors by commenting out the line

// SERVO_ANALOG(Servo1, 0, Servo1Pin, 500, 2500, 1050)

from Configuration_io.h file, but I don't know if this is good workaround.

Thanks

Repetier

Hope you are refering to Stacker X2 config for IDEX. That is my idex I run with V2 and it's configuration that works fine.

5 Axis are X, Y, Z, E and A - A axis is second X axis but works independent. The 2 extruders share E axis with the active one being inserted as E stepper.

You sample seems from Felix Pro 1 which has 2 extra steppers to physically level bed AL1Motor and AL2Motor belong to that. You do not have them. In your case it looks more like

#define NUM_MOTORS 6

#define MOTORS </div>

{ &XMotor, &YMotor, &ZMotor, &AMotor, &E1Motor, &E2Motor }

#define MOTOR_NAMES </div>

{ PSTR("X left"), PSTR("Y"), PSTR("Z"), PSTR("X right"), PSTR("E0"), PSTR("E1") }

You also need to add A motor for send x axis like done in stacker X2 sample.
As said better take that as preset as it is same printer type and default at least compiles for stacker board. You need to set it of yourse to ultratronics and maybe change some pin numbers and heaters - they are quite unusual.

lmcbmai

@Repetier Thanks for the hint! I started from stacker X2 sample and spent almost whole day setting up version 2 on my IDEX. I made good progress, but to-do list is still pretty long. I documented all problems I faced and how I addressed them. I'm planning to make a separate post here describing this. Hopefully it will save others time and help developers to understand what is regular user's experience when upgrading from version 1 to version 2.

While most of the issues were caused by incorrectly settings in header files, I experienced one error that I am pasting below. Not sure what is causing it. I temporarily commented out BEEPER_PIN and moved on, but would be good to know what is causing this:

src\PrinterTypes\Printer.cpp:94:10: error: 'TonePacket' in 'class Printer' does not name a type
Printer::TonePacket toneQueueBuf[Printer::toneBufSize];
~~~~_~~
src\PrinterTypes\Printer.cpp: In static member function 'static void Printer::addToToneQueue(TonePacket)':
src\PrinterTypes\Printer.cpp:1494:5: error: 'toneQueueBuf' was not declared in this scope
toneQueueBuf[seekToneIndex] = packet;
~~~~~~_~~
src\PrinterTypes\Printer.cpp: In static member function 'static void Printer::processToneQueue()':
src\PrinterTypes\Printer.cpp:1509:41: error: 'toneQueueBuf' was not declared in this scope
if ((curTime - lastToneTime) >= toneQueueBuf[curToneIndex].duration) {
~~~~~~_~~
*** [.pio\build\due\src\PrinterTypes\Printer.cpp.o] Error 1

Apart from this I have 2 questions:

- In version 1 I was able to have 2 Z-motors connected to separate stepper drivers. They were moving in sync. How can I replicate such setup in version 2? My 2nd Z-motor is connected to Extruder 2 slot.

- Configuration file contains several references to TMC drivers which I don't have (yet). Is there any particular place where I need to disable them in configuration files?

Thanks

Repetier

Tone problem was a bug I fixed and thought I had uploaded. Have now updated github with proper fix.

You define 3 motors for Z. Z1Motor and Z2Motor are regular motor drivers for Z and E2 axis. The third one is a mirror motor driver:
STEPPER_MIRROR2(ZMotor, Z1Motor, Z2Motor, endstopNone, endstopNone);

Use everywhere ZMotor - it send identical signals to Z1Motor and Z2Motor. Same if you need 3 or 4 motors or for any other axis.

TMC nothing to disable. If they get not configured they are not used. The advantage of the module concept that it only includes used modules.

lmcbmai

Thanks, this worked.
I was making really good progress until I stumbled on the extruder motor step per mm setting, or rather lack of it. I need to reduce current value 2.66 times. Tried to define EXT0_STEPS_PER_MM and EXT1_STEPS_PER_MM values but that had no effect. I cannot find anything about this in documentation and other sample configs. Could you please advice where/how to set extruder steps ?

Thanks again!

RAyWB

you have to adjust it in configuration_io.h , extruder is handled as tool

search for TOOL_EXTRUDER

// TOOL_EXTRUDER(name, offx, offy, offz, heater, stepper, resolution, yank, maxSpeed, acceleration, advance, startScript, endScript)

(resolution is the steps/mm value)

also refer to documentation :

https://docfirmwarev2.repetier.com/config/tools<br/></div><br/><br/>

lmcbmai

@RAyWB Thanks for your reply. I was searching documentation under steppers section...
I managed to set this up correctly right before seeing your post. I changed the following 2 lines.

TOOL_EXTRUDER(ToolExtruder1, 0, 0, 0, HeaterExtruder1, E1Motor, 1.75, 140, 5, 30, 5000, 177, "M117 Extruder 1", "", &Fan1PWM)
TOOL_EXTRUDER(ToolExtruder2, 0, 0.1, 0, HeaterExtruder2, E2Motor, 1.75, 140, 5, 30, 5000, 177, "M117 Extruder 2", "", &Fan2PWM)

Sample configuration that I used had 500 where I now have 140.

Thanks

lmcbmai

Updated Printer.cpp file to the latest revision. This cleared Beeper related compilation errors and Beeper is working now. Thanks to @Repetier

Made the 1st successful test cube print after manually leveling the bed.

Now, trying to configure ABL. With the following settings Print-head moves to the position of the first measurement, then the board resets itself.

//Z-PROBE
#define Z_PROBE_TYPE 1 // 0 means no ABL
#define Z_PROBE_HEIGHT 4.5 // Distance bed-nozzle when trigger switches
#define Z_PROBE_BED_DISTANCE 5.0 // Optimal starting distance
#define Z_PROBE_SPEED 5 // Speed for z testing
#define Z_PROBE_X_OFFSET 26.5 // x offset relative to extruder 0,0 offset
#define Z_PROBE_Y_OFFSET 18 // y offset relative to extruder 0,0 offset
#define Z_PROBE_COATING 0 // Coating thickness if not detected by probe
#define Z_PROBE_DELAY 0 // Extra delay before starting again. Only needed on electronic probes keeping state for a while
#define Z_PROBE_REPETITIONS 2 // How often should we probe, 1 is minimum
#define Z_PROBE_USE_MEDIAN 0 // 0 = use average, 1 = use middle value after ordering z
#define Z_PROBE_SWITCHING_DISTANCE 1.5 // Minimum distance required to safely untrigger probe - used for faster repeated measurement
#define Z_PROBE_BORDER 10 // Safety border to ensure position is allowed
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
#define Z_PROBE_RUN_AFTER_EVERY_PROBE ""
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define LEVELING_METHOD 1
#define GRID_SIZE 5
#define ENABLE_BUMP_CORRECTION 0 // CPU intensive, so only activate if required
#define BUMP_CORRECTION_START_DEGRADE 0.5 // Until this height we correct 100%
#define BUMP_CORRECTION_END_HEIGHT 2 // From this height on we do no correction
#define BUMP_LIMIT_TO 2 // Maximum allowed correction up/down

Log output of G32 command shows this:

>>>g32
SENDING:G32
ok 0
Info:Autoleveling disabled
X:-54.00 Y:343.00 Z:150.000 E:0.0000 A:406.00
busy:processing
endstops hit: x_min:L y_max:L z_max:H a_max:H
Warning:Endstop for axis 4 did not untrigger for retest!
SelectTool:0
X:-54.00 Y:343.00 Z:150.000 E:0.0000 A:406.00
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
busy:processing
start
Info:Watchdog Reset
Free RAM:76512
Card successfully initialized.
EEPROM read from sd card.
SelectTool:0
ok 0

Looks like I am missing something related to z-probe sensor/Endstop settings. As you can see I tried to add

#define Z_PROBE_PIN ORIG_Z_MIN_PIN

to Configuration.h file, nevertheless it was not present here https://docfirmwarev2.repetier.com/config/bed_calibration under Standard Z-Probe section, but it did not help. Any suggestions ?Thanks

Repetier

#define Z_PROBE_PIN ORIG_Z_MIN_PIN

is not needed any more in V2. Configuration should be complete since it compiled.
I see you did not move A axis far enough back in homing sequence hence the untrigger warning.
What happened afterwards until watchdog reset happened?
What is your stepper frequency set?

#define STEPPER_FREQUENCY 120000

When I had this higher on 153000 watchdog reset happened also sometimes on longer z moves due to cpu load > 100% leaving no time for main thread. That might have happened here.

lmcbmai

Stepper frequency is 120000.
I executed G28 that properly homed all axes as per my settings

#define X_HOME_PRIORITY 2
#define Y_HOME_PRIORITY 1
#define Z_HOME_PRIORITY 0
#define A_HOME_PRIORITY 2

First was Z to Zmax, then Y to Ymax, then X to Xmin and finally A to Xmax.

Then I executed G32. It repeated homing moves and then started to simultaneously slowly move bed up and left print-head with probe towards (I think) X=Z_PROBE_BORDER Y=Z_PROBE_BORDER. After reaching that point print-head made quick diagonal move to what looked like X=0 Y=0 and then couple of seconds later firmware restarted.

Sorry, I cannot understand, if we do not specify Z-probe pin, how can it even make the measurements? My probe is connected to Zmin endstop plug of mainboard and that's how it was configured in version 1 and worked fine. All my endstops and probe are schematically identical. They contain optocouple ITR9606-F and 2 resistors.

Thanks

lmcbmai

Forgot to mention - right now I don't have Zmin endstop defined in configuration. Do I need to add it for z-probe?

RAyWB

from my setup

configuration_io.h :

ENDSTOP_SWITCH_HW(endstopZMin, IOEndstopZMin, Z_AXIS, false)

has to be defined and in configuration.h

there should be

// Define ZProbe by referencing a endstop defined
CONFIG_VARIABLE_EQ(EndstopDriver, *ZProbe, &endstopZMin)

in my setup i have home at z-max and probe at z-min input

difference i have is in home priority for a-axis , but i have a real 4th rotational axis in my setup as mill

#define X_HOME_PRIORITY 2
#define Y_HOME_PRIORITY 1
#define Z_HOME_PRIORITY 0
#define A_HOME_PRIORITY 3

lmcbmai

@RAyWB Gave it a quick try before going to work, but there was no change in behavior. Zmin did not appear in M119 output. Will continue looking into it this evening.

Thanks

RAyWB

from your log before :

endstops hit: x_min:L y_max:L z_max:H a_max:H

seems that z endstop and a endstop don´t untrigger, so check that values( in configuration.h):

#define ENDSTOP_X_BACK_MOVE 3
#define ENDSTOP_Y_BACK_MOVE 3
#define ENDSTOP_Z_BACK_MOVE 3
#define ENDSTOP_A_BACK_MOVE 3

may be you can share your configuration.h and configuratio_io.h

Repetier

I currently work on rumba32 support (ST32 based board) which I want to put into my now non working delta. When done I will also test z probing which will be similar to your case with z max homing. Then I will see if there are problems. Currently I only have one "special" printer with zprobe using the 4 point z probe which worked. But might take some days for me to test this since the hardware layer is making troubles.

lmcbmai

Here is the latest status:

- Discovered and fixed half-broken wire going to Endstop-A. Now A-stop works reliably.
- Made few changes to configuration files:
- Commented out #define NO_AMAX_ENDSTOP_TEST
- Replaced #define ZPROBE_ADDRESS nullptr with #define ZPROBE_ADDRESS &endstopZMin
- Set FEATURE_Z_PROBE to 1 (it was 0 before)
These changes caused several compilation errors. The 1st was saying that NUM_EXTRUDER is not defined. I already had line #define NUM_TOOLS 2. It appears that is not sufficient. Added #define NUM_EXTRUDER 2 to Configuration.h file. This took care of the 1st error, but the following errors remain:

src\communication\GCodes.cpp: In function 'void GCode_134(GCode)':
src\communication\GCodes.cpp:725:25: error: 'Extruder' has not been declared
int startExtruder = Extruder::current->id;
~~_~~
src\communication\GCodes.cpp:726:5: error: 'extruder' was not declared in this scope
extruder[p].zOffset = 0;
~~_~~
src\communication\GCodes.cpp:726:5: note: suggested alternative: 'BitOrder'
extruder[p].zOffset = 0;
~~_~~
BitOrder
src\communication\GCodes.cpp:759:14: error: 'startProbing' is not a member of 'Printer'
Printer::startProbing(true);
~~~~~~_~~
src\communication\GCodes.cpp:761:9: error: 'Extruder' has not been declared
Extruder::selectExtruderById(p);
~~_~~
src\communication\GCodes.cpp:762:36: error: 'runZProbe' is not a member of 'Printer'
float refHeight = Printer::runZProbe(false, false);
~~~_~~
src\communication\GCodes.cpp:773:13: error: 'Extruder' has not been declared
Extruder::selectExtruderById(i);
~~_~~
src\communication\GCodes.cpp:774:37: error: 'runZProbe' is not a member of 'Printer'
float height = Printer::runZProbe(false, false);
~~~_~~
src\communication\GCodes.cpp:806:5: error: 'Extruder' has not been declared
Extruder::selectExtruderById(startExtruder);
~~_~~
src\communication\GCodes.cpp:807:14: error: 'finishProbing' is not a member of 'Printer'
Printer::finishProbing();
~~~~~~~_~~
src\communication\MCodes.cpp: In function 'void MCode_890(GCode)':
src\communication\MCodes.cpp:1376:28: error: 'bendingCorrectionAt' is not a member of 'Printer'
float c = Printer::bendingCorrectionAt(com->X, com->Y);
~~~~~~~~~~~~~_~~
*** [.pio\build\due\src\communication\GCodes.cpp.o] Error 1

I don't want to overload this thread with the content of my configuration files, so sharing them via Dropbox: https://www.dropbox.com/sh/eauiinu3uvew8yh/AABI34K00lxXXRYlbjJO8QOOa?dl=0<br/><br/>When I compile this configuration with FEATURE_Z_PROBE=0, I can see all end-stops in M119 printout

endstops hit: x_min:L y_max:L z_min:H z_max:L a_max:L Z-probe state:H

but z_min and Z-probe states do not change.

Reverted firmware back to version 1 to compare behavior - z_min and Z-probe end-stop states did change. So, this is not a wiring issue at this time.

endstops hit: x_min:L x_max:L y_max:L z_max:L Z-probe state:L

Thanks

lmcbmai

Just a separate note: I started new thread https://forum.repetier.com/discussion/7039/firmware-upgrade-from-version-1-x-to-2-x-user-experience that contains my printer's specifications. I am planning to share there detailed description of my experience upgrading from version 1 to version 2.

RAyWB

as i´m busy for the next 2days i´ll try your config on january 2nd.

best wishes for 2020 !

Repetier

NUM_EXTRUDERS is what was used in V1. Making the firmware more flexible this has become NUM_TOOLS since it could also be laser or spindle or syringe in future. With your FEATURE_Z_PROBE definition you triggered old codeparts that have not been converted yet. Do not add that define - it is not used in V2 parts. Z Probe is define only by

#define Z_PROBE_TYPE 2 // 0 = no z probe, 1 = default z probe, 2 = Nozzle as probe

which tells which variant it is. Next type will be 3 = BLtouch which is what I want to add to the delta I'm working on.
Without FEATURE_Z_PROBE it will only the V2 zprobe parts that are already converted. But as said I need some more days to convert printer so I can also test that variant and then hopefully get the same problem to fix it. If not I can at least post my settings that work.

Also big thanks for the testing of V2. It helps testing with different variants which is the main problem in development. Parts I use for my test printers work pretty well so far, but I know there are many other combinations and these can trigger unknown problems, als I hope they are all quite easy to solve since most things are already functional and some already better then in V1.

lmcbmai

@RAyWB Thanks a lot!

@Repetier That's good to know. I will remove NUM_EXTRUDER, revert FEATURE_Z_PROBE to 0 and continue "playing" with other settings. I will be posting everything I am doing in another thread. Meanwhile

HAPPY NEW YEAR TO EVERYONE!! Very best wishes from Seattle!