v1engineeringinc/marlinbuilder

MarlinBuilder

marlinbuilder's Issues

first build problems, cant get any of the motors to run control board has red leds on at each driver also one at USB port apparently have something hooked up wrong

Front Page to MarlinBuilds

We've talked about this before, but it would be nice to have a githubio page or a page in the docs that points to the right zip files.

Fix or remove Archim builder

For years the ci build status of this project has been failed, solely because of the Archim board/architecture it seems. I would suggest to allow it to fail and not set the overall build status of the project to failed. Otherwise it seems this project will never have a proper ci build (at first glance that was my impression at least).

V1CNC_Ramps_Dual-2.0.7.2-src is zipped twice

The V1CNC_Ramps_Dual-2.0.7.2-src zip folder has a separate zip folder inside of it (downloaded from https://github.com/V1EngineeringInc/MarlinBuilder/releases). It would be nice if you only needed to unzip once.

I need help

I Am looking to build a lowrider 3 cnc and i need firmware for a skr 1.4 non turbo board i would apreciate help seeing as i cant code to save my life

Update for Marlin 2.0.9.4

I'd like to use some features in Marlin that were implemented earlier this year and are part of 2.0.9.4 (released in june): https://github.com/MarlinFirmware/Marlin/releases/tag/2.0.9.4

Related:

• https://forum.v1engineering.com/t/marlin-versus-work-coordinates-g10-l20/10959/15
• cncjs/cncjs#549 (comment)

Can we expect an update for the MPCNC firmware?

tft35 e3 v3.0.1 no printer attatched

ive installed marlin 2.1.1 for skr 1.4 turbo LR Duel and also the updated tft cnc however im now getting no printer attatched ;/

Marking the releases as `...-src.zip` is confusing to people who are looking for `.bin` files

I think it would be nice to drop the .src from the release filenames, or clearly state in the release notes that the src.zip files include both the Marlin source and precompiled .bin files.

For example, the MPCNC Primo with SKR Pro board using Dual Endstops release file would be:
V1CNC_SkrPro_Dual_2209-2.0.7.2.zip

and include

• firmware.bin
• V1CNC_SkrPro_Dual_2209-2.0.7.2-src.zip

z axis sensorless not working (alway home)

hi, i try to enable sensorless homing for skr 1.3 dualLR 2209 firmware, joging is ok, all axis moving right direction, sensorless homing work on x and y but only z axis homing not work(alway home). any fix for this?

Ramps non-dual endstop version

Looks like we do not have one.

Adding it to the list, soon.

Updates for next release

Some things I've seen in the forums that I'd like to investigate:

• Bump version to 2.0.9.x
• 2.0.8.2 has added a 3rd serial port for the skr boards. This should allow wifi dongles as well as the usb and tft. Needs some testing.
• Robert suggests we add emergency parsing. I'm not sure the consequences yet, but I think it is worth it for the users that need it.

LCD Timout not working?

Using the main branch, The LCD never returns to the main menu.

I have it set to 3 minutes, in the current main branch. Config_adv line 1095-6. At least on the mp3dp mini rambo version. I can try more boards a bit later this afternoon.

SKR Pro motion causes heat 2 to trigger.

https://forum.v1engineering.com/t/spindle-on-off-in-menu/26862

Archim 1 microstepping not being set properly.

The discussion, https://forum.v1engineering.com/t/steppers-moving-at-different-rates/21925

The current fix,

M350 S16
M351 S3 X1 Y1 Z1 E1 B1
M500

Bed Size?

Should we make the bed size larger in X, Y for the MPCNC builds? It seems like once a week we get someone asking about the 200mm number.

Clarify if `dual` refers to endstop or stepper motor drivers

It is a little unclear to me whether the dual badged firmwares are for "dual endstop" support or "dual stepper motor driver" support. This might be nice to have in the README.md, or perhaps as boilerplate for release descriptions.

EXTRUDERS = 0

your cnc-config file has "echo "- EXTRUDERS = 0" >> README.md" at the bottom, but it doesnt actually set extruders to 0 like it does in the zenxy-config
not sure if you want to remove the tidbit, or set the extruders to 0

Enable Laser without Safety timeout for Laser Focusing

Currently I have a Endurance Laser with power from Fan port and PWM coming from Pin45. With the latest V515 firmware there is no way I can Power on the laser to allow focus for more then 1 second. I Can update LASER_SAFETY_TIMEOUT_MS in the firmware to use a longer time, but i would prefer to keep the safety untouched and have a gcode command / macro that could temporarily disable the timeout.

Previous Controls for laser focus -v513
M106 S255 ; Power on laser
M3 S30 ; fire laser with low power to focus
focus the laser manually
M5 ; Stop laser
M107 ; Power down the laser

Current version -v515
M106 S255 ; Power on laser
M3 I S0 ; without this after the first laser fire it will not fire again
M3 S30 ; fire laser with low power to focus
focus the laser manually while resending M3 S30 multiple times
M05 ; Stop laser
M107 ; Power down the laser

"Adding" other control boards idea

There are some PR's for other boards. Since the builder is so easy I want to just include them. The problem is when something goes wrong, it can be a lot to figure out. If I can't figure it out, what happens if I want to drop "support" for a non-standard board? On top of this the more builds we have the harder longer it takes to run tests of new features or builds.

I propose we only include a few key boards, this will give us the base for any others. So someone could just grab the similar build, change the board name in the file and compile it themselves. For example the ramps config handles a lot of 8bit boards. Or the SKR Pro handles 32bit boards and most of those have TMC's. Instead of trying to handle the SKR Pro and any combination of drivers we just support the recommended one. If you choose to buy tmc2255 drivers or an SKR2 you will need to do some extremely minor editing.

Perhaps we keep a list of edits in certain boards require, both com ports, or different fan port numbers. Put that here in the docs so someone can add, remove, or edit it easily.

Better feedback from the scripts.

We need to add confirmation that the scripts are finding what we need them to change.

Things like Marlin changing the name of a parameter would be obvious then, because it wouldn't find the old name in the file.

Some params, like the screen timing params, aren't in the files, and we add them. In that case, at a minimum, we need a way to accept missing params, and still allow appending.

Please, no one add perl. I think we can do this in bash, but if not, then I'd much prefer python.

more configs

We need to make some more configs:

• 3DP Rambo?
• CNC Ramps?

when screen was working indicated no uart communication I did install the jumpers as instructed What have I missed?

Rambo board cnc dual is setup for dual z instead of dual x

I downloaded the Rambo dual cnc firmware on 3/31 and it compiled and loaded fine but I found that it was setup for dual y and z drivers. I changed it to dual x and y and the motion is fine now. Just wanted to let you know. Keep up the great work. Thanks.

510 mp3d ramps not compiling for some reason

get a filename too long error

Mini Rambo Fan 2

507- mini rambo cnc build has fan 2 always on. Not seeing why

Formatting

First a little change that needs to be made.

From Disable
EVENT_GCODE_SD_STOP
is now
EVENT_GCODE_SD_ABORT

I think most of the settings in the CNC config are actually universal, that previous command, eeprom, arcs, ect. Should they stay separate or should I start moving them to v1 base config?

Rambo, Ramps arduino/bugfix builds are broken

I have been ignoring them for a while, hoping that bugfix will get fixed at some point. But that doesn't seem to be happening.

I'm not sure the root cause, this is the error I see:

2021-04-28T12:26:58.5211094Z In file included from /github/workspace/Marlin/Marlin/src/lcd/dogm/marlinui_DOGM.h:31:0,
2021-04-28T12:26:58.5211955Z                  from /github/workspace/Marlin/Marlin/src/lcd/marlinui.cpp:126:
2021-04-28T12:26:58.5213719Z /github/workspace/Marlin/Marlin/src/lcd/dogm/HAL_LCD_class_defines.h: In member function 'void U8GLIB_64128N_2X_HAL::init(pin_t, pin_t, pin_t, pin_t, pin_t)':
2021-04-28T12:26:58.5215121Z /github/workspace/Marlin/Marlin/src/lcd/dogm/HAL_LCD_class_defines.h:37:13: error: 'init' is not a member of 'U8GLIB'
2021-04-28T12:26:58.5216465Z      U8GLIB::init(&u8g_dev_st7565_64128n_HAL_2x_sw_spi, (uint8_t)sck, (uint8_t)mosi, (uint8_t)cs, (uint8_t)a0, (uint8_t)reset);

That looks like it isn't getting U8glib, or it is getting the wrong version. I see this at the top though:

2021-04-28T12:23:42.3525944Z Install required libraries
2021-04-28T12:23:42.3526495Z Install libraries U8glib

...

2021-04-28T12:26:23.7210869Z Alternatives for U8glib.h: [U8glib [email protected]]
2021-04-28T12:26:23.7211484Z ResolveLibrary(U8glib.h)
2021-04-28T12:26:23.7225877Z   -> candidates: [U8glib [email protected]]

The ways forward:

• Ignore this, as it is in bugfix
• Open an issue in main Marlin. The responses I've heard before to issues like this start with "use platformio", but not from Scott. They might want to know.
• Disable the arduino builds for these boards, at least on bugfix. This would be an even stronger way to ignore the errors :)
• Look into it, and try to update whatever U8glib dependency we need. Maybe the issue is that they changed it, or froze it, and we are specifying the wrong one? We specify it here: https://github.com/V1EngineeringInc/MarlinBuilder/blob/main/.github/workflows/rambo.yml#L98

