-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
CURA 5.8 will not see my wifi Ultimaker3 #20075
Labels
Status: Triage
This ticket requires input from someone of the Cura team
Type: Bug
The code does not produce the intended behavior.
Comments
daparcher
added
Status: Triage
This ticket requires input from someone of the Cura team
Type: Bug
The code does not produce the intended behavior.
labels
Dec 28, 2024
You can add a second, new printer profile as a dummy in order to remove the Ultimaker profile. Include your log file or the zip file generated, so we and/or developers can see what your Cura is reporting in the background. |
Hi Anna .. thanks for the reply. I refreshed the printer name via I.P.
address on the printer and am successfully connected to my wi-fi. I still
have the issue, however, that after slicing I only get the Print To Disk
button., My printer's name is displayed on the Cora home interface but I
go to Manage Printers, hit Refresh or Add buttons -- it asks for an I.P.
address. When I enter my printer's IP, nothing happens.
I
I've endered the printer's I.P. address intp my.browzer, the Ultimate pages
comes up but throws an error when I click on "Digital Factory" (see
attached). In fact all the links on that page throw the same error.
I've rebooted the Macbook and the Printer ... (not the router though).
Yikes ...
[image: Screenshot 2025-01-07 at 11.52.29 AM.png]
[image: Screenshot 2025-01-07 at 11.51.46 AM.png]
…On Mon, Jan 6, 2025 at 8:51 PM Anna ***@***.***> wrote:
You can add a second, new printer profile as a dummy in order to remove
the Ultimaker profile.
Include your log file or the zip file generated, so we and/or developers
can see what your Cura is reporting in the background.
—
Reply to this email directly, view it on GitHub
<#20075 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOBELBFYMWSU5L6AEQD7LV32JMXLRAVCNFSM6AAAAABUKA6NRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGIZTSNJUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Best,
Doug Parcher
|
UPDATE ..... I changed the wi-fi instance and am now able to access the
"Digital Factory" just fine .. I can see my printers, camera, logs, etc.
but CURA 5.9 will still only allow "Print To Disk" after slicing.
What can we do next?
Best,
…On Mon, Jan 6, 2025 at 8:51 PM Anna ***@***.***> wrote:
You can add a second, new printer profile as a dummy in order to remove
the Ultimaker profile.
Include your log file or the zip file generated, so we and/or developers
can see what your Cura is reporting in the background.
—
Reply to this email directly, view it on GitHub
<#20075 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOBELBFYMWSU5L6AEQD7LV32JMXLRAVCNFSM6AAAAABUKA6NRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGIZTSNJUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Best,
Doug Parcher
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Status: Triage
This ticket requires input from someone of the Cura team
Type: Bug
The code does not produce the intended behavior.
Cura Version
5.8
Operating System
MacOS Sequoia
Printer
Ultimaker 3
Reproduction steps
Reconfigured my Ultimker e Printer to a wife using a new printer name but CURA does not list that new nema. I see the original name, but it will not allow remova or renaming and when I slice I only see "Save to Disc" and not "Print over Network.
Actual results
I can connect to the printer's camera through the I.P. Address in Digital Factory however.
Expected results
I want to click the "Print over Network" button to initiate printing.
Add your .zip and screenshots here ⬇️
The text was updated successfully, but these errors were encountered: