12864 LCD "N534" is not work in Duet3 Mini5+ ver 3.4.5

airking7

I have connected a BTT 12864 LCD to the Duet3 Mini 5+ and I am configuring the settings for the LCD.

I added the following code to the lcd"main" file of the LCD to display the IP address of the Raspberry Pi connected to it.

text R54 C17 F0 T"IP:"
value N534 W30

However, it displays "IP: 0.0.0.0". Could this be due to incorrect settings on the Raspberry Pi or elsewhere?

(The Ras-Pi is connected via wired LAN, and the wireless functionality is disabled on the Pi.)

Previously, I was able to use a command to display the IP address on the LCD when using the Duet2 Maestro. I assumed I could do the same with the Duet 3 Mini 5+.

dc42

@airking7 the reason is that you are running the Duet in SBC mode and RRF only knows the IP address (if any) of the local network interface. I am looking into whether there is an alternative way to display the IP address of the Pi.

dc42

@airking7 I think the following should work in the forthcoming 3.4.0-beta.4 release of RRF.

In config.g add:

global ipAddress = network.interfaces[0].actualIP

In your menu file use:

text R54 C17 F0 T"IP:"
value N{global.ipAddress} W30

airking7

@dc42
Thank you for suggesting the cause and solution.

However, are the codes and countermeasures that you have taught me functions that are valid only for the beta version? If so, change to the suggested version and try again.

I would like to strongly hope that it will be compatible with the official version in the future.

Because I am currently developing a 3D printer to sell to Japanese companies.
I think it is very functional that the IP address that accesses the DWC can be easily seen on the LCD just by plugging in the wired LAN.

chrishamm

@airking7 I ~~think that already works in v3.4 (and not only in the upcoming 3.5-b4) but test it to be sure.~~ I'd also recommend to add a daemon.g file and to update the IP address every 10 seconds or so:

set global.ipAddress = network.interfaces[0].actualIP

Note that the approach above only works for the Ethernet interface. With some extra logic you could also add support for the second network interface (network.interfaces[1] -> WiFi) if required.