HEy guys, I was having several of these issues also. I found that moving the #include "Temperature.h" in the FiveD_GCode_Interpretor to above #include "configuration.h" solved alot of it. #include #include #include #include #include #include "WProgram.h" #include "vectors.h" #include "features.h" #include "Temperature.h" #include "configuration.h" #include "hostcom.h" #include "intercom.h"by Adam.m.Nelson - Firmware - mainstream and related support
We've made some progress, but the Z-Axis is buggy. When using the Reprap firmware the only way I can get the Z Axis to spin (and not just sit there and hum) is to crank the Z_STEPS_PER_MM to 20 or lower (our calibrated value should be 1454.545454), This although not accurate at all allows the Z Axis to move in either direction. The min and max feed rates seem to have no bearing on the speed atby Adam.m.Nelson - Firmware - mainstream and related support
brnrd, Take a look here, this guy shared his working code, it'll just need to be tweaked for your application. Forum Linkby Adam.m.Nelson - Firmware - mainstream and related support
Should have searched this one out more, found an answer http://forums.reprap.org/read.php?4,78400by Adam.m.Nelson - Reprappers
brupje I could have your babies! Thanks for the upload!!by Adam.m.Nelson - Reprappers
Hey there! Is anyone using Gen3 electronics on their Reprap? Motherboard v1.2, Extruder controller v2.2, Stepperdrivers 2.xx? I've recently gotten back to my build, and the Reprap world seems to have moved to Gen6/7 mostly, but I already have my Gen3 electronics. I've spent the last month plus trying to get the firmware set-up. I keep running into what my best guess are buffer issues. I'veby Adam.m.Nelson - Reprappers
I went back and tried the v102 build for Gen3 electronics same thing.by Adam.m.Nelson - Firmware - mainstream and related support
According to the firmware its version "1.8", from the 20110509 build. #define REVISION "1.8" // arbitrary, based on comets in top of main file... // definitions for M115 machine capabilities command, see #define xstr(s) str(s) #define str(s) #s #define PROTOCOL_VERSION "0.1" // Make sure you really are compliant with what you advertize here #define FIRMWARE_NAME "FiveD" // Please change this nby Adam.m.Nelson - Firmware - mainstream and related support
It dawned on me that this is no longer a programming error, so I should probably start a new thread. Moved here: http://forums.reprap.org/read.php?146,84522by Adam.m.Nelson - Firmware - mainstream and related support
ok, so I can communicate, I've tested all the inputs, and can move all the axis (including the extruder). However my Mendel still loves to crash. Regarding the RS485_BUF_LEN I found the following: The Original value was 20. Tested Values that give me a debug led 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 60, 63 Failing values 36 and lower, 64 and higher. Settings that communicaby Adam.m.Nelson - Firmware - mainstream and related support
F&% Ya! Found it! Turns out the RS485_BUF_LEN was set to 20 which is too small? Note: In the comments in intercom.h it says this setting is in the configuration.h file, but its really in the intercom.h file line 71. I doubled its value from 20 to 40 and have atleast stable communication, Looks like it needs tweaking, but its a start. The debug LED has also started blinking again. I goby Adam.m.Nelson - Firmware - mainstream and related support
I started ontop of another thread so I move the important stuff over here. Original thread: Here Ok curiosity got the best of me and I went back to look at the generic firmware again with a fresh mind. The code is indeed running, all be it not very well. When I use the serial monitor I see the following message stastststststststststststst ect. I changed up the start message to make sure and surby Adam.m.Nelson - Firmware - mainstream and related support
ok, so I can communicate, I've tested all the inputs, and can move all the axis (including the extruder). However my Mendel still loves to crash. Regarding the RS485_BUF_LEN I found the following: The Original value was 20. Tested Values that give me a debug led 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 60, 63 Failing values 36 and lower, 64 and higher. Settings that communicatby Adam.m.Nelson - Firmware - mainstream and related support
F&% Ya! Found it! Turns out the RS485_BUF_LEN was set to 20 which is too small? Note: In the comments in intercom.h it says this setting is in the configuration.h file, but its really in the intercom.h file line 71. I doubled its value from 20 to 40 and have atleast stable communication, Looks like it needs tweaking, but its a start. The debug LED has also started blinking again. I gby Adam.m.Nelson - Firmware - mainstream and related support
Ok curiosity got the best of me and I went back to look at the generic firmware again with a fresh mind. The code is indeed running, all be it not very well. When I use the serial monitor I see the following message stastststststststststststst ect. I changed up the start message to make sure and sure enough I got 123121212121212121212 in a never ending stream. Does anyone have any ideas? I'mby Adam.m.Nelson - Firmware - mainstream and related support
After a team effort and 6 hours of playing around our Mendel still makes little sense with the generic firmware. If we re-start the host software enough times we will get a combination of 5 different outcomes, eventually leading to the debug LED flashing, and the unit reporting a temperature. We thought this was great until we determined that doing anything but watching the temperature or turniby Adam.m.Nelson - Firmware - mainstream and related support
Well just to keep things confusing, I re-compiled the code, uploaded it, and now I have red LED action. It ends up staying on all the time. Half the time I get this from the console screen: C:\Program Files\Reprap>rem reprap-host -- runs Reprap Java host code with an ap propriate classpath C:\Program Files\Reprap>rem Amount of RAM to allow Java VM to use C:\Program Files\Reprap>seby Adam.m.Nelson - Firmware - mainstream and related support
Well, while I am conceding I may as well post the config file too. I nuked the code for the settings for other boards, it shouldn't effect anything (I tried with it in and with it not in) but since the condition to read the code that was in those areas is never true it shouldn't effect anything. #ifndef CONFIGURATION_H #define CONFIGURATION_H #include "features.h" /* * This is the configurby Adam.m.Nelson - Firmware - mainstream and related support
Right, should have read closer. Already did those mods. Can someone send me their firmware? I had to make some changes to get mine to compile, and I can only assume I did something wrong. I tried it a couple times from a fresh download of the firmware, but always run into the same issue with the order of the included, and have to shuffle them around to get it to compile properly. Mine now loby Adam.m.Nelson - Firmware - mainstream and related support
Thanks rhmorrison, That explains the power issue, but it should be fine to run off of the ATX supply should it not? The whole system seems to be common grounded. Funnily enough I am in London Ontario also, I'll need to see how he made out. I think my issues are purely code related, best I can tell the code isn't running on the chip. I know communications work because they worked before I uplby Adam.m.Nelson - Firmware - mainstream and related support
I've also noticed that the mother board won't run of the USB power, but the extruder board will. Is this normal? Currently I need to run the Motherboard form the ATX power supply to program it.by Adam.m.Nelson - Firmware - mainstream and related support
ok, I can't get this thing to communicate for the life of me. Sometimes after I program it the led will do nothing (after it blinks fast as the data goes through), and other times it will start blinking almost like it use to (once a second). Am I missing something here? I now get this as an output from the host console window: C:\Program Files\Reprap>rem reprap-host -- runs Reprap Java hoby Adam.m.Nelson - Firmware - mainstream and related support
Bob, your my new favourite person, that did the trick. Now I have other issues lol. Do you have the red LED blinking when the program is running? Because mine no longer does it, and I don't seem to be communicating properly with the host osftware. I no longer have control over the robot (which I use to have)by Adam.m.Nelson - Firmware - mainstream and related support
Thanks bob. I'll try that today!by Adam.m.Nelson - Firmware - mainstream and related support
Note: This is the error I get: Binary sketch size: 28490 bytes (of a 63488 byte maximum) avrdude: stk500_getsync(): not in sync: resp=0x00 avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51by Adam.m.Nelson - Firmware - mainstream and related support
Hey! I assume your talking about in the config file, and I have all that. #if BELT_PULLEY_TYPE == MENDEL_8_TOOTH_ORIGINAL #define X_STEPS_PER_MM 4.784 #define Y_STEPS_PER_MM 4.368 #define Z_STEPS_PER_MM 1766.796 From the look of you line numbers the code has changed a lot, but I appreciate the inputby Adam.m.Nelson - Firmware - mainstream and related support
Ok... I am trying to tune my Mendel. We finally got the thing running, and everything works. Just the steps per mm are wrong on all the axis. I calculated the changes using the info on this page Reprap Axis Calibration. For the life of me I can't get it to upload to the board. Windows 7 machine, Arduino 021 environment. I changed the baud rate settings in the device manager com port settingby Adam.m.Nelson - Firmware - mainstream and related support
I'm interestedby Adam.m.Nelson - Controllers
Are your stepper drivers still available?by Adam.m.Nelson - For Sale
You can disregard my post. I had forgotten to connect the SCL and SDA lines and all is fine.by Adam.m.Nelson - Controllers