Check that all the readmes make sense

We just need to go through each config file and make sure the readmes are correct and complete. I added this step a bit late, and I am sure I am missing some.

Config for SKR 1.4 Turbo

Hi,
I would like to use an SKR 1.4 Turbo board for this project.
I may be able to do it myself but I think the only change from a pro to 1.4 turbo is the chip name.
LP1769 instead of LPC1763

Print bed is not correct

Hey, I downloaded the latest firmware to my printer with the MK8 extruder. However, the dimensions entered are not correct, because each time it is pressed, it moves to the right and walks forward. The same game at the MBL. Is there a solution ? In addition, he does not print the test cube in 20mm but in 25mm. greetings

Need to define a laser pin for all the boards.

Best to also add a link to the amazon IOT relay in the instructions somewhere. The one that can run off the fan pin...and some instructions, so maybe a separate page in the docs? https://amzn.to/35CFbDP

Need to try and sort out the laser issues.

• 1-Does M3 work as expected now, no under or over burning? If not M106 -----Yes, works great
• 2-Define a 5V pin to use with the lasers, preferably next to a ground. ....on most of the boards....Mini, Rambo, SKR. SKR and rambo is good, mini is next.
• 3-Update either the laser page or the board pages with instructions (probably both).

Possible to zip up the build before running it?

