Jump to content
SAU Community

Recommended Posts

On 3/22/2019 at 12:03 AM, The Max said:

Much easier than that. As the NUC output is converted to composite, it'll feed the auxiliary input of the infotainment system, as per your first sentence.

As for the touch overlay, I've decided not to bother with a switch. I'm just going to permanently connect it to the USB converter for the NUC (based on Microchip's discontinued AR1100 IC).

Now I actually have a driver for a screen (ar1100 based off memory) and touch interface board for another project at work but reprogramming the board to suit the v36 screen is a big learning curve for me.

What are you programming that interface into? It should just appear as a regular HID/mouse.

If you're using it in a Windows environment, you will need the appropriate UPD drivers which give you the ability to tailor how it performs (as in if it's just x,y or x,y and left click simultaneously, etc). They were free up until a certain version but I'm not home yet to tell you what that version is.

I'm sure I have them on file and can share them on Dropbox if need be.

23 minutes ago, The Max said:

What are you programming that interface into? It should just appear as a regular HID/mouse.

If you're using it in a Windows environment, you will need the appropriate UPD drivers which give you the ability to tailor how it performs (as in if it's just x,y or x,y and left click simultaneously, etc). They were free up until a certain version but I'm not home yet to tell you what that version is.

I'm sure I have them on file and can share them on Dropbox if need be.

I had thought that the driver for the screen (not the touch as I have the windows software to calibrate the touch panel) needed to be programmed for the screen that attaches to it... 

But I think I'm just being silly as you're using the aux input so no screen driver is needed. Hmm let's blame that on waking up too early on a Saturday. 

47 minutes ago, The Max said:

What are you programming that interface into? It should just appear as a regular HID/mouse.

If you're using it in a Windows environment, you will need the appropriate UPD drivers which give you the ability to tailor how it performs (as in if it's just x,y or x,y and left click simultaneously, etc). They were free up until a certain version but I'm not home yet to tell you what that version is.

I'm sure I have them on file and can share them on Dropbox if need be.

How hard was it to connect the v36 touch panel to your usb touch board? Is the ribbon cable hard to get to?

Does the touch panel have a fairly standard 4 wire 1mm pitch FPC cable so most ar1100 boards j at work? 

I'm now contemplating an android box plus external gps and the ar1100 for touch. Then installing an app that makes it possible to use the box like an android auto head unit, or just using it android unit.. Perhaps adding an external mic for Google assistant.

It won't really suit split screen on the small screen like the phoenix screen does but I think it'll tick a lot of other boxes for me at a fraction of the cost. 

So thanks for getting me thinking about this option 

 

Edited by Pete_Repeat

touch panel is 4 wire resistive. split the screen and grab the header. its spat out of the coms lines in serial format if you want to play there.

 

 

  • Like 1
2 minutes ago, Chris Rogers said:

touch panel is 4 wire resistive. split the screen and grab the header. its spat out of the coms lines in serial format if you want to play there.

 

 

Thanks Chris. That's great to know 

tony has it btw. ( I no longer do this for a living.)

 

all the CHEAP $5 ideas won't work on the JDM version. been saying for years to no avail.
get custom OR get teh controller out of a USDM version IDENTICAL in features to yours. from there its a software reload ex NZ and you are set. naturally this works on the later 2011 versions and NOT the earlier ones as they are a different unit.

On 2/17/2018 at 5:21 AM, Wogboy said:

if you are refering to chris rogers, he has moved back to the U.S.A.

 

exactly and I do not do this for a living any more.

26 minutes ago, Chris Rogers said:

tony has it btw. ( I no longer do this for a living.)

 

all the CHEAP $5 ideas won't work on the JDM version. been saying for years to no avail.
get custom OR get teh controller out of a USDM version IDENTICAL in features to yours. from there its a software reload ex NZ and you are set. naturally this works on the later 2011 versions and NOT the earlier ones as they are a different unit.

So you're saying something like below will or won't work? It's 4 wire resistive so was hoping (ar1100 based). I have something similar at work already but as I've have never pulled the dash apart I'm wanting to have some degree of confidence before I pull it apart that I have a possible solution waiting. 

http://vi.raptor.ebaydesc.com/ws/eBayISAPI.dll?ViewItemDescV4&item=163582810627&category=42889&pm=1&ds=0&t=1553895682862&cspheader=1&oversion=efed4d47

 

I already have the video input. Currently using wireless display from android. But will likely move to a dedicated Android box in the car if the touch may work.

Edited by Pete_Repeat

Hmm so now the difficulty. This is more for other people's info and to help me think it through... But happy for feedback still, as I may have missed something.

