myway -> emyway
This was much simpler than the previous job (but chronologically this was the first to be done), because the only things that had to be done is just to replace the nav units and the screens, the wiring stayed the same, no additional components or parts were necessary.
The emyway (RT6) unit and the matching screen (DG4), because it won't work with the RNEG/RT4 screen:
The installation phase is shown below:
First ignition and different modes:
Here's where it gets interesting, after putting the plastic cover back on:
The cover "cuts" the screen on the top. I was surprised to find out that the new screen is slightly taller than the old one (2,5 mm approx), and until today I had the old cover in place, with the new cover being ordered from Citroen. The interesting thing is, we ordered per VIN number by their display car which has emyway installed from the manufacturer, and last week the exact plastic cover that I have arrived ... how, what, why ... no one is really sure, the part number was matching the Service Documentation ... anyways, the order was disputed to the Citroen (Croatia and then back to France), and the new, required cover with the bigger screen hole should arrive in a few hours. Who knew such unexpected problems would happen.
Now, one of the yet unresolved problems is with the wheel screen, it won't display the navigation data, it just displays zone not mapped (remember the previous post, where that means that really the zone is not mapped, in this case, it means no data is being transferred from the nav unit to the instrument panel) ... Everything was done as it should've been, I went through DiagBox three times over, nothing ... went to the Citroen Service, and asked them to do the BSI update, supposedly it could help, but, no, it didn't ... the only software thing that can be done is to try and update the instrument panel (if possible) ... luckily I can do without the navigation information on the small screen (it can be turned off in DiagBox to not be displayed while rotating the display modes), but since I'm looking for a 100% solution, I haven't given up on this yet.
Although I've said in the beginning that no additional parts were required, I went for the genuine USB cable and the USB/Aux connector in the glovebox. Without that, you can't do map/speedcam updates, or obviously, play USB/iPod music. The firmware updates are done via CD, like on the RNEG i.e.
Was it worth it (not looking into finances, but even that is not that expensive, since I've managed to sell the old one)? I'd say yes, the emyway displays track names and folders from the USB stick, Bluetooth music streaming works (but just the phone name is displayed, no music info), the maps are more fluid in animation, the interface is more to my liking, the speed limits are displayed where available ... the thing that hasn't changed from the previous configuration is that the phone signal (visual representation) still gets lost when you go into roaming (which I occasionally do), and until you reconnect the phone, it will be displayed as no signal ... but when you get used to it, you know how it works ...
The RT6 has an active cooling (fan), which makes some noise compared to the RNEG, but that isn't bothering me, at least I know it will be slightly cooler than the previous unit (which would heat the lower compartment a lot after 2+ hours of drive ...). I've tried using the USB with the USB HDD (2.5", single cable, FAT32), but the emyway refuses to see it (the HDD works, because it gets electricity from the USB connector), but no interaction with the nav unit ... regular USB sticks seem to work just fine.
The final situation looks like this:
The currently unsolved situation with the "Zone not mapped", happens because somewhere along the line of communication the instrument panel doesn't know how to display what the emyway is sending, if it is sending anything ...
IMPORTANT EDIT: It took me almost a year, but I've finally resolved the "Zone not mapped" mystery ... the said error was driving me nuts, and with the help of Mira (yep, the guy who's behind MiraScripts, those of you who know about that), I've located the one single parameter that was wrongly set on my device (since I've obtained it obviously), so now I have a fully working instrument panel matrix navigation display once again.
The parameter is 1.9.146. and it can be within 0-4 range, the setting that worked for me was 3 (2 was almost working, with no street names displayed). How that looks like is visible below:
Parameter 2
You can compare the previous image, on it there is no compass visible, and no altitude shown (hence, no data get's transferred from the RT6 unit to the matrix display)
Parameter 3
Here everything is 100% fully working (as fresh from the factory)
... anyways, that meant that my old setup had to go (hence the spare parts I'm selling), and I've managed to find a buyer for the old navigation ... the good thing about all of this was the experience gained and seeing how stuff works ... the bad thing was a lot of time spent in neutral gear due to unexpected problems and a few nerves that probably aren't working as they should ... 
