I doubt you will get much interest in this, people are happy using thingiverse.comby buzz - For Sale
be pre-warned, my fork is buggy, and a work-in-progress.by buzz - RepRap Host
ATmega644 = the same chip as the Sanguino AtMega168 = the same chip as the original arduino. ( which now also uses a Atmega328 ) As a result these terms are use interchangably, thus: * a "sanguino-based" system is one that uses the ATmega644 chip with the *uino bootware/firmware on it. * an "arduino-based" system is one that uses atmega168 or higher ( eg 328 or even bigger like the Atmel 1by buzz - General
I'm not sure what you changed, but I've been using a Mega for quite some time and all I have to do was tweak the pin assignments and a few assumptive #defines, and the mega worked pretty much out of the box.? It's my DC extruder that didn't work with the standard 5D firmare initially. Buzz.by buzz - RepRap Host
this is both normal, and wrong. it's quite normal for complicated firmware to not behave as you expected because of bad wiring, or bad code ( eg, are you end-stops correctly wired, and is your firmtware configured to expect the same logic level as your endstops provide ), I suggest you try small chunks of "test code" to make sure that each pin is connected and behaving as you desire. As forby buzz - RepRap Host
James, are you still working on this? I am very much interested!by buzz - RepRap Host
welcome Triffid_Hunter and Deano. I have an unreliable repstrap in BNE that I'm working to make more reliable in my 1% spare time. :-) It's been a fun build, but not a fast one. I've been 2+years in the making. my suggestions: Take whatever fast-track method/s you can afford. Get the makerbot electronics if you can ( I have gen2 with an arduino mega, but prettty much any gen2 or gen3 wilby buzz - Australia, Brisbane RepRap User Group
Please post a copy of your program! Many of us would like to see it, and even help if possible.by buzz - RepRap Host
I encourage you to post pictures/details at: Buzz. ( proud owner of a functional junkstrap! )by buzz - Mechanics
Barney, if what you say is true, then I can only summize that one of the following is true: * the RS485 communications protocol is too slow for the real-time step/direction information, OR * the protocol hasn't yet been extended to support the stepper feature/s OR * or it's a work-on-progress, since the 5D code was originally written for single-arduino system/s, and it's a temporary solution tby buzz - RepRap Host
....actually that's not strictly true. I believe the Arduino168 is incapable of it as it's only got 16K or memory, but the Arduino328 (becoming the new standard) has 32K of memory, so should be able to use the code. the Mega has 128K, so has *heaps* of memory.by buzz - RepRap Host
perhaps this is just to do with the fact that the irmware is supporting 3 different basic hardware types ( ie wiring configurations)?by buzz - RepRap Host
it's the "ok" response that the firmware sends back to the PC that is normally used. some recent firmware/s have a buffer to support 4 G code movements / instructions being send and actioned in the DDA at once. Most older firmwares only have one DDA object. BUzz.by buzz - RepRap Host
the file you link to is for multi-arduino systems ( one for the extruder, and one for the XYZ table), and it uses RS485 communications between them. It does NOT have support for 5D gcode/s and acceleration.by buzz - RepRap Host
what OS are you running on? Linux/Windows/Mac will affect the diagnostics that people might want to suggest. At least initially, you need to identify whether the problem is in the PC ( and the java and rxtx code) , or in the firmware ( and the way it responds to the GCode/s ). Can you "capture" the exact serial-over-usb data that is being sent to the arduino? If your code *really* isby buzz - RepRap Host
what's the key identifable difference between "Gen2" and "Gen3" firmware? Are you referring to: * the use of multiple arduino chips and RS485 comms between them * the use of a particular custom-designed integrated PCB * 5D/acceleration logic * separation of realtime/DDA/step generation/asynchronous firmware functions from G-code reading/writing/interpretation/comms/synchronous functionsby buzz - RepRap Host
Has anyone here used PWM in the 5D firmware? I've got a repstrap running on 3D firmware + DC motor for extruder + encodere for feedback and it works well... but in converting over to the 5D firmware, I'm trying to port the PWM changes, and having trouble as the DDA is a very "step" driven logic. My idea/code so-far is based on having a PWM driven DC motor+extruder simulate a stepper with aby buzz - RepRap Host
Using EMC2 in "simulator" mode is quite useful as a a GCODE visualisation tool. I do find that I have to change the -999 "homing sequences" into 0 first - as EMC2 doesn't understand these as meaning "home to 0,0", it understands these to mean travel into negative coordinate space. Anyway, you get a nice tool-path visualisation that you can zoom and scroll around, and it shows the exact G-Codesby buzz - RepRap Host
Just guessing here, but in unusual circumstances ( eg static discharge ) chips have been known to loose/corrupt their bootloader - do you have a different chip to try? this site says: (all that follows is a direct extract from the above) avrdude: stk500_getsync(): not in sync: resp=0x00 If you get the following error message "avrdude: stk500_getsync(): not in sync: resp=0x00" that means thby buzz - RepRap Host
do you mean this overview: Brief: 168 = 16K 328 = 32K Sanguino = 64K Mega = 128K or do you mean these technical specs/descriptions: 168 and 328: finally, the datasheets are here: 168: Sanguino: 328: Mega:by buzz - For Sale
...and check, doublecheck, and tripple-check your settings in the Arduino PC software. Seriously, I use all three of the 168, 328, and Mega chips, and I constantly forget to change the Tools->Board->xxxxx setting to match my chips. Must be early-onset senility. :-)by buzz - RepRap Host
Firstly, you need to define "newer firmwares"? ( do you mean the FiveD_* firmware? ) If you are Still refering to the pre-FourD/FiveD "standard" GCode based formware, then my answer is Yes and No.... I do have a DC-motor driven extruder, but not the original "threaded rod" extruder. I'm using a DC-motor + encoder-wheel + pinch-wheel, and my system is working just fine..... but my firmware isby buzz - RepRap Host
You guy's rock - I love sample code. I've recently taken bits of this code ( minus the interrupt parts ), and used a complete PS/2 ball mouse (and just one of its encoders) as the encoder-interface on my extruder. in manage_speed() I poll the "mouse" for the change-in-coordinates since the last call, and add that to the total "distance travelled since speed change". I then compare the actualby buzz - RepRap Host
may I suggest you going this group: I'm the just-elected president of the brand-new group that are working toward having our own "group hacking space", including my repstrap as one of the projects that'll be worked on.by buzz - Australia, Brisbane RepRap User Group
My problem turned out to be ( of all things ) a bug in the libavr/gcc stuff in a typical Ubuntu 8.04 install. Symptoms include your arduino crashing whenever it encounters a strtol() function. The known fix is to download and upgrade the newer library version from intrepid ( 8.10 ). ( at least it's known after you know about it). :-)by buzz - RepRap Host
Alternatively, you could use the tried-and-tested ABS plastic to mould your reprapped item, not wax, and then cast the ABS in high-temp casting plaster. Finally, heat the entire thing up to 1200+ degrees, and hte ABS will be no more, leaving a perfectly shaped hol for pouring your metal into. THis is what the commercial casting companies do with your wax objects anyway when you send them outby buzz - Plastic Extruder Working Group
downloading a .tar.gz or a .zip file from sourceforge IS a non-SVN version, so you'll be fine.by buzz - RepRap Host
dod you have any issues with the arduino-parallel connections? I have read that parallel ports normally run TTL logic levels, so is it just a case of wiring it directly?by buzz - EMC2
the problem is that step_en_pin is set to (byte)-1, which by the time it reaches the if() is actually calculated as 255, si changing the 'if' statement to this works: if( step_en_pin < 0 || step_en_pin == 255 ) { ...} I figured this out yesterday. I also discovered that there are a bunch of sanguino-only interrupts in extruder.pde that should not be running, but are. :-( These can be fixedby buzz - RepRap Host
my symptom seem to be related to the fact that I'm using the SVN version of the GCode_Extruder firmware on my arduino ( 0013 ) , and after much hacking I determined that there are a couple of major faults in the software because it's assuming a sanguino in a couple of places. If you have issues, try a non-svn version of the firmware.,by buzz - RepRap Host