| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| swift_nav_duro [2026/03/23 14:48] – [MicroUSB] admin | swift_nav_duro [2026/11/08 16:49] (current) – [Photos] millerjs |
|---|
| ====== Swift Navigation / Carnegie Robotics Duro ====== | ====== Swift Navigation / Carnegie Robotics Duro ====== |
| | <note important>My findings regarding SSH and TTY access may not apply to all models! |
| | See [[swift_nav_duro#limited_access|Limited Access]]</note> |
| [{{:swiftnav:duro:swiftnav_duro.png?400 |Photo credit Carnegie Robotics}}] | [{{:swiftnav:duro:swiftnav_duro.png?400 |Photo credit Carnegie Robotics}}] |
| |
| \\ | \\ |
| |
| Note about this port: it does deliver power to the Piksi Multi, but I'm not sure if the rest of the Duro board is powered or if that configuration is even kosher. Usually in cases like this the Vcc line of the USB port is left disconnected, requiring the user to operate the device from a separate and more powerful supply. I don't know if this was intentional or a mistake made when designing the Duro board. | Note about this port: it does deliver power to the Piksi Multi, but I'm not sure if the rest of the Duro will work correctly. Usually in cases like this the Vcc line of the USB port is left disconnected, requiring the user to operate the device from a dedicated supply. I don't know if this was intentional or a mistake made when designing the Duro board. In my own testing, the Duro does work when powered from MicroUSB alone, pulling just shy of 5w in normal use. Ethernet and microSD work, I have not tested the RS-232 interfaces. I don't see any warnings or complaints in the logs, and performance appears unchanged. |
| |
| ==== microSD ==== | ==== microSD ==== |
| |
| If we ever want that stuff to run again, all we have to do is comment out the ''CUSTOM_SCRIPT'' line in the config file, reboot again, and all those intit scripts will run again - but make sure the config file is backed up (or duplicated under another name in /persistent/) because of course it will be deleted. | If we ever want that stuff to run again, all we have to do is comment out the ''CUSTOM_SCRIPT'' line in the config file, reboot again, and all those intit scripts will run again - but make sure the config file is backed up (or duplicated under another name in /persistent/) because of course it will be deleted. |
| | |
| | ==== Limited Access ==== |
| | In November 2026, I picked up a few more Duro's that had been listed as "defect". In the ones that work, I found generic firmware - no Unicontroll stuff - and also, no shell access anywhere. No SSH, no third TTY going to agetty, nothing. I'm doing some digging to see if I can figure out how to get into it and get it back. |
| ===== Photos ===== | ===== Photos ===== |
| | Note: these are all photos of my first Duro. If my others have different features, or anything worth showing, I will add them. |
| | |
| My Duro is a late model, with Carnegie Robotics branding. It is not clear to me when it was manufactured, but the [[https://www.marvell.com/content/dam/marvell/en/public-collateral/phys-transceivers/marvell-phys-transceivers-alaska-88e1512-product-brief.pdf|Marvell PHY]] on the carrier board has a late 2021 date code. The Piksi Multi seems to be an 00108-09 revision, but I haven't confirmed its date of manufacture yet. | My Duro is a late model, with Carnegie Robotics branding. It is not clear to me when it was manufactured, but the [[https://www.marvell.com/content/dam/marvell/en/public-collateral/phys-transceivers/marvell-phys-transceivers-alaska-88e1512-product-brief.pdf|Marvell PHY]] on the carrier board has a late 2021 date code. The Piksi Multi seems to be an 00108-09 revision, but I haven't confirmed its date of manufacture yet. |
| |
