Quotedc42 Could it be anything to do with the changes to the Pins-RADDS.h file to support the additional heaters? LOL, No disrespect intended dc42. Just there seems to be a disconnect between the Due and current RRF build. As you're a Duet guy, don't expect you to have any means of testing builds for RADDS/Due. Various builds of Bossac don't communicate well with the Due, just check the Arduinoby prot0typ1cal - CoreXY Machines
Type EP-2 conductive rubber, from 1-100mm thick.by prot0typ1cal - General
Not ruling anything out ATM. Gonna roll back and try as a base build, just as a CoreXY. Maybe even give Repetier a go, as it supports the PanelDue with json, though would need to add CoreXYU.by prot0typ1cal - CoreXY Machines
Well, the new Due arrived along with yet another microUSB cable (now have 5). At least it's new, nothing else was. Same "Device not found" and "SAM-BA operation failed" So tried different flavors of Bossac, seems the Due likes the version dated 11/3/2015 (from Arduino IDE 1.6.1). No problems connecting to the 'bossac programming port' and writing the bin to flash. Doesn't care which USB cable eiby prot0typ1cal - CoreXY Machines
Recommend Slick 50 One Lube, a short shot on each under-side on the bearings. Move while still wet to circulate balls. Not only is One Lube a rust preventative, it also deposits a micro layer of PTFE. You can also spray some on a cotton rag and wipe the rails down to clean them.by prot0typ1cal - Mechanics
Ordered a new Arduino Due R3, should have it in a few days. Tried everything with the old board: Bossa, bossac command lines from Arduino IDE hardware tools and Bossa, both native and programming ports, resistor dump from RX) to GND, etc... Runs sketches from Arduino IDE fine (blink), just won't boot bin files from flash, even when 100% verified ,no response in serial monitor. And yes, tried 4by prot0typ1cal - CoreXY Machines
Thanks o_lampe Still having issues flashing the bin. The comment in the inf file says "pre 1.18" for the driver you posted. Trying to flash RRF 1.19beta8. Odd thing is that if I use Arduino IDE can upload the blink sketch, over the programming due port, and it runs fine. Cannot get Bossa or command line bossac to upload with the programming port, get either SAM-BA failed or no device on com. Upby prot0typ1cal - CoreXY Machines
You may not have to switch nozzles. It's possible to print 0.1 and 0.3 layer heights with a 0.4 nozzle. Unfortunately I've only seen this option for supports via the Makerbot slicer. Model as 0.1 and supports as 0.3 Be cool if you can do this for perimeters and infill, with or without nozzle (print head) swaps. doh, nm. Didn't read the op clearly. Just add a few more perimeters, the small gapsby prot0typ1cal - General
Plugged in a 4x20LCD/SD for RADDS, blank screen. Obviously something is wrong, gotta narrow it down before ordering replacements. Bummer is the controls were the first thing I purchased for this build, almost a year ago.by prot0typ1cal - CoreXY Machines
Surprised you didn't use a reamer on the small through hole. Under the impression surface finish and size was critical in this location.by prot0typ1cal - Look what I made!
I'm concerned either the due or RADDS is bad, most likely the Due. Flashed it more times than I can count using both Bossa and command line bossac, each time the verify said all's good, yet no response sending commands over the USB. COM port won't stay connected. Seriously don't need these problems. Have a few more things to try before taking a hammer to it.by prot0typ1cal - CoreXY Machines
@dc42 Posted the "fix" on the duet3d forums. Though don't exactly know the why. Used Bossa to write my due, plugged Due into RADDS, put all the SD files in sys/ folder and inserted micro SD card into the RADDS, connected up the PanelDue, powered up... Panel Due says "connecting" only never does. from the config.g M575 P1 B57600 S1 ; Comms parameters for PanelDue PanelDue is also set at 57600by prot0typ1cal - CoreXY Machines
Downloaded beta8 bin and wrote and verified it to the Arduino Due. Powered up and now the PanelDue is stuck "connecting". Traced all the leads, all contacts are solid on the 4 pin outs Tx to Din and Rx to Dout, obviously V+ and gnd are correct otherwise there'd be no display at all. config.g and PanelDue both set at 57600 baud. 'bout the PanelDue, really like the "Dark" display, maybe it's just mby prot0typ1cal - CoreXY Machines
Baltic Birch is IMO the best choice for plywood. 3/4" should be strong enough for even a large printer. Heck, if you ever worked with the stuff, 1/2" will do.by prot0typ1cal - CoreXY Machines
Pikefish seemed to have an identical error, IDK, just seem to be going faster in ever decreasing circles...by prot0typ1cal - CoreXY Machines
Yea, when I build Lars' fork for Duet, it lists the syscalls.o and builds fine. 'll try deleting the reprapfirmware project and importing it new rather than refreshing it. EDIT: Same errorby prot0typ1cal - CoreXY Machines
Mine looks the same, straight cut-n-paste from my install of Eclipse Neon2 Linker Expert settings Command line pattern: ${COMMAND} ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX}${OUTPUT} ${LINK_FLAGS_1} ${workspace_loc:/${CoreName}/RADDS/cores/arduino/syscalls.o} ${INPUTS} ${LINK_FLAGS_2} Confirmed file by navigating in Windows, C:\Eclipse\Firmware\CoreNG\RADDS\cores\arduino\syscalls.oby prot0typ1cal - CoreXY Machines
Okay, did a "Refresh". No warnings. Just the same old error: 'Building target: RepRapFirmware' 'Invoking: Cross G++ Linker' arm-none-eabi-gcc -L"C:\Eclipse\Firmware\CoreNG\RADDS" -Os -Wl,--gc-sections -Wl,--fatal-warnings -mcpu=cortex-m3 -TC:\Eclipse\Firmware\CoreNG\variants\RADDS\linker_scripts\gcc\flash.ld -Wl,-Map,C:\Eclipse\Firmware\RepRapFirmware\RADDS/RepRapFirmware.map -o "RepRapFirmwareby prot0typ1cal - CoreXY Machines
PATH for collect is in the Environment, so I don't think that is the issue. Here's the complete list of errors for the binary: make all 'Building target: RepRapFirmware.elf' 'Invoking: Cross G++ Linker' arm-none-eabi-gcc -L"C:\Eclipse\Firmware\CoreNG\RADDS" -Os -Wl,--gc-sections -Wl,--fatal-warnings -mcpu=cortex-m3 -TC:\Eclipse\Firmware\CoreNG\variants\RADDS\linker_scripts\gcc\flash.ld -Wl,-Mby prot0typ1cal - CoreXY Machines
One application for the induction heater may be high melt point filament, like pewter wire. 3d print metal? why not?by prot0typ1cal - General
Right then, Found 2 issues why the "cannot find: -1CoreNG 1. When building CoreNG for RADDS, eclipse left the "lib" prefix off, making CoreNG.a invisible until renamed to libCoreNG.a easy fix, in properties>C/C++ Build>Settings>Build Artifact, not only set Artifact Type to Static Library, Artifact extension to a, also set Output prefix to lib. For some reason prefix was blank. Then ofby prot0typ1cal - CoreXY Machines
Cable management usually last on the check list. Waiting for my printer to work so I can print a control case. 3D printed parts can be as strong as aluminum, just need to be bigger and add more fasteners. Your printer looks pretty sturdy, with a massive build volume. Well done. Glad I could be of inspiration. Only wish I could have finished mine 1st, LOLby prot0typ1cal - CoreXY Machines
I'd use rails for the Y and Z, and anodized aluminum tubes for the X rods. Larger the diameter the better for the span. Drop the hot end between the X rods, and calculate the center of gravity for the carriage to be on plane with the center of the X rods for least deflection (moment of inertia). Stay away from Titanium, unless you can get it hard anodized (type III). You can buy hard anodized aby prot0typ1cal - General
Quotedc42 The collect2.exe program should be part of your Arduino GCC installation I think. I suggest you search for it, and if you find it, make sure it is on PATH. Did that, same message.(added to PATH, in Properties>C/C++ Build>Environment) Also tried adding (then removing after error) the CoreNG/RADDS directory to anywhere and everywhere because of "ld.exe: cannot find -1CoreNG". Onlyby prot0typ1cal - CoreXY Machines
Fresh copies, check. Okay, set CoreNG to build as a Static Library. Now makes a CoreNG.a in C:\Eclipse\Firmware\CoreNG\RADDS However, still can't get RRF to build. Been hammering away on all kinds of settings and Google searches to no avail. From the Properties>C/C++Build>Settings>Build Steps It appears the output should be a *.elf (executable), so set Build Artifact to Executable withby prot0typ1cal - CoreXY Machines
If I build CoreNG for SAM3X8E, get 'Finished building target: libCoreNG.a' When trying to build CoreNG for RADDS get: ./variants/RADDS/startup_sam3x.o: (.vectors+0x0): undefined reference to `_estack' collect2.exe: error: ld returned 1 exit status make: *** Error 1 So, built CoreNg for SAM3X8E. Building RepRapFirmware (beta7+1) for RADDS get the following, c:/arduino-1.5.8/hardware/tools/gby prot0typ1cal - CoreXY Machines
Thanks Lars. Keeping an eye on Github. Though I'll need the RADDS version when dc42 gets to it :pby prot0typ1cal - CoreXY Machines
Quotebobbyd I am so far behind you guys. I'm still designing mine, and once I'm done that, I have to test all of the tolerances and then I have to save up because I'm just a poor college kid lol. I'm starting to doubt that I can finish by the end of summer. Dood, I started sketching back in August of last year. First CAD renders were posted on Thingiverse at the end of September. If I can getby prot0typ1cal - CoreXY Machines
Finally got my Due flashed using Bossa. Bastard wouldn't connect until used the native port. Will be plugging it up to the RADDS tonight, and wiring up the extruders this weekend. Still have to build my bed up, have the RepRap 300x300 big bed and a chunk of 1/4" ATP-5. Plan on using a slab of concrete fiberboard under the heater for insulation. Regarding axes, about homing the U, from what I gby prot0typ1cal - CoreXY Machines
Quotelars.arvidson Did my first prints today! Still pretty ghetto and a lot to fix on the printer. I have seen better first layers but still a big milestone in my project! Now I need more axis than 6 for bed leveling... Next firmware hack me think... Looking pretty damn nice if you ask me. You're first to print CoreXYU !!! /me jealous.by prot0typ1cal - CoreXY Machines