Can these two lines be swapped so we can add the file to the zip or some sort of output before it errors out?

MarlinBuilder/.github/workflows/skrpro.yml

Lines 81 to 87 in 9f36ca0

	- name: Build
	run: |
	src/core/build-for-machine
	- name: Zip up Marlin
	run: |
	src/core/zip-marlin

If that doesn't work can we build the configured marlin and zip it , then configure up another one then build it?

I would really love a way to run the configuration to try and debug the errors. The way it is now I have to manually go in and add and edit all the different changes then try to fix it.

split screen stuck with marlin code on one side big tree touch screen on other cant go to either one nor reset

skr 1.3 tmc has wrong steps/mm

https://forum.v1engineering.com/t/wrong-double-measurements/25291/4?u=jeffeb3

Something probably got confused since the skr 1.3 firmware was originally for 8825s

Document in README.md how to flash firmware

This should probably just be a link to the relevant docu on v1engineering.com.

However, when going to https://docs.v1engineering.com/electronics/marlin-firmware/ I don't see information for flashing the .bin on my chosen platform (Archim 1.0a). I try to keep Platform.io off my computer, in the past it hasn't played nicely with mission critical stuff from Paticle.io. Hopefully there is an easy and lightweight way to flash the binary, rather than install all of VS Code and Platform.io.

P.S. FWIW, in my experience flashing the compiled binary tends to reduce maintenance and support burden, since the project devs can be certain that everyone is on the same page. In particular, it eliminates the case of hardware failure linked to divergent build settings.

UPDATE

I have figured out how to upload a precompiled binary with a CLI tool. See #73 (comment).

New release for marlin 2.1.2.2?

A new official marlin was finally released again: https://github.com/MarlinFirmware/Marlin/releases/tag/2.1.2.2

Would be nice to use this for a new official mpcnc release/build.

unicornmakebotgithub

V1CNC_SkrTurbo_8825-2-3 Binary File via SD

I've been compiling and flashing firmware on my SKR 1.4 Turbo for a couple days and just now when I tried to put the precompiled "V1CNC_SkrTurbo_8825-2-3" binary file on the SD and flash it I'm only getting M105 over and over in the terminal. I don't know if this necessarily a problem with the file because I've had this happen before when trying to upload a binary via SD card on SKR 1.4 Turbo so it could be either something I'm doing wrong or something about the boards but everything else I've flashed that way has worked. I have also noticed that both of the SKR 1.4 Turbo's that I've had could never be recognized by my computer when connected by USB, or even once they could I could still never get PlatformIO to flash via USB so it could have something to do with that also.

It definitely tried to flash though, because I tried it a second time to make sure the bin file was on the SD and both times the FIRMWARE.BIN was gone and replaced by a new FIRMWARE.CUR, only it's partially bricking the board for some reason.