Connecting to Duet3 with Macbook
-
@bearer also the diag led is dimly lit all the time, either with or without the erase pins connected...
-
@meatfest said in Connecting to Duet3 with Macbook:
also the diag led is dimly lit all the time
That means that the firmware has been erased. It should flash once a second if firmware is running. Also note that the Bossa program doesn't work on Mac OS to flash Duet 3 (it does work with Duet 2) so use a Windows PC to flash the firmware.
Ian
-
I switched to my Windows 10 machine for now, I just want to get it working. I will look at re flashing firmware.
-
@meatfest still stuck. let me re-cap.
I have Duet3D board.
I am using Windows 10 (stopped using my Macbook Pro)
I have installed Bossa and Sam-Ba
I have updated the driver for USB and it shows Bossa Program Port (COM 9) in Device Manager.
With Sam-ba I get message:
Error h_handle returned zero
while executing
"TCL_Open $target(connection)" ....
With Bossa I get the message:
Could not connect to device on COM9 -
@meatfest It sounds like something is still connected to the Duet on COM9. I'd suggest restarting your PC, then just use Bossa to flash the Duet.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts rebooted, same message from Bossa...
Could not connect to device on COM9
-
While its possible there is a problem with the board, all the other instances has turned out to be issues with software or usb cables.
As such I think it could be worth while trying to build bossa from sources on the Mac and see if it makes a difference after applying a patch to the code.
Is cloning code with git and running make to build it something you're comfortable with on the Mac?
-
If you happen to have a Raspberry Pi, there are instructions on the Dozuki to set it up and try it. They are sometimes better at finding the bossa port. Sometimes.
-
@meatfest said in Connecting to Duet3 with Macbook:
@droftarts rebooted, same message from Bossa...
Could not connect to device on COM9
Which version of Bossa are you using?
-
Success!
In device manager I selected show hidden devices and found two instances of Bossa one was inactive the other active. I deleted both and reconnected and then when I selected the new com port I ran write and verify and all was well. It seemed that Windows held onto two com ports , one was hidden thus causing the problem. Something to bear in mind!
-
-
This post is deleted!
