sounds like you might have dhcp client still
running, does the IP for the PC change
when it stops working or does it say static?
No. But thanks for the reply.
Is the netbook connected by WiFi to your network as well?
No. WiFi is disabled.
I have further information. When the NoteBook connects to the DUET-E controller & the Web-Console, EtherNet/Controller stays connected so long as there is not a lot of I/O hand-shaking. For instance, I can issue motion commands via the web-interface without any disconnects, but when I click the 'G-Code Files' tab, sometimes it'll load the page and then disconnect, other times it'll instantly disconnect. The only way I can reconnect and have a stable connection is power-cycling the DUET-E (EtherNet) v1.02 controller.
When the connection crashes, the WebConsole emits an error message:
! Request Timeout
The last HTTP request has timed out. Please make sure the connection between your
device and the board is not interrupted.
DUET-E Controller Info:
Duet 2 WiFi/EtherNet Board (v1.02)
Firmware: 2.03 (2019-06-13b2)
Web Interface: 1.21
The settings in the DUET-E controller are:
M552 S0 ; Disable network
; ----------------- static IP direct connect via CAT5e cable DUET-E controller config ------------
M552 P192.168.2.2 ; Static IP Addr - DUET's IP Addr
M553 P255.255.255.0 ; NetMask
M552 S1 ; Enable network
The settings in Ubuntu 14.04 Linux - /etc/network/interfaces file are:
iface lo inet loopback
iface eth0 inet static
While in the Ubuntu DeskTop 'NetworkManager' taskbar dialog
the IPv4 Settings are:
I think this should be working.
Maybe its a really old DUET-E firmware version problem thats been fixed? The NoteBook Linux seems to be doing something that may be
scrambling the controller logic?? It isn't a perfect world. Although these DUET products are very good IMO. I was lucky finding you guys. Thanks.