Duet 3 Web Address in Stand Alone Mode
-
@bearer said in Duet 3 Web Address in Stand Alone Mode:
hth
Thanks I will give this a try today. Have you connected using YAT or are you using a different terminal?
-
@Collin said in Duet 3 Web Address in Stand Alone Mode:
@bearer said in Duet 3 Web Address in Stand Alone Mode:
hth
Thanks I will give this a try today. Have you connected using YAT or are you using a different terminal?
I use YAT. But as my router has a habit of changing the IP address now and then, I now use static IP addresses anyway.
-
@Collin said in Duet 3 Web Address in Stand Alone Mode:
Have you connected using YAT or are you using a different terminal?
I tend to gravitate towards RealTerm mainly for ANSI(hex and binary) support; but if you don't have a preference I'd stick with Yat as that is what is documented in the wiki. On the other hand for Duet boards I'll only break out the USB cable if putting the correct config on the SD card doesn't yield the desired result.
-
Okay so I am trying to connect with YAT and I am still seeing the board only come up in the device manager as Bossa Program port. I followed the thread link below to do the fall back procedure since it sounds like the firmware wasn't on the board.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3I downloaded and used the "Duet3Firmware_MB6HC.bin" and loaded this with Bossa and check marked "Erase all, lock, and boot to flash". After the write/verify is successful, I reboot the board and it still shows as Bossa Program Port.
https://github.com/dc42/RepRapFirmware/releases/tag/3.0Has anyone successfully loaded a firmware on Duet 3?
-
@Collin said in Duet 3 Web Address in Stand Alone Mode:
Has anyone successfully loaded a firmware on Duet 3?
Yes, but using the command line tool bossac. Maybe you have the erase jumper still in place, that would have the effect you describe.
-
@bearer I definitely used a jumper on the erase pins to startup the board so it makes sense the firmware is gone, but the problem is once I flash it with new firmware, it doesn't show up at a Duet 3D Printer device in Device Manager. It still shows as Bossa Program Device
-
Maybe I was unclear; I was trying to make sure you removed the jumper prior to using Bossa to flash the firmware. Try pressing verify after the flashing is complete and see what it says.
-
@bearer Ahhh Gotcha, Yes the jumper is removed.
-
Hmm, and you're using the latest 1.9.1 version of Bossa?
-
I restarted my laptop and under device manager > Other Devices I can find the Duet now. I am using the link below to download duet usb drivers and I am wondering if there is another link for duet 3 specific drivers. When I try to use this driver is says it could not find the driver files inside the folder.
-
@Collin said in Duet 3 Web Address in Stand Alone Mode:
if there is another link for duet 3 specific drivers.
no idea what drivers you have, nor have i needed any drivers. however i suspect if you open the .inf file and replace
60ecwith60eethe drivers will work for duet3 instead of duet2.(edit; or maybe you should check that your duet has the correct hardware ids first.
-
@bearer Yes that worked and I was able to load the firmware! I had to replace it in 3 difference locations inside the driver files. Now I can get into YAT and it said my IP address was 0.0.0.0 using the m552 command.
Now I connected with the ethernet cable and in chrome, when I type in 0.0.0.0 it still doesn't load. any thoughts?
-
Also stupid question, does this need connected to my router or to my laptop ethernet port? I am connected to the ethernet on my laptop directly to the Duet 3 with ethernet.
-
@Collin said in Duet 3 Web Address in Stand Alone Mode:
Now I can get into YAT and it said my IP address was 0.0.0.0 using the m552 command.
Thats not a valid IP adderss but a special case to use DHCP to have your router assign an IP address dynamically; so either connect to your router or set a valid static IP for both the Duet and the computer.
I had to replace it in 3 difference locations inside the driver files.
(as a side note you only had to replace it in the correct place for your operating system, but easier to do all))