Do I stay using the aux in for video but move to dedicated box and take over the touch panel with the ar1100 based board. Run it all into the centre console. Would be the cheapest option (other than the screen mirroring of my phone that I'm alresdy doing). I guess it's about $200 of bits (android box + gps + ar1100 + 5V 3A power + external mic). It's not a great screen in my 2009 but it's ok for a car. Still a single point resistive touch, however some apps can simulate pinch to zoom but not in full. Unlikely to need pinch to zoom in the car anyway. Could look into external mic for google assistant. I can't see Bluetooth in my car for the past few weeks so I suspect hands free will be missing from this option. Also this could be a bit of effort to get right.

Or now Phoenix are saying a 30 day money back policy.. Which I believe will cover their system if it doesn't work as hoped. I will need to return in new condition however. This ticks a lot of boxes for me... If it works. I want android. I want a larger screen. This is still a tempting job expect for the following. Concerns the screen isn't too viewable in sunlight. Concerns the relatively low res for the bigger screen isn't great pic. Although reports seem to say the screen is decent... Concerns that it doesn't function as expected so there is a lot of effort wasted time. Then the concern that phoenix make the return difficult. Plus the cost is around $750. But it ticks all my boxes if it comes off. 

Reason android is such a strong thing for me is that it will tie in with home automation running on tasker + home assistant + ifttt. So the gates can be opened from a widget on the car screen. I can automate my hotspot to turn on automatically and use Google music and maps on the car which is a big thing for me. I can get my calls and text to show on an android screen reliably. Plus naughty things like emails etc. And video when parked only of course.

 

Or stick with screen mirroring wirelessly when I put my phone in the 3d printed wireless charge dock and rely on voice to get things happening, with some automation based on location and time of day.. By far the cheapest as I have it running already. But it's been like this for a bit now so it's nothing exciting. It takes its toll on the phone I would imagine as it gets quite warm even though my custom wireless charger dock has fans on it. If I wasn't wireless charging heat isn't as big a problem but that's not as sexy as just dropping the phone in the dock. 

Edited by Pete_Repeat

look into the chipset I gave you. if you can fidn somethihng that spits out HDMI or similar then you can get evaluation kits for these chips.

 

that wil give you the full resolution you are looking for.

the other option is with Grom Audio and their Vlink system. in your case you would look at 2011 on for the digital screen

  • Thanks 1

Thanks Chris. I've had a look. That's option 3 for an Android option. Seems like about $AU850 for a system for a non-us nav system.

Might sit on it and think for a bit. Do things myself = cheap but effort which is best spent elsewhere at the moment. Buy the phoenix which works well for me with split screen and ability to change the launcher I believe but some element of risk. Buy the vlink system which is likely more reliable and less risky, but uses the low res screen in the 2009 plus its the most expensive but not by a lot.. I'll need to see the restrictions on the phoenix and the vtek system. As both are running android with a big skin change so customising might be limited on these systems. Hmm time to ponder ?

  • 1 month later...
On 9/2/2018 at 7:31 PM, DashyyPC said:

Okay hi and hello!

it is possible for a conversion Via Xanavi.
I've done this. Comes with complete unit with upgraded software and AUS maps.

Cost $1100 Shipped. It IS a stock unit replacement. Works perfectly fine.

http://xanavi.biz/


Completed on

07 Base model (with nav)
07 type S (with nav)

Photo's attached.

 

40525824_748746598803570_976320545408679936_n.jpg

40537821_1939938919632749_6138200460093292544_n.jpg

40581417_2017906491608479_3014551662896349184_n.jpg

Sorry but did u say we can order a English unit with full functionality for $1100 for the 36, 2007 models that came with factory nav? Its been a long night my brains not fully comprehending after all this reading. If so who installs it? Do voice calls work? And voice prompts , air cleaner ionizer?

9 hours ago, Regan9415 said:

Sorry but did u say we can order a English unit with full functionality for $1100 for the 36, 2007 models that came with factory nav? Its been a long night my brains not fully comprehending after all this reading. If so who installs it? Do voice calls work? And voice prompts , air cleaner ionizer?

Hey Mate,

 

You can buy it for any v36. You can buy it with or without nav. They do support the 2 options.
Everything still works as is. its made by the company who made the original headunits so its literally plug and play. They supply everything. Only takes 1 hour to do if you havent done it before. Super simple.

8 hours ago, DashyyPC said:

Hey Mate,

 

You can buy it for any v36. You can buy it with or without nav. They do support the 2 options.
Everything still works as is. its made by the company who made the original headunits so its literally plug and play. They supply everything. Only takes 1 hour to do if you havent done it before. Super simple.

Thanks mate. After reading all the drama n being so late it was hard for my brain to comprehend. Great to know we dont have to stick with the people keeping the other knowledge for financial gains.

  • 2 weeks later...

I recently bought an adaptor from AliExpress which enables me to display whats on my Android smartphone on my cars entertainment screen via the AUX input. I have a 2010 Skyline Crossover 370 GT. Here's the link to what I bought: https://www.aliexpress.com/snapshot/0.html?spm=a2g0s.9042647.6.2.14f64c4dJ3HCeU&orderId=100437840654111&productId=32837465703

The mirroring from my phone to the screen works great but with one major problem. It only works as long as the parking brake is deployed. It's a safety feature of the car that the AUX gets disabled as soon as the parking brake is released. This of course makes it useless for navigation purposes or doing anything else while driving. 

My question is, is there any way to disable this feature so the AUX input can still work while the car is driving?

 

 

9 hours ago, JmanNZ said:

I recently bought an adaptor from AliExpress which enables me to display whats on my Android smartphone on my cars entertainment screen via the AUX input. I have a 2010 Skyline Crossover 370 GT. Here's the link to what I bought: https://www.aliexpress.com/snapshot/0.html?spm=a2g0s.9042647.6.2.14f64c4dJ3HCeU&orderId=100437840654111&productId=32837465703

The mirroring from my phone to the screen works great but with one major problem. It only works as long as the parking brake is deployed. It's a safety feature of the car that the AUX gets disabled as soon as the parking brake is released. This of course makes it useless for navigation purposes or doing anything else while driving. 

My question is, is there any way to disable this feature so the AUX input can still work while the car is driving?

 

 

You need something like this

https://www.ebay.com.au/itm/Skyline-2010-V36-370GT-Navi-and-Video-in-Motion-Control-Bypass-Module-/202507314288

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • I've got the rear ones, they're certainly beefy. I need to take them to my driveshaft guru to check over, he's very fussy about the quality of components so I'll let you know if they are made of cheese by a blind man.   Are you in Australia? A mate just had a set of EN26 shafts made for his K20 Lotus by our fabricator which were quite cheap (compared to Driveshaft Shop) so if you can procure the CV's and draw what you need he'd make them for ~$800 for the pair.
    • Had I known the diff between R32 and R33 suspension I would have R33 suspension. That ship has sailed so I'm doing my best to replicate a drop spindle without spending $4k on a Billet one.
    • OEM suspension starts to bind as soon as the car gets away from stock height. I locked in the caster and camber before cutting off the kingpin. I then let the upright down in a natural (unbound) state before re-attaching it. Now it moves freely in bump and droop relative to the new ride height. My plan is to add GKTech arms before the car is finished so I can dial camber and caster further. It will be fine. This isn't rocket science. Caster looks good, camber is good, upper arm doesn't cause crazy gain and it is now closer to the stock angle and bump steer checks out. Send it.
    • Pay careful attention to the kinematics of that upper arm. The bloody things don't work properly even on a normal stock height R32. Nissan really screwed the pooch on that one. The fixes have included changing the hole locations on the bracket to change the angle of the inner pivot (which was fairly successful but usually makes it impossible to install or remove the arm without unbolting the bracket from the tower, which sucks) and various swivelling upper arm designs. ALL the swivelling upper arm designs that look like a capital I (with serifs) suck. All of them. Some of them are in fact terribly unsafe. Even the best one of them (the old UAS design) shat itself in short order on my car. The only upper arm that works as advertised and is pretty safe is the GKTech one. But it is high maintenance on a street car. I'm guessing that a 600HP car as (stupidly, IMO) low as you are going is not going to be a regular driver. So the maintenance issues on suspension parts are probably not going to be a problem. But you really must make sure that however your fairly drastically modded suspension ends up, that the upper arms swing through an arc that wants to keep the inner and outer bolts parallel. If the outer end travels through an arc that makes that end's bolt want to skew away from parallel with the inner bolt, you will build up enormous binding and compressing forces in the bushes, chew them out and hate life. The suspension compliance can actually be dominated by the bush binding, not the spring rate! It may be the case that even something like the GKTech arm won't work if your suspension kinematics become too weird, courtesy of all the cut and shut going on. Although you at least say there's no binding now, so maybe you're OK. Seeing as you're in the build phase, you could consider using R33/4 type upper arms (either that actual arm, OEM or aftermarket) or any similar wishbone designed to suit your available space, so alleviate the silliness of the R32 design. Then you can locate your inner pivots to provide the correct kinematics (camber gain on compression, etc).
    • The frontend wouldn't go low enough because the coilover was max low and the upper control arm would collapse into itself and potentially bottom out in the strut tower. I made a brace and cut off the kingpin and then moved the upright down 1.25" and welded. i still have to finish but this gives an idea. Now I can have a normal 3.25" of shock travel and things aren't binding. I'm also dropping the lower arm and tie rod 1.25".
×
×
  • Create New...