[Polo]

Pi 4 with latest Pi OS Bookworm and all updates installed. Hopefully this is everything I did and I haven't missed documenting something...



I am correct, updated instructions. No need to switch to x11 now - this EDID works with Wayland also.
You can download from my Google drive here - Custom NTSC compatible 800x480i EDID for RNSE

/boot/firmware/config.txt - add the following section
hdmi_edid_file=1
[HDMI:0]
hdmi_edid_filename=Rpi_RNSE_800x480i_EDID.bin
hdmi_group=1
hdmi_mode=7

/boot/firmware/cmdline.txt - add to end of command line
drm.edid_firmware=HDMI-A-1:Rpi_RNSE_800x480i_EDID.bin

copy Rpi480i_EDID.bin to Pi
sudo cp /boot/Rpi_RNSE_800x480i_EDID.bin /usr/lib/firmware/

Some more pictures of the Pi desktop, but they really don’t do it justice. The 193 in particular is stunning IRL due to the higher resolution.

192…
View attachment 530313

193…
View attachment 530314

The pictures have what look like interference, but I assure you they’re not there in real life. Just moiré lines introduced by the digital camera taking a picture of another screen.

Looks great! I’ve been very happy with the performance of my 3B+ under normal use in the TT, but I think running the latest version of react-CarPlay on a pi 4 or 5 should be better as there are a couple of bug fixes, particularly around audio handling. I’m currently on holiday, but will try your custom EDID on my pi 5 when I get back. I’ve got my sync combiner in an off the shelf VGA connector breakout box, which will hopefully reduce the rework if the £5 HDMI to VGA adapter fails in the future. And yes, soldering VGA pins is a bit of a pain…

 

