Marlin 1.1.9 firmware for BigBox Pro

installed it via PlatformIO, it just works, although i had to disabled Automatic Bed Leveling and rerun a PID for both nozzle and bed.

so far its working great with no issues, Linear Advance works like a charm and the whole reason why i upgraded thanks for the bigbox edit

//Bo

 

Hi I just tried flashing it to my Bigbox Pro (its been a while since I have used it last.) The version number at start up still says "1.10 RC3" I flashed the HEX file through xloader. Just wanted to confirm whether this is normal or not.

 

Yeah the upload must have failed. I compiled and uploaded through the arduino IDE and now shows the correct version number. Tho the logo is garbled.

 

Is there anything like this out there for the hybrid dual titan?

 

Cez, you’re welcome to give my branch a go.
For some time now i has been running my own 1.1.x BugFix branch. Regularly merging the main marlin changes into my fork.

Although I have modified it a little, adding/tweaking the code for my own BigBox customisations eg Dock, XY plane testing, inverting the default behaviour when you change tools (T0/T1) so that the head doesn’t move. (these things can be dis/enabled in “BigBoxCustomisations.h”)

have a look at
https://github.com/autonumous/MarlinFirmware-BigBoxV1.1

my main branches are:

• DHT_BF1.1.x_dev is my dev branch, tracking the current Marlin bugfix-1.1.x branch. I tend to update this every so often
• 1.1.9-BigBox is the Marlin 1.1.9 release (actually tracking the 1.1.x branch). I update this when changes have been made to the marlin 1.1.x branch

Marlin Development on the 1.1.x line has slowed/halted, in favour of the new 2.0.x.
I've recently merged my tweaks with the Marlin 2.0.x branch, DHT_BF2.0.x_dev on my GitHub, but I’ve not tested anything.

I'm also use a slightly tweaked version of tohara’s octopi plugin “BigBox Firmware Flasher” to allow compiling/flashing from the pi. A word of waning, on many occasions i have enabled too many options resulting in a firmware file exceeding the limit, resulting in me bricking my RUMBA. Luckily not totally bricked, simply requires refreshing using a ISCP programmer but just hassle.

I can upload a precompiled firmware if you like, although these are based on my printer and how i’ve been playing/testing with things, so YMMV. ie I’m not responsible for any thing breaking

not sure how long I will stick with Marlin as i recently bought a Duet board and plan to covert to IDEX.

Paul

 

Let me just bring this thread back from the dead.

So this is the top google result for updating e3d bigbox firmware. I got it updated just fine using the HEX and Xloader. However, when I tried to auto level the the probe would go off the build area on the left side. (I have a standard BB pro with the IR sensor.) So I decided I have experience with Arduino's I will just look at the code make a few changes and update.

This also went well, sort of. I found the probe offset was set to -32 in the Y direction and 0 in the X direction, which made sense with what I was experiencing. So I measured the off set of my probe and came up with Y = 0, and x = -66. However now when I try to compile I get an error in the sanity check as follows:

#if ABL_GRID
static_assert(LEFT_PROBE_BED_POSITION < RIGHT_PROBE_BED_POSITION, "LEFT_PROBE_BED_POSITION must be less than RIGHT_PROBE_BED_POSITION.");
static_assert(FRONT_PROBE_BED_POSITION < BACK_PROBE_BED_POSITION, "FRONT_PROBE_BED_POSITION must be less than BACK_PROBE_BED_POSITION.");
static_assert(LEFT_PROBE_BED_POSITION >= MIN_PROBE_X, "LEFT_PROBE_BED_POSITION is outside the probe region.");
static_assert(RIGHT_PROBE_BED_POSITION <= MAX_PROBE_X, "RIGHT_PROBE_BED_POSITION is outside the probe region.");
static_assert(FRONT_PROBE_BED_POSITION >= MIN_PROBE_Y, "FRONT_PROBE_BED_POSITION is outside the probe region.");
static_assert(BACK_PROBE_BED_POSITION <= MAX_PROBE_Y, "BACK_PROBE_BED_POSITION is outside the probe region.");

Outside probe region. Now I have checked all the variables that that relates too and I can't find anything that would make the program think it is outside the region. Is there something simple I am missing?

I also found if I just "//" that line of code it will compile and update, but if I do autobed leveling with those settings, the BB will Home, then it won't do anything.

If I try linear bed leveling, it will auto home, then lower the bed 10mm or so, then move to the first point, then time out because bed is too low and the probe never sees it.

Any help would be great!

And thank you for helping a noob that knows just enough to get into trouble!

 

Might not get a response given this is an old thread, but for anyone else trying this:

I got the same errors as above, but ONLY when changing the bed size. Without changing bed size, it compiles without errors.
I was changing the bed size because I put a tempered glass screen protector on the bed (as per suggestion from https://www.youtube.com /watch?v=gQGibxRfq7w) so the available space on the bed was reduced, and I wanted the bed level probing to not exceed the screen protector.

In the end, I solved this by increasing the Probe Edge value to 30, so that it would probe further away from the bed edge, and with this I was able to keep the original bed size with no compile errors.

I successfully flashed it to the bigbox pro, and all seemed well, apart the following two issues:

1. The LCD screen kept distorting every few seconds.
2. Each time I tried to print, I would get a bed heating failure and it would force me to reset the printer. After reset it would print it fine, so issues. Has happened twice to far one print after another.



Any thoughts on how to fix the above? See attached photos for the errors.

 

Did you ever find a fix for the bootscreen logo?

 

Hi

I'm getting my Bigbox going and trying to improve things after a few years of it being shelved. It's basically a mint Kickstarter model. Can I ask - what are the reasons for upgrading the firmware? Does it improve print quality? It seems like there are a few issues otherwise...