Skip to content

Upgraded config for FlyingBear P905H#1195

Open
rumatoest wants to merge 1 commit into
MarlinFirmware:import-2.1.xfrom
rumatoest:import-2.1.x-p905h
Open

Upgraded config for FlyingBear P905H#1195
rumatoest wants to merge 1 commit into
MarlinFirmware:import-2.1.xfrom
rumatoest:import-2.1.x-p905h

Conversation

@rumatoest

Copy link
Copy Markdown
Contributor

Description

Took latest configuration files and ported P905H options there.

Tried to to make printer work faster while preserving decent quality.

Benefits

Print speed could be up to 90mm/s with linear advance enabled.

Related Issues

On higher speeds >= 90mm/s or similar linear advance makes printer periodically stuck - CPU is to slow for this fancy calculations. Turning linear advance K factor to 0 allows to print on 100mm/s and above.

@ellensp

ellensp commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

You cannot drop Marlin 2.1.2.8 configs "CONFIGURATION_H_VERSION 02010208" over import 2.1.x "CONFIGURATION_H_VERSION 02010300" configs

Thats like using imperial parts in a metric system.. it just doesn't fit (it actually undoes all changes since 2.1.2.8 onwards)

@Nuck-TH

Nuck-TH commented Jul 12, 2026

Copy link
Copy Markdown

To contribute configs here, they are needed to be made for and tested on bugfix-2.1.x code. 2.1.2.x is several years old at this point, point releases are sporadic bugfixes, not core upgrades.

@rumatoest

Copy link
Copy Markdown
Contributor Author

You cannot drop Marlin 2.1.2.8 configs "CONFIGURATION_H_VERSION 02010208" over import 2.1.x "CONFIGURATION_H_VERSION 02010300" configs

Thats like using imperial parts in a metric system.. it just doesn't fit (it actually undoes all changes since 2.1.2.8 onwards)

Ok I just wanted to upgrade existing 2.1.2.8 configuration but bugfix PR was not the solution.
Are you saying that configuration template for import 2.1.x is different compared to 2.1.2.8 ?

@rumatoest

Copy link
Copy Markdown
Contributor Author

To contribute configs here, they are needed to be made for and tested on bugfix-2.1.x code. 2.1.2.x is several years old at this point, point releases are sporadic bugfixes, not core upgrades.

I've tried bugfix but PR was automatically closed.
Ok I guess I have to try the latest firmware and redo config again.

@ellensp

ellensp commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

CI error is "Configuration.h:284:11: error: missing binary operator before token "("
#if EITHER(PARKING_EXTRUDER, MAGNETIC_PARKING_EXTRUDER)"

This is because Marco EITHER and BOTH was removed from newer Marlins and replaced with ANY and ALL
Some 3 years ago MarlinFirmware/Marlin#25908

@rumatoest

Copy link
Copy Markdown
Contributor Author

Wait a moment "Marlin 2.1.2.8" released not so long ago.
I understand that 2.1.3.x is different but it is still in beta.
I've tried to update exact 2.1.2.x but my PR was auto closed #1194

The bot says "Please redo this PR starting with the current import-2.1.x branch "

The main question is:
Does it mean that 2.1.3 configurations are backward compatible with 2.1.2.8 ?

@Nuck-TH

Nuck-TH commented Jul 12, 2026

Copy link
Copy Markdown

It doesn't matter when it was released, it is several years old code.
Releaes are nothing more than relatively arbitrary snapshots of (currently) bugfix-2.1.x branch. They generally shouldn't be used, because they only thing they are really good at is becoming outdated fast.

Again, to contribute here you don't run releases, but bugfix-2.1.x. Configurations aren't backward or forward compatible verbatim.

@rumatoest rumatoest force-pushed the import-2.1.x-p905h branch from bf21745 to f43f66e Compare July 12, 2026 15:19
Attemp to make it pring faster with decent quality was successfull.
Print speed could be up to 90mm/s with linear advance enabled.
@rumatoest rumatoest force-pushed the import-2.1.x-p905h branch from f43f66e to 13e25c3 Compare July 12, 2026 15:21
@rumatoest

Copy link
Copy Markdown
Contributor Author

@Nuck-TH @ellensp Thanks for pointing our to my PR issues.
Guess I fixed everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants