Good point Elk as pointed out above , there are multiple scenarios on top of variables depending on one’s system. Issues I would guess lie within the process vs the product. However ease of use is always a factor. Everyone just wants their stuff to work and I’m very happy mine does…
But, who knows what the actual problem is with your device since you won’t send it in to get fixed. Is your problem the same or completely different? You can’t say that it is the same so you are doing a disservice to PS Audio here.
2 Likes
I downloaded the Bridge 2 update directly from my directstream. I did not use a SD card. I’m still wondering though since my signal from my internet was getting a strong signal, why the DSD didn’t see my bridge since my ethernet cable was hooked up to the Bridge, and the DSD was working fine before the update.
Few others have had problems with firmware updates, so either you are doing something wrong (like formatting the SD card on a Mac, which won’t work) or your hardware is defective.
I’d say that if you aren’t willing to let PS Audio fix your updating issues, you should probably quit pointlessly whining about them.
2 Likes
Yes, you can format the SD card on the Mac. Here is a link to how:
https://forum.psaudio.com/t/my-ds-wont-update-to-redcloud-totally-stumped/5203/4?u=speed-racer
The usual Mac Disk Disk Utility method no longer works for FAT16 for some reason. It took me quite a while to discover this.
The only times I’ve had a f/w update brick a PSA component was during beta testing and I was perfectly OK with that.
Please, Paul, don’t stop: the updates are welcome and wonderful. And one for the DMP would be so, so wonderful.
PS Audio are on top of the support process, completely to my satisfaction. Suggestions with regard to my case in particular from those who aren’t directly involved, who I know are well meaning, I can assure everything is under control. There is no urgency on my part to rattle anybodies cages to embark on a different course to that which is underway.
For those few who have similar symptoms, my repeated comments on this topic in response to theirs is just to assure them they are not alone. A problem shared is a problem halved. And if it’s of any reassurance to them, I’m confident PS Audio will get on top of it all so the firmware update is rock solid for one and all.
1 Like
I’m feeling lucky after reading so many posts. My experience with all my PSA products is flawless performance, flawless update up/downloads, great forum connections, I’m a happy customer.
Ditto- and when I did have a question, I called Jeremy or Duncan and it was handled…So far- 5 Stars…
1 Like
Quite. PS Audio is the only manufacturer that I know that employs this SD card software update method. Here is a summary of what we’ve learned about all the variables at play with the process:
- it depends on the SD card used.
- it depends how that SD is formatted.
- it depends how/if that SD was ejected properly after format or copy of files.
- it depends on what software version you’re starting with, and aiming for.
- Some software updates work better if you go backwards first.
- Some software updates work better if you start with a “forced” version first.
Now, here are some alternatives that I’m familiar with in my home.
Sony TV. I woke up this morning and turned on the TV. On the screen was a message “a software update is available, do you wish to update?”. I pressed the OK button on the remote control and the process ran automatically from there. I’ve only owned the TV for a week and there have been 3 software updates in that time.
Success every time.
Kaleidescape. I don’t get a choice with this one. The manufacturer pushes the update to my device and I have absolutely no control over the process. It will update automatically whether I want to or not.
Success every time.
Axis IP cameras. I’m spoiled for choice.
a. There is a Windows updater app that runs in the background on the PC and it tells me when an update is available for a camera. I just have to click on a button and it grabs the latest software from the Axis web site and runs the update automatically. I can choose to update all the cameras on the network together, successively, or individually.
b. I can use TELNET connection to upload the software file directly to the camera.
c. I can use webUI and browser to connect to the camera and upload the software.
Success every time.
Lumagen Radiance. There is a Windows updater app. I download the required update from the Lumagen website to the PC, which is connected to the Lumagen device via USB or serial RS232. I run the updater app, point it at the desired software, and it connects to the Lumagen and runs the process automatically. If for any reason the update fails, turning off/on the Lumagen reverts to the previous software.
Success every time.
Pakedge networking stuff. Again, spoiled for choice.
a. A management agent on the network looks after the whole process, you just need to select “update” if you want to do an update and it grabs the software from the cloud and runs the process automatically.
b. CLI (command line interface) for direct upload of the software file to the device. Connect the PC to the CLI port and run the appropriate commands in the terminal emulation program (PuttY, etc). Very useful if the device is being temperamental and the webUI is not working.
c. Connect to the webUI of the device and update the latest software from the cloud.
d. Connect to the webUI of the device and update any other version of the software sent from Pakedge Support (they send me beta software from time to time for testing).
The only issue I’ve had with a Pakedge software update was loading the wrong software on a switch and it bricked it. No fix possible. No safeguard against loading the wrong software on that particular switch. All my own fault, bricked a $2000 switch through my carelessness.
Success every time (except for the one example mentioned).
Esoteric. I need to watch the Esoteric website or owners forums for this one to discover when a software update is available. When so, I just go to the iPad Esoteric SoundStream app and select update from the device configuration window. It tells the Esoteric network-enabled device to do what it needs to do and the process runs automatically to completion. When done, the final step is for me to power off/on the Esoteric device and the new software will install.
Success every time.
Now let’s compare these against the SD card update process. And all those variables that you need to negotiate spot on for it to work. And all those other things that might be at play which aren’t understood, when people follow exactly what is known but fail to succeed. The process is exposed to too many variables that will lead to failure. And to variables that aren’t yet known that will lead to failure.
There is a better way. I’ve described all the other choices above. If we are locked into the SD process by virtue of the PS hardware design, then something more robust than what presently exists needs to happen. And I know they are working on that, Paul has said so.
None of the six “variables” you have declared need be “spot on” make any difference for me; swapping firmware with any of the PS Audio products just works and does so simply.
Something else is at play.
There are plenty of products with update procedures which require user involvement of various degrees. Most procedures work well for the vast majority. There will always be some with issues.
In your circumstance, you have had so many problems with different products that I suspect there is something specific going on which is common to all, but I have no clue what it might be.
1 Like
I’m not making the declaration. They are all things that Ted has said over the passage of time in the forums here that can affect the software update success or otherwise.
The root cause of my 10 power plant failures has been dealt with. The transistors were changed with more robust higher voltage ones. And the power utility changed the mains transformer in my street, so I’m not exposed to 258V+ any more (which I mention, my long term power play data captured by PS Audio server was instrumental in getting Western Power to do something about it). I’m now on a more subdued 227-248V range.
Declared, listed, summarized, identified, enumerated, what-evered. 
Which is excellent news. But you have complained repeatedly about PS Audio products in addition to Power Plants, especially with respect to firmware updates. It remains odd you have so many problems. There must be a root cause.
Doesn’t gravity work differently down there? Sorry, just feeling a bit ornery.
The Dectet tripping problems were fixed with software, to make it more tolerant of voltage variations. So that was another complaint of mine which was fixed, it’s not as if these things haven’t been getting fixed. There are only 3 outstanding support issues for me, and they are all pending and under control.
No. But coriolis does.
Most are taken out of context, misunderstood or incorrectly quoted.
Update issues are mostly a function of the state of the device being updated or the state of the SD card being used, not software versions, etc.
- the size of a SD card does indeed matter and which file system it’s formatted to does matter
- a format may be required if the user forgot to use eject somewhere in the past or powered off a device that had the SD card installed while a write was happening, how big the hazard is depends on the version of the PC’s OS and what options the user has set for the card reader/writer device or the particular card in the OS - a priori this has nothing to do with PS Audio updates - its always true
- it’s independent of which release you start with or are going to - if the unit has a corrupted flash and if you are installing what it thinks it already has, then you can’t do an update to that release (after all we don’t want the device to reload the same software over and over every time it’s powered on.) So when there’s already been a bad update (or flash corruption in the device) going to any other release and back is the best course of action.
- it’s independent of the particular release of software, except that earlier versions of software may have fewer update related bugs fixed - (during beta things are more complicated but explicit instructions are usually given if there may be an issue.)
When I give a long list of things to do to recover remember that many of them may not be needed in any particular case but all of them are needed in some cases. If you have never needed to do a particular step but are having a problem you should do all of the steps to save yourself a lot of wasted time.
I give a shorter set of steps to people if I’ve got enough information to know which steps can be skipped, but just because I don’t mention a step in any given post doesn’t mean it is never required for that release, etc.
This isn’t as black of magic as things sound. But that doesn’t mean that PS Audio is happy with the current state of affairs.
2 Likes