[TT'sRevenge]

The side with the plug has a square PCB with the QFN40 square chip on it. That’s the circuit board and chip that came with the HDMI to VGA, less the VGA plug. The rectangular board on the other side with THE 5 pin JST plug and a 14 pin SOIC is the quad 74HC86 which does the sync combine.

Yes there’s a 3.5mm plug for audio. Not sure where that is going yet. Really all I want to do was get the sync combine built and tested. I’m not so interested in getting a AA system together, it’s more about building the hardware for me. Perhaps if I can simplify the build process these might be available for sale. They’re not expensive to make after all.
...
The 640x480 EDID wasn't for RNSE, it was for VGA signals for gaming from Pi. But it’s all I could find as a starting point as nobody had shared their EDID yet. RNSE is definitely is expecting 800x480 NTSC video, although in analogue world there really isn’t a horizontal resolution as such. The LCD/LED panel it ends up on is 400/800 pixels though, so we should target that for best results.

RNSE wants interlaced 525 line (480 active) NTSC signal. If it doesn’t get that you likely won’t get a stable image. So I crafted my own EDID to ensure there are 525 lines total, 480 active, 15.75khz line frequency, 3 lines of v sync, etc.

Ohhh okay this now clears up a lot!

The Extron is presumably designed for AV use, not the RNSE, and we don’t 100% know what voltage level the designers intended for the RNSE sync signal. But I find it hard to believe they expected 5v into a 75ohm impedance, which results in 60mA being sinked! The limiting factor I’m my circuit is the current that the XOR gate could provide, and I was driving it past its limit. As a result voltage was pulled down to 3v from a 5v logic high, and that’s not good for logic gates.

Indeed the Extron is for AV/PC use, as is the RGB2SCART; and I at least thought pretty much every other sync combine thing that had been discussed before, was the same. I didn't really realise the RNS-E wouldn't use that well...it's another thing to "convert" I guess, but very good to know ahead of time. I wonder if that's why @Karmannsport was having issues at first? But I don't think he said what he did to fix it after, just that he had fixed it.

So what I’m saying is a 150ohm resistor in the output from a 5v sync would be a better design. That “corrects” for the fact that our sync signals are 5v, whereas the RNS510 combiner has 3v sync. What I am aiming for is that the end result is the same, about 1.5v presented to the RNSE with it sinking 20mA from both circuits. 5v into 150ohm (+75ohm at RNSE) is same as 3v into 75ohm (+ another 75ohm at RNSE) = 1.5v and 20mA.

So in my case I'm going to have leads going from BNC to wires--BNC on the Extron side and then wires into the AMP connector on the RNS-E. Would I just need to insert a 150 Ohm resistor in series on the "S" wire/signal, before it goes into the RNS-E? Or am I not understanding or missing something still?

 

[pcbbc]

Yep. Just pass the signal through a suitable resistor and into the RNSE. You should then have 5v (or whatever your combiner outputs) on one side, and 1.5v on the other before going into RNSE.

The RNSE acts like a 75ohms to earth (input impedance), so it's a voltage divider and you can easily calculate voltages, or the resistor needed, to achieve any desired voltage on the input...
5v -> 150 ohm -> CSYNC IN -> 75ohm -> earth

And also the current draw via ohms law V = I / R

 

[pcbbc]

Okay, to heck with it. 😉

Today I made up the rest of my HDMI to VGA adapters that I got from AliExpress last year. All now have integrated sync combiners and output RGBS suitable for direct input to RNSE.

If anyone would like one, drop me a PM or an e-mail. 😊

You’ll need to make up your own cable, 5 pin JST XH plug to 32 pin grey connector. I could make you one, but don’t currently have those parts in. Plus you’ll have to tell me how long you want it, if you need the 32 pin plug, 3.5mm audio, etc.

 

[Karmannsport]

Okay, to heck with it. 😉

Today I made up the rest of my HDMI to VGA adapters that I got from AliExpress last year. All now have integrated sync combiners and output RGBS suitable for direct input to RNSE.

If anyone would like one, drop me a PM or an e-mail. 😊

You’ll need to make up your own cable, 5 pin JST XH plug to 32 pin grey connector. I could make you one, but don’t currently have those parts in. Plus you’ll have to tell me how long you want it, if you need the 32 pin plug, 3.5mm audio, etc.

View attachment 530432

View attachment 530431

I emailed you! I absolutely want one. Saves me from having to transfer my bread board!

 

[TT'sRevenge]

Yep. Just pass the signal through a suitable resistor and into the RNSE. You should then have 5v (or whatever your combiner outputs) on one side, and 1.5v on the other before going into RNSE.

The RNSE acts like a 75ohms to earth (input impedance), so it's a voltage divider and you can easily calculate voltages, or the resistor needed, to achieve any desired voltage on the input...
5v -> 150 ohm -> CSYNC IN -> 75ohm -> earth

Great thanks! Those pre-made adapters look good, I will try via what equipment I have first as I think buying one from you will end up being more just to ship it here than you're asking for one; but really cool you have them for sale already!

And also the current draw via ohms law V = I / R

Haha yeah I know that one very well, it just escaped me I'd need to apply this to anything I/O and video signal-related. But this is not exactly plugging in a VGA/HDMI/RCA cable we're talking about of course!

 

[Karmannsport]

Alright…well I’ve come far enough along that I can say with confidence that my goal for this project will be achieved. I am now running Android 15 on a raspberry pi 5 displaying on my rns-e with touch screen. This means the carlinkit carplay dongle works with native software. I also did not require a custom edid.bin file for this. I will post everything up when I’m 100% satisfied but this gives the option of closing out of CarPlay and having Netflix, YouTube, plex, obd2 apps, whatever navigation software you want…I mean full access to the google play store and side loading of apps. This brings the best of rns-e copycat Chinese android head units and the quality and factory features of the rns-e.

 

[ltl_nmo]

@pcbbc you are a hero. With this edid i should be able to use it in Konstakang’s Lineage Android OS now instead of React or Openauto. If you get a chance to try it out before I get to it that would be awesome.

Any change of getting that adapter but to standard hdmi instead of micro? Im using an adapter pcb off the pi that goes micro to standard so i can fit it in a nice case. If not that’s fine but i definitely want one either way.

 

[ltl_nmo]

Alright…well I’ve come far enough along that I can say with confidence that my goal for this project will be achieved. I am now running Android 15 on a raspberry pi 5 displaying on my rns-e with touch screen. This means the carlinkit carplay dongle works with native software. I also did not require a custom edid.bin file for this. I will post everything up when I’m 100% satisfied but this gives the option of closing out of CarPlay and having Netflix, YouTube, plex, obd2 apps, whatever navigation software you want…I mean full access to the google play store and side loading of apps. This brings the best of rns-e copycat Chinese android head units and the quality and factory features of the rns-e.

View attachment 530460

Bro. Please post soon and which sync combining you are using etc. this is amazing. You even have it themed for RNSE

 

[pcbbc]

@pcbbc you are a hero. With this edid i should be able to use it in Konstakang’s Lineage Android OS now instead of React or Openauto. If you get a chance to try it out before I get to it that would be awesome.

Sorry, I have to say I’ve only the very vaguest of ideas what you are taking about…
If you tell me where to go, what to download and do, I’m happy to try it.

Sorry if this is basic stuff, but really I’ve only been dabbling around the edges of Pi stuff as a passing interest due to my involvement in the RNSE firmware project.

Any change of getting that adapter but to standard hdmi instead of micro? Im using an adapter pcb off the pi that goes micro to standard so i can fit it in a nice case. If not that’s fine but i definitely want one either way.

Probably. I’d need to get a full size HDMI to VGA adapter of the same appareance. And we’d be taking a chance that it uses the same internal circuit board design and VGA socket such that my piggyback sync board can still solder in place. Do you want me to give it a go?

 

[ltl_nmo]

Sorry, I have to say I’ve only the very vaguest of ideas what you are taking about…
If you tell me where to go, what to download and do, I’m happy to try it.

Sorry if this is basic stuff, but really I’ve only been dabbling around the edges of Pi stuff as a passing interest due to my involvement in the RNSE firmware project.


Probably. I’d need to get a full size HDMI to VGA adapter of the same appareance. And we’d be taking a chance that it uses the same internal circuit board design and VGA socket such that my piggyback sync board can still solder in place. Do you want me to give it a go?

This is a link to the pi firmware for LineageOS (Android). Instructions are in there. Raspberry

As for the full size hdmi. I’m going to run hdmi wire all the way to the back where the R8 RVC module is so it’s digital and not analog for interference. So if the current version allows soldering of an hdmi wire to it where you currently solder the small wire of micro hdmi then it should be fine. Just some custom bit I would need to do

 

[TT'sRevenge]

With this edid i should be able to use it in Konstakang’s Lineage Android OS now instead of React or Openauto. If you get a chance to try it out before I get to it that would be awesome.

But then you'll be using straight Android right, and not Android Auto? Like making your RNS-E into a standalone tablet or phone. I guess that does have its advantages (and disadvantages). I'm guessing you plan on hot spotting your phone for internet connection?

I guess that's also the reason you'd really need touch...which brings me back to the same question BTW, lol:

Out of curiosity, what touch digitiser are you using/where did you get it?

 

[Karmannsport]

Bro. Please post soon and which sync combining you are using etc. this is amazing. You even have it themed for RNSE

I am using the same sync combining circuit that pcbbc is using. I would imagine it’s the same sync combining circuit that everyone here is using as it’s the only one I’ve found that works with the rns-e. Mines currently on a breadboard but I could fancy it up if pcbbc hadn’t already done it above. The man is brilliant! It’s a very simple circuit to build.

To get Android to work, you need to install KonstaKang’s port of Lineage 22 (Android 15) onto the pi 5. From there, the only bit of coding that needs to be added to cmdline.txt in the /root directory is:

video=HDMI-A-1:800x480M@30i,margin_left=0,margin_right=0,margin_top=0,magin_bottom=0

You can change the margin numbers to account for overscan to get the picture perfectly on screen. 1 moves the picture in 1 pixel, 2 moves 2 pixels, so on so forth. If you use your phones camera to zoom in on the rns-e screen, you can count the individual pixels to get a perfect picture. Just set them all at 25 first and work your way back.

You also need to set 800x480 as the resolution in the resolution.txt file also found in /boot.

As for the touchscreen, this 6.5” one is the one I used for the rns-e. You just remove the screen bezel, and overlay it over the screen. Some clearencing on the bezel to allow it to lock in place smoother is definitely recommended but not required. I got it to fit between the screen and the bezel without modifying it. The touch screen fits the rns screen like it was designed for it. I didn’t even have to calibrate anything, it works perfect out of the box.

https://a.aliexpress.com/_mPgr6WT

As for Android 15, just follow all of konstakangs recommendations for things like the gps dongle and everything just works. It really really is awesome.

The rns-e background is a quick and dirty photoshop I did from a picture of the media screen but I will clean it up to get it perfect so you see no difference when swapping from any other source to the media button.

Still have to sort out canbus but even without it I’m 100% happy. CarPlay and Android are made for touch interface and I feel it’s clunky to use them without it.

 

[Karmannsport]

This is a link to the pi firmware for LineageOS (Android). Instructions are in there. Raspberry

As for the full size hdmi. I’m going to run hdmi wire all the way to the back where the R8 RVC module is so it’s digital and not analog for interference. So if the current version allows soldering of an hdmi wire to it where you currently solder the small wire of micro hdmi then it should be fine. Just some custom bit I would need to do

This is what I did. I replied to your other post.

Also note, that you can’t use the R8 RVC and TV tuner as there is only one port on the rns-e. I have a parts list together to build an RGB switching circuit to change from tv input to RVC module input when put in reverse, but haven’t gotten that far yet.

 

[MT-V6]

As for the full size hdmi. I’m going to run hdmi wire all the way to the back where the R8 RVC module is so it’s digital and not analog for interference.

Are you using the R8 RVC for the reverse camera as well as a secondary input (Pi?)

I've heard it is possible but I couldn't find much info on it. Pins, coding etc

 

[Karmannsport]

Are you using the R8 RVC for the reverse camera as well as a secondary input (Pi?)

I've heard it is possible but I couldn't find much info on it. Pins, coding etc

This is not possible. Elsewhere in the thread I posted that you will need a device that switches RGB sources from the pi to the RVC module when the car is put in reverse. I have a parts list together to build one but haven’t gotten that far yet.

 

[Karmannsport]

But then you'll be using straight Android right, and not Android Auto? Like making your RNS-E into a standalone tablet or phone. I guess that does have its advantages (and disadvantages). I'm guessing you plan on hot spotting your phone for internet connection?

I guess that's also the reason you'd really need touch...which brings me back to the same question BTW, lol:

This is the capacitive touch screen digitizer I used. It fits the rns-e screen absolutely perfectly.


I just found this on AliExpress: $14.60 | 3.5/4.3/5/6.2/7/8/9/10.1 Inch Raspberry Pi Industrial Equipment PC Car Capacitive Digitizer Touch Screen Panel USB Driver Board

https://a.aliexpress.com/_m0MeMKx

This is the setup I built. It loads CarPlay or AA automatically by default, but when you exit out of it instead of going to pi OS, it goes to Android 15. Then you basically have an Android tablet and can add whatever Android apps you want. I’m not familiar with Android auto so I don’t know if it’s content locked like CarPlay is, but it’s cool to be able to use CarPlay and then also have the ability to load obd2 apps or YouTube or plex if you want.

 

[Karmannsport]

@pcbbc you are a hero. With this edid i should be able to use it in Konstakang’s Lineage Android OS now instead of React or Openauto. If you get a chance to try it out before I get to it that would be awesome.

Any change of getting that adapter but to standard hdmi instead of micro? Im using an adapter pcb off the pi that goes micro to standard so i can fit it in a nice case. If not that’s fine but i definitely want one either way.

Lineage did not require a custom edid. It worked with cmdline modification.

 

[pcbbc]

Lineage did not require a custom edid. It worked with cmdline modification.

But is it outputting NTSC or the VGA timing version of 800x480i?

Because when I used VGA there was some nasty flickering artefacts about half way down the Pi desktop image. Only when I crafted my custom EDID, which forces NTSC timings, did those go away.

This is not possible. Elsewhere in the thread I posted that you will need a device that switches RGB sources from the pi to the RVC module when the car is put in reverse. I have a parts list together to build one but haven’t gotten that far yet.

If I do another spin of my sync combiner it’s probably going to include a video switch and maybe and audio amp.

 

[Karmannsport]

But is it outputting NTSC or the VGA timing version of 800x480i?

Because when I used VGA there was some nasty flickering artefacts about half way down the Pi desktop image. Only when I crafted my custom EDID, which forces NTSC timings, did those go away.


If I do another spin of my sync combiner it’s probably going to include a video switch and maybe and audio amp.

I don’t have any artifacts. I’m not sure if this is a Lineage thing over pi os thing. I needed the custom edid for pi os to work (modified a 480i edid from 640x480 to 800x480). The cmd line modifications did not work in piOS. For some reason on lineage they work. I’ll try and post up a video of it all in action tonight while I’m tinkering.