Posts made by darbyad85

thanks so much - I am indeed up and running!

thank you, do I need to perform M997 S0?

I have 3.0 i didnt upgrade to 3.4.1
I have found the DWC zip file that is part of 3.0 - can i just install the same way i did to get to version 3.0 or do i delete and install all together?

I updated the wifi and rap/rep at the same time, is there also an update for the DWC
I was on version 2.03 but used the Duet 2 and 3 firmware 3.0 as advised - is there something else i have missed?

Thanks

@jay_s_uk I've updated the firmware and it doesn't seem to have solved the problem. M552 61 is confirming I am connected and the right IP address for DWC but all I get is a blue bar saying 'Connecting...' with no connection

I have been happily connected for 24 hours and not i cannot get on the Duet Web Control
I am connected to WIFI and can see the screen in the background but i am getting a blue screen saying connecting and at the bottom the following message
Failed to connect - incompatible fireware

I just wanted to check it would be the Duet that needs firmware updating? I am running version 2.03 currently
What i dont understand is why did it work yesterday and not today?

@phaedrux thanks... managed to sort this now! Home wifi was 2.4 and its now connected... trouble I think was registering it on the diplay board rather than YAT

So i have been trouble shooting all day
My WIFI and hub at home both run 5GZ - could this be the issue

I have also connected to both our phones and get the following

Remembered networks:
TNCAPF2FD81 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
Three556370 IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
Bens iPhone (3) IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
Adele IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0

It connects but i still cannot connect to wifi - the fact that i see all 0's make me think its not connected to anyone of them

@phaedrux I am as far as connecting to WIFI and im blocked again
I have started another thread asking for help

I have entered command M552 and entered the login details for my router
#I have also confirmed it is a remembered device

when i enter the next step M552 S0 - from YAT i just get ok and on the Panel it just continues with
WiFi reported error: no known networks found
WiFi module is idle
WIFI reported error: no known networks found
WIFI module is idle

I have tried disconnecting WIFI and reconnecting

What i am expecting to see is that its connected the WIFI and it gives me an IP address so i can connect to DWC

Thanks in advance

@phaedrux thank you.
so where I am is that the DuetDue touchscreen panel firmware has been updated, it says 'connecting' in the top right corner.

As for my laptop I still can't find the Duet in device manager and now I've downloaded YAT I can't select it as a serial port.

Not sure where to go from here... can the panel really be faulty? It was brand new out of the box.

Thanks for your quick reply - so i am not sure the difference between the Duet and the PanelDuet - currently my laptop is connected to my WIFI and a USB connection to the small 7 inch panel but the 4 pin cable that goes into the big machine is not plugged in - does that need to be plugged in ?
Thanks again

I didnt get far, i installed YAT and its looking for port (COM port) but there is nothing there and there is nothing in device manager. I am connected to the Panel but via USB am i doing something wrong?

Amazing thanks alot!!! I am helping my husband ( i am more technical than him) but still not that technical! Will keep trying to set it up!

I recently got this device and have been trying to set it up, I have done all the trouble shooting i can and looking to see if there is anything i missed before getting a new panel.
I am plugging the panel into a laptop (Windows 10) and the device powers on but does not appear in the device manager. AS per other threads I reset and erased the device and put the lasted firmware on there. It still did not work and add to device manager. There is 2 green lights lit up on the bottom of the panel and the panel is PanelDue 7i. I have also checked and confirmed it is not the cable. Hoping i have missed something and there is an easy fix