Very embarrassing, but it appears I had a typo in my IP address and even though I thought I had double-checked, I somehow missed it. Everything is working just fine. Can access DWC from my computer while it's using 5ghz even though the duet is using 2.4ghz.
Feeling pretty stupid lol 
@mintytrebor Thanks for the suggestion. I gave this a go and I was able to get my computer connected to the 2.4ghz band, however, I was still unable to access DWC, so it must be something else causing the issue.
I can't access DWC on any of my devices by typing in the Duet's IP address. I'm using a Google Nest WiFi to provide the WiFi network. I think the issue is that all my devices automatically connect to the 5ghz band while the Duet can only use the 2.4ghz band. On the router I was using previously I was able to access DWC from a device connected to the 5ghz band, but on Google Nest WiFi communication between devices on different bands doesn't seem to be working, or at least I can't get it to work. Band assignment is handled automatically on Google Nest WiFi, and I don't think I'm able to manually switch my computer to the 2.4ghz band.
Hoping someone might be able to help me out.
Is there any documentation on a good process for creating custom .img files for the 12864 Display? I can't seem to find much of anything and I haven't been able to successfully create an .img file the displays correctly. Most of the time not is displayed or I get a solid white rectangle. Any help would be much appreciated.
@phaedrux I forgot about start.g, thanks for reminding me! I will give that a go.
@phaedrux I had that thought, but that can interfere with the print jobs if mesh leveling is done at the beginning of each print. At least in Cura, it outputs the tool command for the first tool used during a job before it inserts the start gcode. This means if the job is supposed to start using T1 and there is a T0 command anywhere in the start gecode then the job will start using T0 rather than T1. Thus, I have been trying to avoid any use of tool commands in the start gcode. This is pretty annoying though, so I might have to look into changing how Cura outputs gcode in the back end instead.
My idex machine has the z probe attached to T0. If T1 is the active tool it tries to home z and probe the bed using T1, which does not have a probe attached. I realize the simple solution is to make sure T0 is active when running G28 or G29, but is there any way to ensure that if this is accidentally done with T1 active it will still probe with T0? If you're not paying attention and trying to home z or run mesh leveling with T1 active it crashes the tool into the bed.
I think I have a bad SD reader on my Mini 5+. The board randomly reports no sd card found in the middle of prints, or and startup. Has been happening with increasing regularity. It's gotten to the point where it won't detect the card 4 out of 5 times on startup and can barely make it a few minutes before if it is able to detect it on startup.
I'm wondering if there is anything else that might be causing this or if I should get the board replaced.
I have already tried using a different sd card, but this resulted in the same problem. I have also tried both SD cards on a different Duet 3 Mini and they work fine there.
This is a firmware feature request for additional functionality for 12864 displays.
I would like to request additional values to be added to the alter/value list. I would like to be able to call all these values with the value function, but some may not be suitable for the alter function. They are listed in order of my personal priority.
Please let me know if anything is unclear. Thanks!
@Phaedrux @droftarts Thanks for the help troubleshooting this with me!
I just got an email from the customer today, and it turns out the patch cable was overstretched and that was what was causing the issue.
@Phaedrux I'm thinking it's on the network end as well, but the IT person there doesn't seem to be able to figure it out either.
They said they tried http, https, and just the naked IP (i.e. xx.xx.xx.xx).
I'm assuming you're talking about connecting directly to the PC via ethernet? Do you know if there is a guide anywhere on how to do that that I could send to the customer?
The SD card is installed correctly. We have custom macros pre-installed and they said they saw those on the printer display.
@Phaedrux That's what I thought.
Just heard back and the network is not MAC filtering.
Their network is showing the printer and they can ping the printer from the command line on their computer, but when trying to access DWC from a browser they get HTTP error 403.
I don't have access to the printer, it is at one of our customer's facilities. The printer was tested during production and successfully connected to the network at our facility via ethernet. I'm an utter novice when it comes to networking, but I know one of our other enterprise clients needed the MAC address possibly for that reason. I will ask this customer if it's possible their network is MAC filtering.
On a side note, do you know if subnet and gateway parameters are saved once entered, or do they need to be in the config.g?
There are several elements to this issue.
First, when starting up and plugged into an ethernet connection, the duet is unable to acquire an IP address via DHC and returns a message that the IP address is 0.0.0.0.
Second, this is a large business network and a subnet and gateway need to be defined. After entering the appropriate M553, M554, and M552 commands the Duet returns that it has connected and is using the specified static IP address. The network also shows a device using that address. However, when entering the Duet's IP address into a browser it returns a 403 error.
I'm pretty stuck at this point and am definitely not a networking expert. Does anyone have any ideas?
Hardware: Duet 2 Ethernet
Firmware version: 2.05.1
DWC: 2.0.7
@dc42 Any chance this can be added to the firmware wishlist?
Text strings that are longer than the width of the 12864 display currently get cut off. I would like to request that functionality be added so that text strings that exceed the width of the display scroll horizontally.
This is particularly relevant for:
Please let me know if I need to add more info.
@Phaedrux Gotcha didn't know that existed. Just checked and I have zero hiccups on the current print I'm running, but there haven't been any issues with the current print thus far. I will make sure to check that next time there is an issue.