So I got my printer working awhile back, but seem to have a couple of bugs to fix before it will be fully operational. Even though I have set in my firmware to have a bed area of 250x152x152, It wont go past 152 on the x axis. In the firmware it shows a line: #elif defined(PB_SIMPLE), and then gives the x, y, and z axis dimension, so I changed the default to 250x 152y and 152z, saved and complied, loaded the new firmware though Atmel, and still get it stuck at 152 on the x. While I was loading the new firmware I noticed something rather odd. I would put the jumper on the boot pins, power cycle, and hit the reset button until I heard the distinct sound windows makes when I sees something plugged in. But when I went to device manager, it doesn’t show up as a “other device”, only as a lusb… device. I’m not sure if the firmware is being properly loaded or if I’m making a mistake in the firmware somewhere. Any ideas? I can link the firmware if someone would like to take a look at it.
What printer? I have thousands in the wild w/o this problem. Difference may be you are using a self-compiled firmware, but maybe not. Have you tried our factory-provided firmware. A simple mcode resizes the print volume. There are some files we modified that a self-compiled version would not include teensy stuff).
Brook
@Brook_Drumm Its a Simple Metal, I havent tried the stock firmware, Ill try that.
@1111137 spam reported.
@Brook_Drumm ok, so I loaded old firmware which was provided to me by Astica on Thingiverse. And it does work , I get the full 250x 152y and 152z. But this only half solves my problem, I still need to be able to compile my own firmware so I can set my own PID tune, and add more probing points to my bed. At least we have found out that it is in fact a firmware issue, and not a “wont flash” issue. The Marlin I have been editing is the one found at: https://github.com/Printrbot/Marlin, which is made to work with the Printrboard, so I’m unsure of y my compiles aren’t working.
https://github.com/Printrbot/Marlin
THE issue w multipoint probing and a whole bunch of other stuff available in main line marlin is featureblot and the ultimate size of the firmware. The chip in the Printrboard has less memory available than a typical ramps setup. So we hacked out stuff we didn’t need to get the features in that I wanted. It’s all personal decisions I have made based on need. Good luck!
Brook
@Brook_Drumm ok, so if the hex file is too big, it wont show an error in Atmel? I was under the impression that something would have warned me about that. Thanks then, guess Ill just stick to what I have.
so even with all of the things I want enabled, I get to ~80Kb, well under the 128Kb that the Rev F6 board can take, not really sure why its not working…
Isn’t the bed size stored in eeprom?
@Testof_Newtablet what do you mean?
@Testof_Newtablet oh I see, yes it is. But it is still set by the firmware, when it is loaded. And that is what I am having trouble with.
What are you use no to compile? The http://printrbottalk.com community has s lot of helpful info- you might check them out
For the eprom to take new firmware settings, you have to bump a version number in the configuration file you are editing. (I think)
@Andrew_Blinkmann only when you change eeprom values in the http://ConfigurationStore.cpp, I have only touched the Configuration.h
Ok so I have figured out that the firmware is getting loaded. I gives me 9 probing points, and the PID has works well. But I still get a bed size of 152xyz. Even though I have changed the bed size to 250x 152yz
Hitting a hardware endstop by chance?
@Andrew_Blinkmann nope, my previous firmware I used (5min ago) allowed my to use my full bed
Thats for all the help everyone. Figured out that you can send the M211 comman to change the bed size, then M500 to save to eeprom
@Jocelyn_Susie spam reported