Using HangPrinter geometry for Wall Plotter?

[TC]

@JoergS5 I didn't intend to build for all. Do you know how just to build for Duet Wifi?

[JoergS5]

@TC in project RepRapFirmare, right click on project, then select Build Configuration - Select - and select your target.
I deleted the Duet 2 target in my project, so I cannot tell you how it's named, probably SAM4E8E (that's the name of the MCU).

I checked, it's probably Duet2_RTOS.

[TC]

@JoergS5 Ok I did not take the different branches into account. Now CoreNG and FreeRTOS work but RRFLibaries dont...
Do you use these branches?

RepRapFirmware: v3-dev
CoreNG: dev
FreeRTOS: master
RRFLibraries: dev
DuetWiFiSocketServer: master
CANlib : master

Or did anything change here that is not updated in the instruction?

[JoergS5]

@TC I had also some problems with the different branches. So now I always use tags, currently 3.1.0 tag for all projects (in github, when opening a project, there is a tag button). They compile well. I've not tested it, but RepRapFirmware has a 3.1.1 tag also, this could work also.

[TC]

@JoergS5 yes now we are very close
Just one more error at the end of Firmware build:

c:/program files/gnu arm eclipse/build tools/2.6-201507152002/bin//sh: crc32appender: not found
makefile:94: recipe for target 'post-build' failed
make[1]: [post-build] Error 127 (ignored)

Did you see that before?

[JoergS5]

@TC in the reprapfirmware\Tools\crc32appender directory is this tool for different operating systems, this must be reachable. I expect it creates a signature or checksum information.

[TC]

@JoergS5 hm but it is definitly there...

[droftarts]

@TC see this thread https://forum.duet3d.com/topic/12275/crc32appender-now-needed-for-rrf
The folder that contains crc32appender needs to be in you PATH.

Ian

[TC]

@droftarts @JoergS5 Ah now its working. Thanks a lot!

[TC]

This post is deleted!

[JoergS5]

@TC you can make a fork of the Reprapfirmware in github and use it to add your files. The advantage would be, you can update easily with the newest updates of the original and check if anything breaks. Sometimes the method's signatures change.

[TC]

@JoergS5 Oh thanks. I just noticed I can't upload the the files here

[JoergS5]

@TC maybe for security reasons

[TC]

@JoergS5 I tried to fork the firmware. Hope I did it right...

https://github.com/TC1991/RepRapFirmware/blob/dev/src/Movement/Kinematics/VerticalPlotterKinematics.cpp
https://github.com/TC1991/RepRapFirmware/blob/dev/src/Movement/Kinematics/VerticalPlotterKinematics.h

Proberbly I will also have to add there the changes in Kinematics.cpp etc.

[JoergS5]

@TC I think you have added it to a wrong branch, to dev. I would use v3.02-dev, there is the current development. The blob in the path confuses me a bit.

[TC]

@JoergS5 Doesn't the link you posted for the robotic kinematics alos contain a blob? https://github.com/JoergS5/RepRapFirmware/blob/v3.02-dev/src/Movement/Kinematics/FiveAxisRobotKinematics.cpp

Ok then I change it to v3.02. Do I have to update my changes in kinematics.h and kinematics.cpp there too?

[TC]

New links:

https://github.com/TC1991/RepRapFirmware/blob/v3.02-dev/src/Movement/Kinematics/VerticalPlotterKinematics.h
https://github.com/TC1991/RepRapFirmware/blob/v3.02-dev/src/Movement/Kinematics/VerticalPlotterKinematics.cpp