-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes #9
Comments
I’m sure it is a wetware issue. I have yet to see what I would call proper “work instructions” on how to do this in PrusaSlicer. When I write them at work (I am a manufacturing engineer), I like to find a reasonably intelligent person with no prior knowledge and see if they can follow them. In the 3DP world I find that most of the time the givers of advice or instructions assume way too much about the user’s knowledge. All I know is import the bundle, then the below magically appeared. Or maybe had done something before the 2.0 profile came out and I cannot remember the magic button for this.
As a side note, I would be more than happy to be a test dummy for instructions/instruction writing. Is the below what I should be seeing at the start of the process after importing the bundle?
***@***.***
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 6:16 AM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes (Issue #9)
I'm not sure where you're seeing this.
I've just reset my slicer and reimported the config_bundle and it shows correct for me
[image]<https://user-images.githubusercontent.com/2574598/226888059-87a746c0-0f58-4b27-a29b-d10f0a968772.png>
—
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TXSIAFPYXYPP4FUINZICDW5LNNRANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
there's already instructions on how to use PrusaSlicer on their website. no point reinventing the wheel... |
But is my image what I should see?
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 8:43 AM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes (Issue #9)
there's already instructions on how to use PrusaSlicer on their website. no point reinventing the wheel...
https://help.prusa3d.com/article/how-to-import-and-export-custom-profiles-in-prusaslicer_382766
—
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TXSIA6HQJ7RJ5TF27SEH3W5L6YDANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
there were no images in your response so hard to tell |
IT was in my earlier email, here below:
***@***.***
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 9:43 AM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes (Issue #9)
there were no images in your response so hard to tell
—
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TXSIHE2DZU53ODMZCVAJLW5MFYRANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
I’ve done it as an attachment this time, but I snipped the email it was first in so you can see that there may be a problem with images on one of our ends.
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 9:47 AM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes (Issue #9)
still no images
[image]<https://user-images.githubusercontent.com/2574598/226941644-7e9077c4-09ec-4e00-9a3a-12b0efee57d3.png>
—
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TXSIBWMZWMASWVCULUBY3W5MGFFANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
theres still no image attached. best use the github interface to load stuff |
no idea where that has come from. its definitely nothing to do with this release though. |
Thats the same version i'm using here and it works fine for me. |
Thanks for your patience, and sharp eye. 5 presets loaded. Since I have not turned my machines on yet, do I have to worry about "recalibrate your AutoZ and Toolhead Probes" since I never calibrated them? Is the config-override.g in firmware or something? Searching my hard drives generated nothing. |
If you've not turned them on yet and already done the calibrations you'll
be fine.
Just make sure there's no config-override.g in sys. You can safely delete
it and it'll be regenerated
…On Wed, 22 Mar 2023, 18:14 MKHTexas, ***@***.***> wrote:
Thanks for your patience, and sharp eye. 5 presets loaded. Since I have
not turned my machines on yet, do I have to worry about "recalibrate your
AutoZ and Toolhead Probes" since I never calibrated them? Is the
config-override.g in firmware or something? Searching my hard drives
generated nothing.
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATUSBSF7EYFD7W55RQ2XVTW5M6QZANCNFSM6AAAAAAWBUFDQQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Where will that config-override.g be? Is it a file or a line in a file?
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 1:20 PM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer wrong, also shows as v1 with v1 bed sizes (Issue #9)
If you've not turned them on yet and already done the calibrations you'll
be fine.
Just make sure there's no config-override.g in sys. You can safely delete
it and it'll be regenerated
On Wed, 22 Mar 2023, 18:14 MKHTexas, ***@***.***<mailto:***@***.***>> wrote:
Thanks for your patience, and sharp eye. 5 presets loaded. Since I have
not turned my machines on yet, do I have to worry about "recalibrate your
AutoZ and Toolhead Probes" since I never calibrated them? Is the
config-override.g in firmware or something? Searching my hard drives
generated nothing.
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATUSBSF7EYFD7W55RQ2XVTW5M6QZANCNFSM6AAAAAAWBUFDQQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***<mailto:***@***.***>>
—
Reply to this email directly, view it on GitHub<#9 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A6TXSIDCAGR2PBKRH7Z5ML3W5M7FDANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
It would be a file in the sys folder on your SD card (not in the GitHub
repo). If it doesn't exist that's fine
…On Wed, 22 Mar 2023, 18:23 MKHTexas, ***@***.***> wrote:
Where will that config-override.g be? Is it a file or a line in a file?
From: jaysuk ***@***.***>
Sent: Wednesday, March 22, 2023 1:20 PM
To: TeamGloomy/Troodon-V2 ***@***.***>
Cc: martinkh leanoperator.com ***@***.***>; Author ***@***.***>
Subject: Re: [TeamGloomy/Troodon-V2] Description as shown in PrusaSlicer
wrong, also shows as v1 with v1 bed sizes (Issue #9)
If you've not turned them on yet and already done the calibrations you'll
be fine.
Just make sure there's no config-override.g in sys. You can safely delete
it and it'll be regenerated
On Wed, 22 Mar 2023, 18:14 MKHTexas, ***@***.***<mailto:***@***.***>>
wrote:
> Thanks for your patience, and sharp eye. 5 presets loaded. Since I have
> not turned my machines on yet, do I have to worry about "recalibrate
your
> AutoZ and Toolhead Probes" since I never calibrated them? Is the
> config-override.g in firmware or something? Searching my hard drives
> generated nothing.
>
> —
> Reply to this email directly, view it on GitHub
> <
#9 (comment)>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AATUSBSF7EYFD7W55RQ2XVTW5M6QZANCNFSM6AAAAAAWBUFDQQ>
> .
> You are receiving this because you modified the open/close state.Message
> ID: ***@***.***<mailto:***@***.***>>
>
—
Reply to this email directly, view it on GitHub<
#9 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/A6TXSIDCAGR2PBKRH7Z5ML3W5M7FDANCNFSM6AAAAAAWBUFDQQ>.
You are receiving this because you authored the thread.Message ID:
***@***.******@***.***>>
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AATUSBVUMYVXFD4URS7K3VDW5M7QPANCNFSM6AAAAAAWBUFDQQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Config screen shows 4 flavors of v1, and .1mm nozzle.
In the slicer profile itself, it has 310x310x400 vs. 350x350x330
And are the speed limits real/safe limits without shaping/mods?
The text was updated successfully, but these errors were encountered: