Qidi Studio Linux Mint / Ubuntu exits after startup v2.5.1.52 #176
Unanswered
basilverthorn
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Any guidance on how to stop it from exiting once you add the Q2 printer? Qidi studio stays open until I add a printer and its ip. Then it will open and promptly exit. The only way to keep it from exiting is to remove the printer? Oddly it will crash Orca Slicer as well once the printer is added by IP. All my other printers work fine, things only crash when it tries to connect to the moonraker instance on the Qidi Q2. It is on the latest firmware as well. Once the printer is added it produces a core dump, causes the same error on Orca: (If I remove the printer, readd it without connecting, I can slice and then just upload through klipper)
perator(), status = 0, error: curl:Couldn't resolve host name:
Could not resolve host: api.qiditech.com
[Error 6], use default key
22:13:24.287271 [TRACE] 02:43:32:16:41:6D
(qidi-studio:11656): Gtk-CRITICAL **: 22:13:24.901: gtk_window_resize: assertion 'width > 0' failed
(qidi-studio:11656): Gtk-CRITICAL **: 22:13:24.911: gtk_window_resize: assertion 'width > 0' failed
(qidi-studio:11656): Gtk-CRITICAL **: 22:13:24.911: gtk_window_resize: assertion 'width > 0' failed
22:20:32.687461 [TRACE] addDevice[Manager] Device added: 8543
22:20:32.791128 [TRACE] connectDevice[Connect] Connecting to device 8543 (Q2)...
22:20:32.811380 [TRACE] onOpen[WS] Device 8543 connected.
22:20:32.911704 [TRACE] sendSubscribeMessage[Send] Sent subscribe message to 8543
22:20:33.241698 [TRACE] 02:43:32:16:41:6D
22:20:33.241785 [TRACE] addDevicedevice :0x60718e9a0a00exit
22:20:33.823965 [TRACE] cleanupConnection[Manager] Starting cleanup for device 8543
22:20:33.824088 [TRACE] cleanupConnection[Manager] Device 8543 connection cleaned up.
Segmentation fault (core dumped)
Just by digging around the json files. If I add the moonraker port 725 to Q2.json I no longer crash, I can view the status page, but at least I can upload the print and then use the web to control klipper, stop the print etc.. Hope this helps someone till it gets figured out. This works for ORCA to.
~/.config/QIDIStudio/user/default/physical_printer
{
"from": "User",
"host_type": "octoprint",
"name": "Q2",
"preset_name": "Q2",
"preset_names": "Q2",
"print_host": "192.168.1.29:7125",
"printer_technology": "FFF",
"printhost_apikey": "",
"printhost_authorization_type": "key",
"printhost_cafile": "",
"printhost_password": "",
"printhost_port": "",
"printhost_ssl_ignore_revoke": "0",
"printhost_user": "",
"version": "02.05.01.52"
}
There is my Q2.jsoon file, again you cant stop the printer etc.. But at least you can slice etc and upload. Then switch over to the web view to control it.
All reactions