printrbot / printrboardmodernmarlin Goto Github PK

Hi!

I flashed the revF simple metal HB Marlin 2.0.1 firmware twice but it seems like the heated bed is not configured? I dont know how to compile the firmware by myself but is the config set to 0 for the HB Temp Sensor?

Thanks!

Hey Phil, hope this finds you well.

Not really familiar with Github so please excuse me if this should not have been reported as an Issue.

I've attempted a few different firmwares for my Smalls, but none worked -- details below. Can we work something out for the Smalls? Mine has the extended/heated bed and I'd like to add an LCD to it.

Here's what I've tried with no success so far:

Attempt 1 --> RevF-v0.5 PlayV2-HB-Y_DIR_NORMAL_170x220_LCD.hex. This has the same bed size, though reserved X/Y, and apparently everything I want, but FLIP would not load it properly, throwing out a 'out of range' error.

Attempt 2 --> RevF-v.05-Simple MetalHB-150x150-NoLCD_inverting Probe.hex. This did flash properly, the heated bed was recognized, X and Y would home properly, but Z went away from the bed and would not home.

Attempt 3 --> v.04-Simple Metal-RevF-NoLCD_Non Inverting Probe.hex. This did flash properly as well, homed fine in all directions, auto-bed-levelling with G29 was also fine. However, the heated bed was not recognized (expected) and I could not change the bed size with M211.

Looking forward to be of assistance so we can port this newer Marlin to the Smalls out there!

Kind regards,

Antonio

Hello, before I go ahead and mess with my printrbot too much, I was wondering if there was a reason you chose to use the old 3 point option. Is it a memory issue?

Also, is this firmware setup for the M8 z axis (1.25mm per rotation), or the original 1/4-16 ACME screw (1.5875mm per rotation).

I am sorry if this is not the right way to ask questions, it's the best avenue I could find.

Currently, my M211 reports my Min and Max at

echo: Min: X0.00 Y0.00 Z0.00

Max: X125.00 Y203.00 131.00

When the documentation states it should be at
X152.40 Y152.40 Z152.40

The extended bed should bump it up to about X250, as well.

However, sending M211 just reports the value of the soft endstops, and doesn't allow me to set them.

What are my options?

I have 8 simple metals I need to update firmware on after a thermal runaway issue melted down one of my heatbeds. I have a mix of rev F and D boards. I also have a mix of heated and non heated beds, but all have e3d hot ends. Would it be possible to get more compiles than what is currently available for the simple metal? Rev D and Rev F with e3d hot end and one with and without HB?

After flashing the v0.6.5 .hex file on your site, I can no longer get into programming mode with my Rev F5 Printrboard. Installing the jumper and resetting or power cycling does not result in the board being recognized as "programmable". Programming by TINYusbISP also fails for the same reason; the board now refuses to go into programming mode.

Just uploaded RevD-v.04-Simple Metal-RevF-NoLCD_inverting Probe.hex onto my Printrboard Rev D in my simple 1405 markers edition. It was the closest IMHO

The motor directions are all inverted, but this is easy to resolved by flipping the connectors. However the endstop configuration between the Simple metal and the Simple 1405 wood is different.

The x min endstop works fine, however the y and z have issues.
Stage size X and Y max are fine, but z is a little off.

The differences I can see are:
The simple has the endstop on y min instead of y max, also running M119 shows Y_max triggered when the Y endstop isnt pressed. The result doesnt change when the Y end stop is pressed while M119 is run so I have no idea how the pins are routed.

The simple wood 1405 has an pnp style z endstop so it is inverted wrt the simple metal. It lights up when its close to metal and off when not. When the probe is far from metal M119 shows triggered. When close to the metal and lit up M119 shows open.

Z max is listed by M211 as 131 where as I believe Z max should be 112.

Additional request I have added a heated bed with a generic NTC 100K, enabling this would also be most awesome.

So what is my request. Could you please compile a .hex compatible with the printrbot wood 1405? I have tried to do this repeatedly using the platoform IO method and the teensy/arduino method and am closer to an aneurysm than either method working.

I am having a problem compiling and flashing the firmware per your directions in Windows. I installed Marlin-conf using the executable on their Git site, and successfully import one of your configurations into Marlin-conf. I set it to compile using the "at90USB1286-DFU" setting, then click compile.

The first time I do this, the PlatformIO terminal pops up and shows it downloading a bunch of things (the last successful package being "LibraryManager: Installing c1921b4"), until it stops with the error:
Error: Unknown board ID 'at90USB1286'.

Subsequent attempts to compile just give the error:

Processing at90USB1286_DFU (platform: teensy; board: at90USB1286; framework: arduino) Error: Unknown board ID 'at90USB1286' Done.

I've tried this with Marlin-conf versions 2.10.7 and 2.10.5, with the same result. Any tips?

Hi,

is any of these files compatible with a printrbot jr v2 (1402) ?
(mine has a RevD printrboard )
Or should I compile it?

thanks in advance
Yannis

I tried flashing the new .8 revision and noticed heated bed is not enabled in marlin. I love the work that you do. Made my old printrbot awesome.

I have just flashed my Printrbot Play with "RevFv1.0_Printrbot_Play.hex" (the 1.1 only had Heated Bed version) and I want to set the Z Offset to be like 0.1mm higher than it is now. I read the Readme instructions on how to do this, but it says to use the measurement on the LCD Screen to get the offset. I don't have an LCD screen, so is the measurement from M114 good enough?

On another note, is there a way to add an LCD to my printer that does not have one using this custom firmware?

M851 is not working like M212 used to work on original printrbot firmware for my Printrbot metal simple. The Z location is not changing at all when homing with G28 or in octopi.

I flashed the hex-file with E3D hotend and heated bed. Next I used M502 and M500 to restore settings since others that have had issues with M851 not working had forgotten this. I used M500 after setting the new probe Z offset position and the new position is correctly shown with M501. When trying to set offset postion lower than -2 i get this error message in octopi: "Error reported by printer. Your printer's firmware reported an error. Due to that OctoPrint will disconnect. Reported error: ?Z out of range (-2 to 20)". This is probably due to settings in firmware and should be fine if probe setting is working.

Is this a bug in the firmware that or can anyone confirm that they have used M851 successfully to set Z probe offset? Is there a solution?

I've got a Printrbot Simple Metal with extended bed (10"x6") & heater.
I flashed RevFv1.0_Printrbot_Simple_Metal_HB.hex

Connecting to it, I see the dimensions are the default 6"x6" - no surprise.
So I tried to set it with the M211 command, but it reports the default:

M211 X254.0 Y154.0 Z152.0
echo:Soft endstops: On   Min: X0.00 Y-2.00 Z0.00  Max: X152.00 Y152.00 Z152.00

Am I missing something?
[Edit: this seems to be a duplicate of Bug #7 - which is closed, but I'm not sure what I'm supposed to do. The release notes for the current version which closed the bug talk about being able to set "build volume" but I don't see how to do that, or if that's what fixes it]

@Zakattacks I think I as talking to you on reddit about heated bed tuning. I definitely have some ripple when I try to use my heated bed. Thought if maybe we discuss on here it might be helpful to others or add to readme.

I'm currently using the Smalls firmware on my Simple Metal, and neither Cura or Prontrface can detect my heated bed.

When I load up Prontrface, anytime I fire up the heated bed, I just get invalid command errors.

Hi,
I have a printrbot plus v2-1 (with wooden frame and LCD 20x4).
So i want to change the nozzle and i need to set new parameters.
But with Marlin 2.0 the LCD screen make whatever.
It's display characters but all is mixing like an overflow and move all time.
Did you always try your firmware with this hardware ?
So my motherboard is an printrboard revD .

Hi,

Can you possibly remove the POST auto-leveling rapid movement to 0,0,10 as its too fast for my machine, and its not nice having such a movement hard coded in post autoleveling. I cant seem to get the firmware compiled myself, as platformio is giving me hell to try and compile for at90USB1286_DFU.

Thanks.

After updating printrbot simple metal. My heated bed when at temperature consistently turns on and off rapidly I can hear the relay clicking on and off on and very quickly. I did not have this issue prior to updating heated bed worked fine.

Any thoughts?

I've had a few issues while putting this on my Printrbot Play. The one that seems most blocking is that flashing the firmware using the FLIP software requires me to leave the jumper on the board alone. If I try to follow the many instructions that I find online (install the boot jumper to start the machine in firmware flashing mode) it doesn't work. I did manage to get the firmware flashed and successfully run prints (with no jumpering), but it seems strange to me that the instructions that work for others would be irrelevant to my printer. Am I missing something important?

I haven't been able to compile the firmware myself, I'm just using one of the prebuilds for the Play that is available in the repository.

Also, the Play has an SD card slot (with no LCD or control panel of any kind) that seems to be unsupported in the Play build that I see in the repository. The only references to SD cards that I remember seeing documented around here are for SD cards on LCD control panels.

Lastly, although it is noted in the readme that three-point bed leveling works better for small beds (like the 100mm square standard build plate on the Play) there seems to be a 16-point grid enabled in the available Play build. Is that intentional?

I'd love to be able to connect to my printer, point it to a file on the SD card, and then disconnect to let it finish the print. I'd also like to have the 3-point leveling because I found it to make a better first layer, especially near the edges of the build plate. The compiling/flashing issue is less important in the end, other than as a way to work on my own problems.

Any thoughts on any of these points?

Not an issue, just some notes for others.
I recently recompiled the latest Marlin for my Printrbot. Just for the recored over time I've changed the hot end to an E3D V6, extended the bed and added a silicone heat pad from Aliex Express.

Two observations that may be helpful to others.

Heatbed temperature and failures:
The heatbed kept on failing and killing the firmware operation. I played with extending WATCH_TEMP_PERIOD to 120 in Configuration_Adv. This helped, but the issue kept on occurring. I then noticed that MAX_BED_TEMP was set to 150, I changed this to 255, which completely resolved the issue and the bed is heating up as it did with the original firmware.

• The problem here was that the bed was simply taking longer to heat on 150

Extruder Z-height
This may just be my ailing memory, but I seem to remember Z being at the correct height when the PB is homed. This is no longer the case, when I home the bot it is around 1mm from the bed. When I set the Z using M851 the PB only seems to use the new correct value when printing. So you basically set the Z height, and then start a print and see if it is the right height. I actually found an easy way to do this using Octoprint and a plug-in which enables a dry run. I put a piece of paper on the bed, and start the dry run. At around the point where I can move the paper, but still feel that the paper is being slightly gripped, I know I am around the right height.

I'm trying to compile my own hex for a Printrbot Play with the heated bed upgrade and a RepRapDiscount Smart Controller using PlatformIO. I'm really getting nowhere. Could someone compile a hex for me and upload it to the repository? I'd greatly appreciate it.
Cheers!

After flashing, I no longer get the red light turning on to stop the nozzle from crashing into the bed. When I try to home the Z axis, it tries to keep going (I pull the plug before damage occurs). Oh, also, homing Z tries to send the probe LOWER than what manual commands allow me to do.

I am trying to compile the firmware for my Simple Metal HB no LCD with Bilinear Bed Leveling enabled but I am facing some issues. I don't think the issue is correlated with the bed leveling option I selected because I can't compile the unedited files by themselves. I have attached the log messages that I saw for reference. Thanks.

ErrorLog.txt

I have flashed "RevFv1.0_Printrbot_Simple_Metal_HB.hex" for my stock Simple Metal with printrboard F5. After that I ran all G-code found on the referenced page in the instructions for the Simple 1403. I have also added the startup gcode in some slicers.

Unfortunately the coordinates seems to be offset from what is correct resulting in prints close to the edge of the bed when the object is centered in the slicer.

Do I have to compile Marlin again with some special settings or can I use some g code (ie. M206) to fix this issue? Examples would be appreciated.

I am getting a halt on thermal runaway when the cooling fan runs
This occurs either when manually activated or when the printer initiates. Extruder temp drops from 208 to 196.8 on the last fail

Not running a heated bed.

The Marlin 1.1.9 .hex file for the Simple Metal Rev. F doesn't seem to have been compiled with either the SD card or the Reprap LCD enable. The LCD is blank and when I attempt to read from the SD card on the Printrboard it gives me unknown command for M20 and M21.

Hey, okay, I'm going to come clean, I am a total Newb to Github. I have drafted a complete set of instructions to create the firmware for the Printrbot based off the config files here. I am happy to put it up, but I feel like I need to ask the question:

Is this okay with DrPhil, and is this the right place to put it, should it go on the printrbottalk forum or somewhere else.

Apologies again, I've never really used Github

I have a Simple Metal with heated bed and a REVD board. I flashed the firmware and after a G28 then during a G29 the Z moves upwards away from the bed and never tries to probe downwards to detect the metal bed. Z stepper direction is normal otherwise.

I just set this up on my Printrbot Simple Metal (and it appears to work perfectly!) but I think I found a slight issue in the readme. It says

 M815 Z-1.95 ;this is the default value
 M500 ;save

Should that be M851? - https://reprap.org/wiki/G-code#M851:_Set_Z-Probe_Offset

The 1404 model is the wood/metal hybrid. same heated bed, extruder, hotend, and level sensor as the Plus Metal, only real difference is the Printrboard RevD at its heart.

https://github.com/Printrbot/printrboardmodernmarlin/releases/download/2.0.1/Marlin_2.0.1-Printrbot_Simple.Metal_HB_RevF.hex

This version does not seem to have the heated bed enabled.

Thanks for all the work keeping this updated. I just dragged my printrbot out for the first time in a few years and the 1.0 version seems to be working great!

A couple of day ago I tried to flash the "RevFv1.0_Printrbot_Simple_Metal_.hex" to my Simple. But Flip refused to do it. "Jozer503" describes the same behaviour:

I tried to install Modern Marlin on it using the wiki directions with FLIP. I got my printer into DFU mode and the driver installed.

When I tried to run an Erase, Zero Check, Write, Verify cycle, the Erase step "completed successfully", but the zero check failed at 0x00000. When I reboot the board, I get back into the original firmware. If I skip the Zero check, it also "writes successfully", but fails verification, and again, I boot back into my original firmware.

http://www.printrbottalk.com/forum/viewtopic.php?f=22&t=11895

Any idea what went wrong?

Hi!

I'm attempting to upgrade my printrbot simple metal rev F5 to 2.0.1 (mostly to try get rid of a connection issue I've been having for years). I flashed the board with the Marlin_2.0.1-Printrbot_Simple.Metal_HB_RevF.hex file. It seems like flashing process was successful. When I run M115 I get the following:

FIRMWARE_NAME:Marlin 2.0.1 (GitHub) SOURCE_CODE_URL:https://github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:Printrbot Simple Metal EXTRUDER_COUNT:1 UUID:40ce61d1-2ed0-4530-8304-55e3eeaaebff
Cap:SERIAL_XON_XOFF:0
Cap:BINARY_FILE_TRANSFER:0
Cap:EEPROM:1
Cap:VOLUMETRIC:1
Cap:AUTOREPORT_TEMP:1
Cap:PROGRESS:0
Cap:PRINT_JOB:1
Cap:AUTOLEVEL:1
Cap:Z_PROBE:1
Cap:LEVELING_DATA:1
Cap:BUILD_PERCENT:0
Cap:SOFTWARE_POWER:0
Cap:TOGGLE_LIGHTS:0
Cap:CASE_LIGHT_BRIGHTNESS:0
Cap:EMERGENCY_PARSER:0
Cap:PROMPT_SUPPORT:0
Cap:AUTOREPORT_SD_STATUS:0
Cap:THERMAL_PROTECTION:1
Cap:MOTION_MODES:0
Cap:CHAMBER_TEMPERATURE:0
ok N10 P15 B3
N11 M105*23

Which looks good, but when I try to heat the bed, I get the following:
echo:Unknown command: "M140 S95"

I saw that the February 2019 pre-release 0.8 didn't have the heated bed enabled. Could that be what is happening here? How do I enable the heater?

I am trying to change the bed size and before M211 Z250 would work fine. That seems to not work anymore. What am I doing wrong?

BACKGROUND: I recently had the good luck to inherit a PrintrBot Simple Metal (no heated bed, Rev F5 2015). Initially it would connect randomly (like 0.01% of the time in Cura) and then I would be able to jog the motors and set the hotend feedback loop, yet never initiate a usb print job, or start printing auto0.g off of a microSD. This told me that the board is likely OK but there is an issue with the firmware and that it should be reflashed.

PROBLEM: Using ATMEL FLIP I was able to flash the board using several versions of your firmware .hex files (including 'RevF-v.05-Simple Metal-150x150-NoLCD_inverting Probe.hex'). The good news is it now connects via USB Serial COM8 very quickly and 100% of the time in Cura which was never happening before. The bad news is although it connects, I can not jog the motors or set the hotend temperature, or communicate with GCODE commands. On a side note, when flashed with 'RevD-v.04-Simple Metal-RevF-NoLCD_inverting Probe.hex' (likely the wrong firmware) the motors do briefly seem to attempt movement.

Do you have any suggestions as to where the issue might be? I am new to both AVR and 3d printing firmware. So far I was able to make good progress following your instructions but maybe I am missing something. I have not compiled anything from source code and I'm wondering if I did what I might change.

I do have a serial analyzer and pocket oscilloscope available if I need to debug the board itself, but my hope is that the board is OK and this is a software issue.

Thanks for your help or suggestions!

Trying to figure out exactly what approach to take for updating my dual extruder Metal Plus with heated bed. Do I just use the most recent RevF file (RevF-0.6.5_PlayHB_200x100_Inverted_Probe.hex) and then load the previous eprom settings, or what?

Hi All!

I recently downloaded RevFv1.0_Printrbot_Simple_Metal_HB.hex for my Simple Metal with heated bed and board RevF5. Everything is original to the printer (I have made no modifications). I think this is the right firmware to use? I did manage to get the firmware flashed to my printer; however, I am running into a minimum Y issue. I am not a programmer, but what I think is happening, is the minimum Y value is not 0 within this or any other .hex file for the Simple Metal. The minimum Y is -2, thus when trying to setup the auto-level functions, specially when G29 is used, the minimum Y is trying to go beyond zero (-2mm according to the firmware). This causes a very unpleasant noise, as the Y axis is trying to go beyond the print platform. Is the above correct? Or am I doing something wrong? Is there a way to fix this?

Hello, I use octoprint and have been playing with different firmware configurations for the past few weeks. For some reason I can't get the heated bed temperature to be read (and as such no heating is possible). I have tried setting it myself and using the firmware v1.0 provided here.

I have tried measuring the thermistor, and it comes out at 100k ohm as it should.

Any ideas on how to troubleshoot this some more? Is there some way I can use the gcode terminal to probe stuff?

Thanks

Update : I've switch the hot-end and heated bed thermistors just to troubleshoot. The heated bed thermistor works just fine when plugged in the hot-end port. It seems the heated bed thermistor port just isn't picking up any reading. This was confirmed by putting the hot-end thermistor on it, still didn't get a reading.

I always used M212 to set the Z offset to adjust the printer, but M212 no longer works, and M206 doesn't seem to work the same way in that it in no way provides an offset that can go below the trigger point of the probe....

Sorry, wrong place

I am trying to use the firmware updater app as recommended by the guide. Using the compiled firmwares for the Printrbot simple metal from this repository I get the following error "Error parsing the line. Something went wrong with creating the memory image." This happens with both my revF and revD boards, I have tried multiple verisions of the firmwares (HB/E3D) and all give the same error. However selecting the printrbot simple metal and board version in the updater app and letting it download firmware itself flashes ok.

Can't seem to get the LCD to work, but I'm not sure if its a faulty LCD or if I screwed up so... two questions

1- is the 1.0 firmware provided LCD enabled? (I am under the impression it is)
2- what is the pinout mapping you used?

Thank you!

Hello,

I see this has been brought up before, but I am an extreme novice at this. How can I get my settings of 203 x 203 x 130 mm back again? I cant seem to use the old commands as stated in this forum.

What archive version can I use to setup the old way?

Thank you,
Johnny B

Upgraded the firmware on my Simple Metal RevD. Since doing so the logic on the probe is now reversed.
M119 shows Triggered when no metal is detected, Open when metal is detected. This of course means when homing Z, it goes up then stops.
Rolled back to an earlier firmware, issue goes away and able to print normally.

Are you able to compile an updated file with the line change for the z probe?

Thanks.