So, there is a lot of very useful information that goes by in this thread. Much of it is very difficult for us mere user to glean from the code itself. As an example, take Triffid_Hunter's reply to my most recent question. I know I have had trouble finding some of this info again even though I have seen it before and know it exists. I can't imagine the difficulty a new user might have trying to fby spaztik - Firmware - experimental, borrowed, and future
Jacky2k Wrote: ------------------------------------------------------- > The firmware seems to work on Gen7 now. Heated bed > not tested yet. > I have a suggestion for the firmware, maybe it was > already discussed earlier, don't know > What about seperated config files for electronics > and the mechanicals? And a easy way to choose > between those "board support packages".by spaztik - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- > 100% ram probably means 'more than all' which > leaves zero room for stack- I think 90% is a sane > upper limit. beyond that, expect breakage > Yeah, I thought that might be a bad sign. > latest commit allows DEBUG and BANG_BANG Yes it does and I'll just confirm that it loads and works on the 168. Tby spaztik - Firmware - experimental, borrowed, and future
I tried the input-float branch over the weekend. I noticed Make reported it used 100% of the ram on the 168. It also didn't give a "start ok" on boot and would not respond to any commands. So that is the extent of the testing I can do on that branch. I also found that if I don't define any heaters I can enable debug which let me get more information about the other issues I am having. Unfortunatby spaztik - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- > sounds like gcmd.seen_E isn't being reset or > something, but it's clearly being reset on lines > 350 and 364 of gcode_parse.c.. really not sure > what's going on there Is there anything I can do to see what is going on here? I am thinking of putting sersendf lines immediately before or after the lines yoby spaztik - Firmware - experimental, borrowed, and future
VikOlliver Wrote: ------------------------------------------------------- > I've found that the following produces the correct results > (based on the old 1.3 firmware): > > for (j = 1; j < NUMTEMPS; j++) { > if (pgm_read_word(&(temptable[0])) > temp) > { > // multiply by 4 because internal temp is > stored as 14.2 fixed point >by spaztik - Firmware - experimental, borrowed, and future
Architect Wrote: ------------------------------------------------------- > I currently > have to manually issue the proper M codes to set > the PID values and then my Heater controls began > functioning correctly. > -trout Do you have to do this every time you power up your Arduino? I had this porblem too, but once I had set the PID values I used m134 (I think) to write the valuby spaztik - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- > > Google "PID without a PhD" for tuning help > That helped. My "heater" now seems to work with the values I posted earlier (I_limit = 384 not .375). I've never been happier to get an arduino to turn an LED on and off. Thanks for the help.by spaztik - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- > 8192 * 1024 > 65536, result 0 > > try M130S8 etc Thanks Triffid, I will try this when I get home from work tonight. I am still not certain of what to do here, but this is what I am thinking. 8192/1024 = 8 therefore m130 s8, then do I divide all the default numbers I found in heater.c by 1024, like thisby spaztik - Firmware - experimental, borrowed, and future
Wow 28 minutes, thats gotta be some kind of record or something. I used these defaults from heater.c: #define DEFAULT_P 8192 #define DEFAULT_I 512 #define DEFAULT_D 24576 #define DEFAULT_I_LIMIT 384 and entered them like this: m130 s8192 m131 s512 m132 s24576 m133 s384 m134 the output is now this: m104 s100 T{E:-77, P:-77 * 0 = 0 / I:-384 * 0 = 0 / D:2 * 0 = 0 # O: 0 = 0} PWMby spaztik - Firmware - experimental, borrowed, and future
So, having taken Christmas off from repstrap building and then concentrating on completing fabrication of my cartesian robot, I find myself with little else to do other than software and firmware. While waiting for the thread locker to dry on the penultimate step of fabrication I downloaded the most recent commit from the master branch (4febbe) and uploaded it, to see if I could get the heater woby spaztik - Firmware - experimental, borrowed, and future
Architect Wrote: ------------------------------------------------------- > I decided to > start looking into the code here and getting it > installed on my Duemilanove. I have a couple of > easyDriver steppers from sparkfun which run a few > NEMA17s Wow similar setup. I am using a boarduino (w/168 chip) and 4 Sparkfun Easy drivers and maybe having similar troubles as well. Whichby spaztik - Firmware - experimental, borrowed, and future
I have downloaded the latest commit (eaddc51) and have done some testing. The m115 command still outputs this: ok test_FIRMWARE_NAME:FiveD_on_Arduino FIRMWARE_URL:http1b.com/triffid/FiveD_on_Arduino/ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 TEMP_SENSOR_COUNT:1 HEATER_COUNT:31236 I started wondering if somehow I was compiling old code or maybe it wasn't being uploaded to theby spaztik - Firmware - experimental, borrowed, and future
Thanks for the response Triffid. I will try the m135 code tonight although I am not sure how to use it. I assume this sets which heater the m104 command sets the temp for. If so then I would try "m135 1" or "m135 2" for heaters 1 and 2 respectively or possibly "m135 0" and "m135 1", I'll try both. What are you using as reference for G and M codes? I have been looking here but it doesn't list m135by spaztik - Firmware - experimental, borrowed, and future
I am also having trouble getting the the heater to work. I am currently running the release-candidate-triffid branch (commit 01b5c67) and I think I have everything configured correctly. /***************************************************************************\ * * * 4. TEMPERATURE SENSORSby spaztik - Firmware - experimental, borrowed, and future
cdriko Wrote: ------------------------------------------------------- > > Is the position returned by the m114 command in > number of steps? If so, is this correct or should > it return position in mm or inches depending on > which units you are using? > > > I don't have any return with talking to the > arduino via the serail console > even setting the XONXOFF Noby spaztik - Firmware - experimental, borrowed, and future
cdriko Wrote: ------------------------------------------------------- > I success to connect to it with the > ReplicatorG-5Dsupport of ErikDeBruijn > > with little modifications : > - in serial.c > #define BUFSIZE 64 > (to corresponds to RepRap5DDriver.java) > > - in mendel.c > serial_writestr_P(PSTR("start\nok\n")); > (instead "Start" that'sby spaztik - Firmware - experimental, borrowed, and future
spaztik Wrote: ------------------------------------------------------- > Anyway, the errors I get now > are these: > > avrdude: Device signature = 0x000000 > avrdude: Yikes! Invalid device signature. ... > I will probobaly try using the -F option to force > avrdude next but I suspect that will just cause a > verification error as is seen in the bug report > linkedby spaztik - Firmware - experimental, borrowed, and future
cdriko Wrote: ------------------------------------------------------- > 1 - I can't compile under arduino 0018 (or more > recent) because can't find "sys/time.h" The only branch I have successfully compiled with the arduino IDE is "release-candidate" > 2- So I compile it with succes with avrdude BUT > replicatorg0013 say everytime 'machine reset > called' > but a can open conby spaztik - Firmware - experimental, borrowed, and future
Triffid_Hunter Wrote: ------------------------------------------------------- > try ( cat <&3 & cat >&3; kill %! ; ) > 3<>/dev/arduino for a super simple talker. set > port up with stty first, see func.sh for more > thoroughly tested examples > > If you enable xon/xoff flow control, you can paste > rather large chunks of gcode in and it won't miss >by spaztik - Firmware - experimental, borrowed, and future
QuoteThis happens if you leave 'GEN3' defined, as the GEN3 electronics use pins (and uarts) that don't exist on a '168. I think it's defined both in the Makefile and in config.h at the moment- I probably should fix that. Thanks that worked. I am now able to make and make program without errors. However when I try to run ./sender.sh I get these errors: ./sender.sh: line 6: waitfor: command not fby spaztik - Firmware - experimental, borrowed, and future
I will likely be buying a combination heater barrel/nozzle and thermal barrier from you in the near future. I am wondering if you have considered manufacturing the hobbed bolt for Wade's extruder. If you offered this part I would buy one and I suspect it would be another good seller.by spaztik - For Sale
I am nearing completion of my Mcwire cartesian bot and have been using this firmware to test so far. I have been using the release-candidate branch to date as it is the only one I can get to compile in the Arduino IDE. I have tried a few times to compile this firmware using make with winavr on windows and on my Debian machine with no luck. Most recently I have tried release-candidate-triffid andby spaztik - Firmware - experimental, borrowed, and future
I promise.by spaztik - For Sale
Quoterocket_scientist I made a guess and got the Adruino Mega and four Easy Driver boards from SParkfun Here is an example of those electronics in use. I bought easy drivers too. You have to choose higher voltage motors to get the same torque from 750ma though.by spaztik - General
Printing buildings would be considered civil engineering, right? printing buildingsby spaztik - General
I am just wondering if there has been any discussion about a manually controlled pick and place tool. It seem to me that the biggest problem with working with smt components is seeing and manipulating the tiny parts. I think a pick and place tool doesn't necessarily need to be fully automated to be a useful tool. A "print head" with a pick and place tool and a magnified camera and manual controlby spaztik - Pick-and-Place Electronic Assembly (and robots!)
Makerbot has indicated they will carry Gen 3 electronics till they can't sell them any more. Fair enough, I was misinformed on that point. $200 plus motors is still getting up there in price though.by spaztik - General
Just to reiterate by $500 I meant perhaps $300 materials and 20 hours labor or $400 materials and 10 hours labor or $100 materials and 40 hours labor. I am not sure if this is a response to my comment about thinking twice about a price tag over $500, but I'm gonna pretend like it is. I meant $500 in materials cost, I value my time much lower in this endeavor as this is my hobby. If I wasn't doinby spaztik - General
once you build your McWire you slowly build parts to make it go faster. You can print Mendal style pulleys and buy belt. You can print Vik's ball chain pulleys and buy ball chain or you can print Forrest's rack and pinion and buy nothing That is a very good solution and one that I am seriously considering myself, but I won't lie, I'm cheap and the more parts I can avoid buying (especially temporby spaztik - General