Skip to content

Move from "Filament Manager" #212

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
WimVDK opened this issue Nov 2, 2021 · 6 comments
Closed

Move from "Filament Manager" #212

WimVDK opened this issue Nov 2, 2021 · 6 comments
Labels
status: closedByBot status: markedForAutoClose Issue will be closed automatically status: waitingForTestFeedback

Comments

@WimVDK
Copy link

WimVDK commented Nov 2, 2021

Just found this plugin which seems to be the successor to your "Filament Manager" that you took over from someone else a while ago. I swapped to that one as my android app i was using to manage spools didn't sync my spools back. I have exported my spools from there but i'm having problems with this plugin.

I found out where to add spools, but in order to add spools i need to add a vendor. The problem is i can't find out wher to add a vendor nor can i find out where/how to import my "Filament Manager" profiles & spools.

I'm getting a bit overwhelmed atm as i'm seeing "Printer Display" in the bottom left, a warning about "filament tracking is possible in the top right" and something about layer height etc not being detected. From what i get so far the "Printer display" is the same as what i'm seeing under "printer notifications". I don't need a M117 notification about the % or layer as i can see the % in the progress bar of my CR-10 Max.

Nor is the documentation any help atm,

i'd be very grateful of any and all assistance.
@OllisGit OllisGit added status: waitingForFeedback Wating for Customers feedback type: question Further information is requested labels Nov 3, 2021
@OllisGit
Copy link
Owner

OllisGit commented Nov 3, 2021

Hi @WimVDK,
well documentation is always helpful ;-) ...Unfortunately it also took a lot of effort to create.
It is on my list (a starting point is a FAQ in the Wiki)..or feel free to provide a documentation which I could include here ;-)

But you are mixing multiple plugins . Each plugin has multiple responsibilities and some plugins interact with each other. But it is also possible to use each plugin individualy.

E.g. you are using DisplayLayerProgress which include theses features:

  • "Printer-Display" in lower corner. Every M117 which was sent by OP is displayed also in the Web-Browser. Can be deactivated via Plugin-Settings
    image
  • Extract Layer-Informations from the GCode during the upload of the file. If the gcode doesn't include special layer-comments the plugin could not extract this information and shows a warning (could also be disabled)

PrintJobHistory-Plugin

  • This plugin captures each printjob-data and stores the result in a database. Beside the "out-of-the-box" information like start/end-time it captures also the layer-informations provided by the DLP-Plugin (if installed)
  • And it could also capture the filament usage. But to do this, it needs a plugin that could capture the filament. The popup is a hint to select a tracking plugin
    image
    image

Switching from FilamentManager to SpoolManager

  • The easiest way is to install both plugins and to export the FM-Data via the SpoolManager-Plugin. This way all data is exported in a format that could be easily manipulated via Excel (or Texteditor) and reimported into SpoolManager
    image

In the SpoolEdit-Dialog enter your spool vendor name into the field, hit enter and press save. After that, you can reuse the vendor name in the next spool.

Profiles like in FM is not supported in SpoolManager.

I hope I answered all of your questions...if so, please close the issue.

@WimVDK
Copy link
Author

WimVDK commented Nov 4, 2021

One thing at a time, lets start by getting SpoolManager to work. I thought i might be mixing things but they 3 of those got installed cause SM recommended PJH and PJH recommended DLP in one way or another. I thought i had to export the csv from FM THROUGH FM, apparently not. So i managed export its db though SM, didn't see the sample csv so just straight up loaded it in SM but the "upload & import" is spinning. Could it be because there's a print going on?

@WimVDK WimVDK mentioned this issue Nov 15, 2021
Closed
@OllisGit
Copy link
Owner

OllisGit commented Jan 7, 2022

fyi: In the next release the import function is only available if the printer is not busy.

@OllisGit OllisGit added status: inNextRelease Will be implemented/fixed in next release and removed type: question Further information is requested status: waitingForFeedback Wating for Customers feedback labels Jan 7, 2022
OllisGit added a commit that referenced this issue Jan 12, 2022
@OllisGit
New Version 1.6.0
02e6231 
- E release-channles
- E stale-bot via github-actions
- E #79, #87, #99, #119, #157, #176, #202, weight calculation during editing PR #206, thx al lot @TiziG
- E #106 switching from travis to github-actions
- E #107, #215 database-settings in the log will only be shown, if sql-logging is enabled
- E #170 inform user about switching a spool already selected
- E #213 sort/filter options in spool selection dialog
- E Extrusion-Debugging: Show current extrusion during printing

- B #188 touchUI conflict
- B #193, #196 sorting/showing of remaining weight
- B #205 changed to "browser-native" date/time picker
- B #210 loadCatalogColors when color name is blank
- B #211 button text changed
- B #212 import CSV only if printer in idle-mode
- B #216 FilamentManager and SpoolManager used same viewmodel
- B #217 when print is paused the extruded filament is assigned to the spool and the counter is reseted
@OllisGit
Copy link
Owner

Hi,
in the latest version the issue should be fixed.
Please test and give a feedback.

Thx in advance
Olli

@OllisGit OllisGit added status: waitingForTestFeedback and removed status: inNextRelease Will be implemented/fixed in next release labels Jan 12, 2022
@github-actions
Copy link

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

@github-actions github-actions bot added the status: markedForAutoClose Issue will be closed automatically label Feb 12, 2022
@github-actions
Copy link

This issue was closed, because it has been already marked for 10 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: closedByBot status: markedForAutoClose Issue will be closed automatically status: waitingForTestFeedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@WimVDK @OllisGit