Hi,
firstly very big thanks for this outstanding work! I just switched my ercf v1.1b to HH and must say i am very happy with the proposed features as for now.
I don't know if this is the place to discuss this but i have several thoughts about the spoolman integration and would like to discuss some (and maybe contribute). See my fork of moonraker
In my previous setup i had added pre print checks to the ercf software based on the spoolman.py compoment enhancement.
initialize and keep track of which slot (gate) has which spool_id
activate, clear, get ... slots
check filament usage before printing (added metadata fields to be parsed in metadata.py)
generate swap table according to found filament and requested print
enable printing with only one filament even though i have 9 gates
remap tools automatically to correct gates with swap_table
add persistence (with variables.cfg
The bold features are the one i managed to find in HH and i was wondering if it was planned to add the features I'm currently missing. I'm willing to try and rework my previous fork of moonraker in order to accomodate HH.
For future discussion, i found out about this PR in OrcaSlicer that might help for a very nice user experience. I learned that it is possible to use the "extra" field in order to store custom information, i was hoping to use it to store the gate mapping for the current machine there. For now i was using the location field with something like <hostname>:<slot_nb>.
Thanks again for all this great (and very well documented) work!
Hi, firstly very big thanks for this outstanding work! I just switched my ercf v1.1b to HH and must say i am very happy with the proposed features as for now.
I don't know if this is the place to discuss this but i have several thoughts about the spoolman integration and would like to discuss some (and maybe contribute). See my fork of moonraker
In my previous setup i had added pre print checks to the ercf software based on the spoolman.py compoment enhancement.
The bold features are the one i managed to find in HH and i was wondering if it was planned to add the features I'm currently missing. I'm willing to try and rework my previous fork of moonraker in order to accomodate HH.
For future discussion, i found out about this PR in OrcaSlicer that might help for a very nice user experience. I learned that it is possible to use the "extra" field in order to store custom information, i was hoping to use it to store the gate mapping for the current machine there. For now i was using the
location
field with something like<hostname>:<slot_nb>
.Thanks again for all this great (and very well documented) work!