Group Buy / EOI new generation DNS head units (RNS-510 alternative)

[DkN]

Ok just to clarify, the instructions I posted do work, they update the software in this order: BSP (colour text screen), MPU (white screen with text in the middle), MCU (software menu after unit boots into radio).

For the BSP update to come up, it is essential that you:

• start with a blank SD card (format it to make sure)
• make sure the "UPD" file in the firmware zip is the first file copied to the blank SD card (this is why you must extract this file and this file only, by itself, into the blank SD card before you extract the rest)

If your unit does not boot into the colourful text screen with the firmware SD in the GPS slot, most cases it's because the UPD file is not the first file copied to the SD card.

After the BSP update the MPU update will run itself. After it tells you to reboot the unit, whether the unit reboots itself or not, SWITCH OFF the unit. And then, REMOVE the firmware SD from the GPS slot, and start the unit again. If you do not remove the firmware SD before you start it again, you will end up at the colourful text screen for the BSP update again, and you will have to repeat the process and wait for the MPU update.

If you removed the SD from the GPS slot and started the unit it will simply boot into radio. When you see the radio screen, insert the firmware SD into the GPS slot again. You will get an automated popup menu asking to update the MCU. Choose yes and wait, then the unit will turn itself off when the MCU update is complete. At that point your firmware update is complete, remove the card from the GPS slot (again, do this before you turn on the unit or you will end up at the BSP update screen again), and you can turn on your unit with BSP, MPU and MCU all updated.

For reference, the updated firmware numbers are:

BSP: MS9.D
MCU: DNS810.131202_CAN
MPU: DNS810.A9.20131129

I use the exact same process above to update my firmware every time, so if you don't end up with these versions, go back, read the instructions, and follow them to the letter.

[polski_ogurek]

According to a photo I took of the system info (when I first got the unit), my BSP shows as MS9.C - therefore polsk it doesn't appear your unit has updated correctly.

I thought thats the case, I'll give it a go again, see if i can get it to work.

cheers lads.

[DkN]

Interestingly no-one has made a fuss about this.

I'm in same mindset as you. Current RNS is resistive, capacitive screen was very tempting but if this is not the case, I won be dropping $700 for just software upgrade.

I'll wait for the next generation.

I need to talk to the manager about this if you are receiving units with resistive screens. I have spoken to him from as early as January and he said the DNS will have capacitive screens. When I received my sample unit, I noted that it was a significantly more responsive screen than the ANS series but it still was resistive. I spoke to him and he said the final version of the unit will have capacitive screens. I didn't think this was going to be an issue and assumed the initial batch would receive capacitive screens - if this has not been the case then it appears the DNS series is receiving resistive screens after all. Again I will have to speak to the manager but there seems to be an issue of him simply not informing me of changes to features until I find out the hard way.

I will say this though, capactive screen or not the DNS is and always has been much more than just a software update. All components with the exception of the BT module I believe, have been updated, including CPU, RAM, DSP, radio module, GPS receiver, CAN-Bus decoder etc.

[cpkk]

Sandy, regarding the firmware update, I followed the instructions exactly the way you posted but something odd happens.

After the MPU update is successful, the unit does a quick reboot of itself and goes into the radio. I turn the unit off completely and remove the SD card then boot back up. Thing is, my unit doesn't boot straight into the radio, but instead I'm faced with a white screen and a crosshair in the middle with chinese text at the top (appears to be a touch calibration since I basically need to press where the crosshair is and repeat - middle, top left, bottom left, bottom right, top right) and then goes into another screen which I then have the tap the screen again.

After all that, I'm booted into the radio and follow the process as described.

I've checked firmware numbers and they match up with yours above...but just wondering whether there was any issues with my update given the slight nuance in process.

[DkN]

Sandy, regarding the firmware update, I followed the instructions exactly the way you posted but something odd happens.

After the MPU update is successful, the unit does a quick reboot of itself and goes into the radio. I turn the unit off completely and remove the SD card then boot back up. Thing is, my unit doesn't boot straight into the radio, but instead I'm faced with a white screen and a crosshair in the middle with chinese text at the top (appears to be a touch calibration since I basically need to press where the crosshair is and repeat - middle, top left, bottom left, bottom right, top right) and then goes into another screen which I then have the tap the screen again.

After all that, I'm booted into the radio and follow the process as described.

I've checked firmware numbers and they match up with yours above...but just wondering whether there was any issues with my update given the slight nuance in process.

That's just the screen calibration process, and if your taps weren't accurate enough it just repeats itself until it is able to properly calibrate the touch screen. It's not an issue, just a procedure the unit goes through when the software is updated.

On a side note, as someone pointed out this calibration should only be required for resistive screens so if you're getting this menu then it does appear the screen is resistive...

[Fdandy]

Overall the unit seems much faster now, switched canbus on, and that side of it works... no slowdowns as such, yet, but time will tell.

Do we need to set this manually in the secret menu?

Sent from my LG-E975K using Tapatalk

[polski_ogurek]

Do we need to set this manually in the secret menu?

Sent from my LG-E975K using Tapatalk

Should be Automatically set, unless you turned it off, mine was on IIRC.

[DkN]

Sandy can you make a list of which units and who is next on the list for the next batch? I was originally on the first batch list but then you changed it to the first come first served basis. If that is the case and my order hasn't come through since I am on the bottom of the heap now. I would like to withdraw my orders for both my units until the situation improves if that's alright with you.

Everyone else on the initial batch list will get their units in this second batch that I have received. The initial batch order was shipped to me in 2 batches so the first batch went to the earliest orders on the initial batch list. I'll do my best to organise the rest to all be sent out tomorrow, though I'm still crawling through emails and PMs right now.

[asa572]

Is there anyway to set the time? GPS time is right but if you put it on stand by it is always 3 hours behind.
When you try and change it in System Setting / Time Setting, pressing the up arrow on the hour adjustment and it just flicks straight back to the hour it's set at.
Last time I tried this I kept pressing the up button to see if it would work and it sent the unit into lag central and I had to do a restore.

[DkN]

Is there anyway to set the time? GPS time is right but if you put it on stand by it is always 3 hours behind.
When you try and change it in System Setting / Time Setting, pressing the up arrow on the hour adjustment and it just flicks straight back to the hour it's set at.
Last time I tried this I kept pressing the up button to see if it would work and it sent the unit into lag central and I had to do a restore.

That's one of the glitches that still remain - I think in light of some of the other issues they haven't really been focussing on the smaller things as I would imagine this should only take 10 mins for any programmer to fix. For now you can't adjust the system time setting.