prusa3d / prusa3d/libbgcode

Extending bgcode

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
G-code
Stars
73
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Hi guys, not sure if this is right repository, if not, could you please suggest better place?

Issue
Gcode is filament profile specific. This forces user to go back to slicer anytime they just want to swap to different material (or do plenty of manual adjustments on the printer).

Proposal
One solution how to fix this problem would be to not have filament profile specific gcodes - I guess that could be challenging due to compatibility reasons, but considering you are owner of new bgcode format I think it's opening some doors... 😊

BGcode could actually support storing of all slicer installed filament profiles with placeholders on important places.

This way when user would pick filament,then printer could generate gcode out of universal bgcode by simply using find/replace.

Final thought
Solution is not perfect as obviously it would not work with gcode, but for users who anyway uses just bgcode it would work and actually would be another selling point for using them...

Not sure if there is some better way, maybe there is, just I got annoyed by this problem so started to think what could be done about it. What do you think? Does it make sense?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. First determine whether libbgcode is the appropriate repository, then investigate how bgcode currently represents slicer and filament information. Done means an agreed, compatibility-aware design for storing profiles and applying material-specific values, rather than an implementation based on the current proposal alone.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.