# 2.2.0 firmware for new production PWDs

**URL:** <https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185>\
**Category:** DACs\
**Created:** [June 6, 2013, 1:38pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185 "2013-06-06T13:38:01Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![Streets\_Still\_Works](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/streets_still_works/32/23_2.png) [@Streets\_Still\_Works](https://forum.psaudio.com/u/Streets_Still_Works)\
**Post date:** [June 11, 2013, 7:39am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/41 "2013-06-11T07:39:45Z")

</div>

There are too many variants of 2.2.0 out there. I just downloaded one dated 6/6/13 with DPL109 but the official link still has the 2.2.0 version dated 3/20/12 and DPL104 dated 12/19/2011  
  
  
  
Aargh. which one is correct?  
  
  
  
Should there be a 2.3.0 release that only has the correct files in it just to end the confusion?  
  
  
  
–SSW

---

<div class="post-metadata">

**Author:** ![setamp](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@setamp](https://forum.psaudio.com/u/setamp)\
**Post date:** [June 11, 2013, 8:20am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/42 "2013-06-11T08:20:39Z")

</div>

And how much of the difference lies with the Bridge firmware vs PWD firmware?  
  
  
  
I do not have the Bridge installed. The difference (positive) I hear should not be due to Bridge firmware.  
  
  
  
@Gordon It is interesting that you you are hearing the 2.20 glare with this version. I get none of it. I found the old 2.20 to be horrid but this to be a cleaner version of 2.02.

---

<div class="post-metadata">

**Author:** ![wglenn](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/wglenn/32/172_2.png) [@wglenn](https://forum.psaudio.com/u/wglenn)\
**Post date:** [June 11, 2013, 2:18pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/43 "2013-06-11T14:18:12Z")

</div>

> streets still works said: Should there be a 2.3.0 release that only has the correct files in it just to end the confusion?

  
 Great idea!

---

<div class="post-metadata">

**Author:** ![alekz](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/alekz/32/1121_2.png) [@alekz](https://forum.psaudio.com/u/alekz)\
**Post date:** [June 11, 2013, 3:10pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/44 "2013-06-11T15:10:10Z")

</div>

Since the code is the same, it shouldn’t be 2.3. Rather 2.2.1 or even 2.2.0.1. Or use build numbers: 2.2.0 b1234

---

<div class="post-metadata">

**Author:** ![mariankiely](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@mariankiely](https://forum.psaudio.com/u/mariankiely)\
**Post date:** [June 11, 2013, 3:23pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/45 "2013-06-11T15:23:07Z")

</div>

Working on it. Patience please. [-O\<

---

<div class="post-metadata">

**Author:** ![Streets\_Still\_Works](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/streets_still_works/32/23_2.png) [@Streets\_Still\_Works](https://forum.psaudio.com/u/Streets_Still_Works)\
**Post date:** [June 11, 2013, 3:24pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/46 "2013-06-11T15:24:18Z")

</div>

> Since the code is the same, it shouldn't be 2.3. Rather 2.2.1 or even 2.2.0.1. Or use build numbers: 2.2.0 b1234

  
  
 I want to see another digit in it besides a 1, 2, or 0  
  
 It's driving me nuts.  
  
 :)

---

<div class="post-metadata">

**Author:** ![ryonlunch32](https://avatars.discourse-cdn.com/v4/letter/r/9e8a1a/32.png) [@ryonlunch32](https://forum.psaudio.com/u/ryonlunch32)\
**Post date:** [June 11, 2013, 3:36pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/47 "2013-06-11T15:36:27Z")

</div>

So you want PWD firmware version 2.2.3? 😃  
  
  
  
J.P.

---

<div class="post-metadata">

**Author:** ![madmacs99-2](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@madmacs99-2](https://forum.psaudio.com/u/madmacs99-2)\
**Post date:** [June 11, 2013, 3:48pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/48 "2013-06-11T15:48:48Z")

</div>

> streets still works said: It's driving me nuts.

  
  
 me too, and it is a short trip   
 8-}

---

<div class="post-metadata">

**Author:** ![mariankiely](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@mariankiely](https://forum.psaudio.com/u/mariankiely)\
**Post date:** [June 11, 2013, 4:21pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/49 "2013-06-11T16:21:24Z")

</div>

take a look at the JR Mac section [[http://yabb.jriver.com/interact/index.php?topic=81302.0](http://yabb.jriver.com/interact/index.php?topic=81302.0) ] where he lists the latest version with what was fixed or added, any known issues and what variables to test for. See if you like the format. [the feedback could be in a separate thread to keep the “download” thread clean like I tried to do by closing the thread. [until we get the new forum]  
  
  
  
So the process would be that any new release goes to Beta group. If a couple of days reveals no issues then it becomes an “official release” posted in the general forum and in the PSA support area. They can then turn on the auto update feature if they want to.

---

<div class="post-metadata">

**Author:** ![alekz](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/alekz/32/1121_2.png) [@alekz](https://forum.psaudio.com/u/alekz)\
**Post date:** [June 11, 2013, 4:22pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/50 "2013-06-11T16:22:26Z")

</div>

> > Since the code is the same, it shouldn't be 2.3. Rather 2.2.1 or even 2.2.0.1. Or use build numbers: 2.2.0 b1234
> 
>   
>   
> I want to see another digit in it besides a 1, 2, or 0  
>   
> It's driving me nuts.  
>   
> :)

  
  
 What about the suggested b1234? :D

---

<div class="post-metadata">

**Author:** ![alekz](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/alekz/32/1121_2.png) [@alekz](https://forum.psaudio.com/u/alekz)\
**Post date:** [June 11, 2013, 4:24pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/51 "2013-06-11T16:24:05Z")

</div>

> Gordon said: [until we get the new forum]

  
  
 Yeah, right... :-t

---

<div class="post-metadata">

**Author:** ![rogerdn](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@rogerdn](https://forum.psaudio.com/u/rogerdn)\
**Post date:** [June 11, 2013, 5:00pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/52 "2013-06-11T17:00:19Z")

</div>

> take a look at the JR Mac section [http://yabb.jriver.com/interact/index.php?topic=81302.0] where he lists the latest version with what was fixed or added, any known issues and what variables to test for. See if you like the format. [the feedback could be in a separate thread to keep the "download" thread clean like I tried to do by closing the thread. [until we get the new forum]  
>   
> So the process would be that any new release goes to Beta group. If a couple of days reveals no issues then it becomes an "official release" posted in the general forum and in the PSA support area. They can then turn on the auto update feature if they want to.

  
  
 Yes, yes, yes

---

<div class="post-metadata">

**Author:** ![Elk](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/elk/32/1240_2.png) [@Elk](https://forum.psaudio.com/u/Elk)\
**Post date:** [June 11, 2013, 6:52pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/53 "2013-06-11T18:52:19Z")

</div>

> Gordon said: . . . lists the latest version with what was fixed or added, any known issues and what variables to test for. See if you like the format.

  
 Something similar makes sense, together with a defined nomenclature. Anything is fine as a naming convention as long as it is consistent.  
  
 Don't over think it and make it simple to implement.

---

<div class="post-metadata">

**Author:** ![Streets\_Still\_Works](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/streets_still_works/32/23_2.png) [@Streets\_Still\_Works](https://forum.psaudio.com/u/Streets_Still_Works)\
**Post date:** [June 11, 2013, 8:21pm UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/54 "2013-06-11T20:21:55Z")

</div>

Yaay, I finally got 2.2.0 and PLD 109 installed.  
  
  
  
but the alternator in my car died, so now I have to go fix that.  
  
  
  
Aargh.  
  
  
  
–SSW

---

<div class="post-metadata">

**Author:** ![birddogthecat](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@birddogthecat](https://forum.psaudio.com/u/birddogthecat)\
**Post date:** [June 12, 2013, 7:39am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/55 "2013-06-12T07:39:00Z")

</div>

@audioslave I do not understand how to use the link. It looks like a white box. Do I double click it? Right click it? Copy?

---

<div class="post-metadata">

**Author:** ![Streets\_Still\_Works](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/streets_still_works/32/23_2.png) [@Streets\_Still\_Works](https://forum.psaudio.com/u/Streets_Still_Works)\
**Post date:** [June 12, 2013, 8:02am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/56 "2013-06-12T08:02:44Z")

</div>

> @audioslave I do not understand how to use the link. It looks like a white box. Do I double click it? Right click it? Copy?

  
  
 Click the white box. It should download a .zip file. Save it into a known location. Unzip the files and transfer them to the root directory of the 2 GB SD card from the DAC. Make sure all the old files are NOT in the root directory first (I just made an "archive" folder and threw the old files into it, thus keeping the root directory 'clean' for the newly downloaded an unzipped files. Turn the DAC off with the back power switch, insert the SD card into the DAC (SD card contacts facing UP toward the glossy top and away from the mounting feet). Turn the DAC on with the power switch, and if all goes well, the power button at the front panel will start to blink indicating the load process has started. You'll get an 'initialization' screen (DON'T touch the screen or interrupt the boot with the power switch.) In my case last night it booted, then I got another "initilization" screen that acted like a normal boot, and I confirmed that 2.2.0 was loaded.  
  
 best of luck.  
  
 --SSW

---

<div class="post-metadata">

**Author:** ![setamp](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@setamp](https://forum.psaudio.com/u/setamp)\
**Post date:** [June 12, 2013, 8:06am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/57 "2013-06-12T08:06:58Z")

</div>

I suspect there is a hardware/software interaction that causes some PWD’s to work well with some firmware versions but not others. It would good to have a repository for all past firmware so we have the ability to find the version that works with our serial number.

---

<div class="post-metadata">

**Author:** ![birddogthecat](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@birddogthecat](https://forum.psaudio.com/u/birddogthecat)\
**Post date:** [June 12, 2013, 8:19am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/58 "2013-06-12T08:19:30Z")

</div>

@streets still works are these the files I need send/copy to the card? Are they ready to send/copy? I plan to use a new SD Card and then replace it with the old. Is this how to do it?

```
<fieldset class="gc-fieldset">
							<legend> Attached files </legend> <a href="/wp-content/uploads/attachments/54312=1875-da5b4b0890493ba7ce29d9c1229b1d.png"><img src="/wp-content/uploads/attachments/54312=1875-da5b4b0890493ba7ce29d9c1229b1d.png" class="gc-images" title="/FileUpload/4e/da5b4b0890493ba7ce29d9c1229b1d.png" style="max-width:300px" /></a> </fieldset>
```

---

<div class="post-metadata">

**Author:** ![Streets\_Still\_Works](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.psaudio.com/streets_still_works/32/23_2.png) [@Streets\_Still\_Works](https://forum.psaudio.com/u/Streets_Still_Works)\
**Post date:** [June 12, 2013, 8:33am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/59 "2013-06-12T08:33:35Z")

</div>

Yes, those are the right files, just drag/drop onto the root directory of the SD card. Be aware that the SD card has to be 2 GB or smaller, so a newer SD card may actually not work if it’s too big. finding 2GB cards nowadays is actually harder than one may think. Hence my suggestion to use the one that came with the PWD and just move the old files into an ‘archive’ folder and away from the root directory. I did that with mine and it worked fine.  
  
  
  
Best of luck.  
  
  
  
–SSW

---

<div class="post-metadata">

**Author:** ![birddogthecat](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@birddogthecat](https://forum.psaudio.com/u/birddogthecat)\
**Post date:** [June 12, 2013, 8:36am UTC](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185/60 "2013-06-12T08:36:35Z")

</div>

@streets still works You have been great. My new card reader arrives today from [Amazon.com](http://Amazon.com). Do I “archive” the old files on the same card or transfer and store on my PC? Found & ordered 2 SD 2GB cards from [Amazon.com](http://Amazon.com) just now. I will just keep them for some future project: [http://www.amazon.com/SanDisk-Flash-Memory-Card-SDSDB-002G-AFFP/dp/B007JRB0QA/ref=sr\_1\_1?s=pc&ie=UTF8&qid=1371051991&sr=1-1&keywords=sd+card+2gb](http://www.amazon.com/SanDisk-Flash-Memory-Card-SDSDB-002G-AFFP/dp/B007JRB0QA/ref=sr_1_1?s=pc&ie=UTF8&qid=1371051991&sr=1-1&keywords=sd+card+2gb)

[Previous page](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185.md?page=2)

[Next page](https://forum.psaudio.com/t/2-2-0-firmware-for-new-production-pwds/185.md?page=4)
