Closed pmbroth closed 4 months ago
I attempted to reproduce the issue by clicking under various conditions, such as without a network card or connecting via Ethernet, but I was unable to replicate the situation where it wouldn't navigate.
If the information obtained from the ifconfig
command includes wlan0 (indicating the presence of a wireless network card) and eth0, try adding the Wi-Fi configuration directly to /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
and restart the system. Then, check if it takes effect through the router management interface.
Here is what I have after I run ifconfig:
To avoid disclosing your information publicly, I have hidden this comment for your protection.
Thank you! The file is completely blank. Can you send me the file? pmbroth.ny@gmail.com wpa_supplicant-wlan0.conf.txt
It shall look like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
ssid="XXXXXXX"
psk="XXXXXXX"
}
replace ssid
and psk
with wifi name and password
will do.. Thank you
I made the changes, network button still does not work. Interestingly, if I press the load screen and then, the network button, the extruder temp section shows part of the network ip see pic, and ip is strange should be 192.168...
Have you upgraded the UI using the file provided in the 7z archive
I do not see a step for that. I did Motherboard, x_4.bin, extruder upgrade and Emmc image flash. I do not see a step for UI. What do I do?
This is what I did, but do not see anywhere to process QD_Max3_UI5.0
You can place the UI file in the QD_Update
folder at the root directory of a USB drive and then update through the screen detection.
Alternatively, you can rename the file to 800_480.tft
and place it in the /root
directory of the system, then restart the printer.
Thank you. Will do this when I get home Can I use the external usb drive on the printer?
Please excuse any typos, this email is being sent from my phone
On Wed, Jun 26, 2024 at 9:21 AM CChen616 @.***> wrote:
You can place the UI file in the QD_Update folder at the root directory of a USB drive and then update through the screen detection.
Alternatively, you can rename the file to 800_480.tft and place it in the /root directory of the system, then restart the printer.
— Reply to this email directly, view it on GitHub https://github.com/CChen616/QIDI_Max3_Bookworm/issues/8#issuecomment-2191685713, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF25YXOWQHCKEMWE6VDH643ZJK56BAVCNFSM6AAAAABJ4GAZVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJRGY4DKNZRGM . You are receiving this because you authored the thread.Message ID: @.***>
Yes, just like a normal version update.
It never came back to ask to reboot. After 30 minutes, I shut down, and rebooted it is now going through the USART update. Will let you know how it goes, Thank you..
I have updated the instructions, Question should I have the system recover time-lapse? It works fine, just has the corrupt error. Thank you again, and will let you know how it goes once the upgrade is completed. upgrade instructions v3.pdf
It works.. Thank you!!!
I also upgraded to Orcaslicer 2.1.1 and I do not need the M117 command, the layers are displayed correctly, and fans work perfectly. Thank you again.. Should I run the recover on time-lapse, or leave it alone since it works?
I also upgraded to Orcaslicer 2.1.1 and I do not need the M117 command, the layers are displayed correctly, and fans work perfectly. Thank you again.. Should I run the recover on time-lapse, or leave it alone since it works?
I wanted to follow up on the network issue. Thanks to the work of someone who opened an issue on my repository, i have the wifi working on my screen. this is what I came up with as a way to get it working, and it may work for your image as well.
sudo mv /etc/resolv.conf /etc/resolv.conf.bak ; sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf ; sudo printf 'ctrl_interface=/var/run/wpa_supplicant\nctrl_interface_group=0\nupdate_config=1\n\nnetwork={\n ssid="network"\n psk="password"\n mesh_fwding=1\n}\n' > /tmp/wpa ; sudo mv /tmp/wpa /etc/wpa_supplicant/wpa_supplicant-wlan0.conf ; sudo chown root:root /etc/wpa_supplicant/wpa_supplicant-wlan0.conf ; sudo sed -Ei 's/^After.*$/Before=dhcpcd@wlan0.service\nAfter=dbus.service/;s/^ExecStart=.*$/ExecStart=\/sbin\/wpa_supplicant -c\/etc\/wpa_supplicant\/wpa_supplicant-wlan0.conf -Dnl80211,wext -iwlan0 -u/;s/^Alias=.*$/WantedBy=network.target/' /lib/systemd/system/makerbase-wlan0.service ; sudo apt install dhcpcd -y ; sudo systemctl disable dhcpcd.service ; sudo systemctl enable dhcpcd@wlan0.service ; sudo systemctl disable wpa_supplicant.service ; sudo systemctl enable makerbase-wlan0.service ; sudo reboot
For my setup, I am using the rtl8xxxu
driver. A script located at /root/scripts/rename_interfaces.sh
generates the rules file to rename the network interfaces. After that, I install and enable dhcpcd
, but I continue to use the original makerbase-wlan0.service
service file. With this configuration, the network works correctly.
The display control system uses wpa_cli
to send commands such as SCAN
and SCAN_RESULTS
to search for and display available Wi-Fi networks. The makerbase-wlan0.service
is used to automatically connect to Wi-Fi on startup.
For my setup, I am using the
rtl8xxxu
driver. A script located at/root/scripts/rename_interfaces.sh
generates the rules file to rename the network interfaces. After that, I install and enabledhcpcd
, but I continue to use the originalmakerbase-wlan0.service
service file. With this configuration, the network works correctly.The display control system uses
wpa_cli
to send commands such asSCAN
andSCAN_RESULTS
to search for and display available Wi-Fi networks. Themakerbase-wlan0.service
is used to automatically connect to Wi-Fi on startup.
The screen wifi settings didn't work for me in your image, and they didn't work in my image until today. Which is why I commented. I did also update my comment with a better way to fix the issue. And I believe the commands I posted do the same thing you describe, they use the dhcpcd service, and they use the makerbase-wlan0.service. But those are not functioning properly in either of our images
Using CCHEN image, wifi works for me. I wonder if my machine was manufactured with newer parts, as when I received it, it came with all the upgraded parts installed.
All is working perfectly, and since I use ethernet cable, I did not try the network button till today. When you press the network button nothing happens it stays on the screen that you were on previously. My concern, is if my network ip changes, it will be alot of effort to determine the ip adress for the printer, and I will not be able to connect using wifi