Jump to content

Recommended Posts

Posted (edited)

Looking at purchasing a DSP in lieu of an Audiocontrol LOC (hated the LC7 I had in a previous car) and wanted to ask for recommendations. I was always an Alpine guy but it seems they are limited to amplifiers with built in DSP instead of standalone units. Looks like the JL audio Fix86 +/- JL audio TwK 88 (or D8) are the best options for adding a 2 channel (sub) and 4 channel (doors) amplifiers? Anyone running both the Fix86 w/ the TwK?

 

 

Edited by Goobax
Posted
2 hours ago, Goobax said:

Looking at purchasing a DSP in lieu of an Audiocontrol LOC (hated the LC7 I had in a previous car) and wanted to ask for recommendations. I was always an Alpine guy but it seems they are limited to amplifiers with built in DSP instead of standalone units. Looks like the JL audio Fix86 +/- JL audio TwK 88 (or D8) are the best options for adding a 2 channel (sub) and 4 channel (doors) amplifiers? Anyone running both the Fix86 w/ the TwK?

 

 

You could go with the Zen (https://navtv.com/products/NTV-KIT955/zen-avb-gm.html) and hook it straight to a JL Audio VXi amplifier. No need for a FIX or TwK.

Posted

That NavTV unit is only going to work on a factory Bose system.It replaces the stock amp basically.The I0R base system has completely different connectors and wiring configurations.

Posted (edited)
14 hours ago, Goobax said:

Looking at purchasing a DSP in lieu of an Audiocontrol LOC (hated the LC7 I had in a previous car) and wanted to ask for recommendations. I was always an Alpine guy but it seems they are limited to amplifiers with built in DSP instead of standalone units. Looks like the JL audio Fix86 +/- JL audio TwK 88 (or D8) are the best options for adding a 2 channel (sub) and 4 channel (doors) amplifiers? Anyone running both the Fix86 w/ the TwK?

 

 

I did the fix 82 in my Custom. I used it instead of of the 86 due to the fact that I dont care about fading. I also used the VXi amps and can control all my settings via bluetooth and ipad. No need to remove seats or panels to make an adjustments. Its the best sound I have ever had.

Edited by Zelas
spelling error
Posted
13 hours ago, Zelas said:

I did the fix 82 in my Custom. I used it instead of of the 86 due to the fact that I dont care about fading. I also used the VXi amps and can control all my settings via bluetooth and ipad. No need to remove seats or panels to make an adjustments. Its the best sound I have ever had.

Forgive my ignorance but what is gained by retaining the fix 82 when using the VXi line, shouldn't this be a redundancy given the VXi has DSP already in or do you need both for other reasons?

 

Thanks

Posted (edited)

Ok So after hours upon hours of audiophile research heres the deal, if you’re going to put a system into a BOSE 2019+ then you need the NAV TV Unit. Period. It converts the bus data signals to optical/digital or coax and allows the cleanest signal possible with no time alignment issues etc. If you choose to use a harness, (which none on the market to date have zero interference), or if your like me who figured out all of the wire connections on the amp and spliced from there, you are going to need a DSP since the issue with the bose amp is mainly some timing correction that cannot be altered with an LC7i. For the non bose, Im not entirely sure but again the NAV TV unit is without a doubt your best bet for the cleanest possible sound and best bang for your buck build for an audiophile grade signal. I have tried everything, I will also be making a color coated wiring diagram for all the speakers and amp input/output for those who are not going to to buy the NAV TV unit. Again, no matter what, you are going to need a DSP regardless if you have bose or not. Otherwise its not even worth the money upgrading. The whole issue is these newer trucks have converted the signal from

the head unit into BUS DATA which obviously is not able to be used by aftermarket amps or DSP’s. So the NAV TV unit essentially changes those pre amp bus data signals into digital or analog allowing you to actually bypass the bose amp or factory amp without losing all of your door chimes etc. If you dont use the nav tv unit you are going to have to tap into the amp post amp signal, and use a dsp to clean up the incoming signal as best you can, then have the dsp convert the signal to rca to be able to plug into your amp. Again you will need a dsp no matter what because the signal coming through has its own factory time alignment which will not suit any aftermarket system you install. As far as tapping into the truck, there is a wire cluster under the passenger rear sill panel, but its best to remove the rear seats and tap in there since its much easier to clean up the wiring mess. Currently Im waiting on my NAV TV unit so Im going to be soddering back all those wires I spliced and when the Nav Tv unit comes In Il install that and send a digital signal to my DSP then send the signal to my amp and finally have a truly worth your money audiophile grade sounding system. 

7109F749-94A9-474B-B4DD-C2F4E3B86B3D.png

8CB9D239-AE3F-440C-9FAA-A45283BB9ABF.png

894C6924-28F7-4EF7-BFE5-4DDFF9C95529.png

Edited by MrSavageTim
Posted
On 1/30/2020 at 8:09 PM, Goobax said:

Forgive my ignorance but what is gained by retaining the fix 82 when using the VXi line, shouldn't this be a redundancy given the VXi has DSP already in or do you need both for other reasons?

 

Thanks

The Fix is only to correct the signals from  and provide a flat baseline to then use whatever method you gonna go. Its the best option out there for Non bose units.

Posted
7 hours ago, Zelas said:

The Fix is only to correct the signals from  and provide a flat baseline to then use whatever method you gonna go. Its the best option out there for Non bose units.

The Fix86 is certainly a fine choice but by no means a "must" for Non-Bose systems.Many have ran their stock speaker signals straight into the speaker level inputs of a 4ch amplifier and used the RCA passthrough to feed signal to their mono bass amp yielding fantastic results.

Posted

So thought I’d post this here to let you guys know about a problem with the NavTv.  I have a 2020 AT4 and just had a new sound system installed.  I had factory Bose replaced with NavTv, Audison 5.9 bit 5ch amp with built in DSP, pushing Hertz speakers throughout with a Illusion Carbon 10” sub.  Sounds great, except there’s a software problem with the NavTv.  It randomly shuts off all sound from the head unit, including door chimes and blinker.  Once it’s off the unit (NavTv) has to be reset to get sound back.  Turning the truck off does not fix it when started back up.  Short term fix is a toggle switch my installer put under my dash until the next software update to correct the problem.  He called NavTv and they expect a software update to roll out in a few weeks to correct the problem.

Posted
5 hours ago, TNAT4 said:

So thought I’d post this here to let you guys know about a problem with the NavTv.  I have a 2020 AT4 and just had a new sound system installed.  I had factory Bose replaced with NavTv, Audison 5.9 bit 5ch amp with built in DSP, pushing Hertz speakers throughout with a Illusion Carbon 10” sub.  Sounds great, except there’s a software problem with the NavTv.  It randomly shuts off all sound from the head unit, including door chimes and blinker.  Once it’s off the unit (NavTv) has to be reset to get sound back.  Turning the truck off does not fix it when started back up.  Short term fix is a toggle switch my installer put under my dash until the next software update to correct the problem.  He called NavTv and they expect a software update to roll out in a few weeks to correct the problem.

I have different components, but have the same end results with the NAV-TV. I changed the amplifier turn on to "DC Offset" instead of relying on the NAV-TV remote wire. It almost seems like the blue remote wire is losing voltage which is causing the amp to shut off. Granted it has only been a day since I changed to DC Offset but so far seems to be working. Probably will make a fool out of me tomorrow, hehe.

 

It drives me up the wall that I spent $600 for a device that works intermittently, and has non-existent support resources.

 

Posted
5 hours ago, ArcherMP said:

I have different components, but have the same end results with the NAV-TV. I changed the amplifier turn on to "DC Offset" instead of relying on the NAV-TV remote wire. It almost seems like the blue remote wire is losing voltage which is causing the amp to shut off. Granted it has only been a day since I changed to DC Offset but so far seems to be working. Probably will make a fool out of me tomorrow, hehe.

 

It drives me up the wall that I spent $600 for a device that works intermittently, and has non-existent support resources.

 

My installer was told they'd have an update within 2 weeks or so.  They told him they need to get a 2020 truck in there to "play" with in order to figure out the software update.  Let me know if the DC Offset is a true solution because something tells me it will take them longer than 2 weeks to get the software update and its annoying having to hit the toggle button and wait for a bootup every couple days.  

Posted
3 hours ago, TNAT4 said:

My installer was told they'd have an update within 2 weeks or so.  They told him they need to get a 2020 truck in there to "play" with in order to figure out the software update.  Let me know if the DC Offset is a true solution because something tells me it will take them longer than 2 weeks to get the software update and its annoying having to hit the toggle button and wait for a bootup every couple days.  

Nope, didn't work, although I did not have to reboot the NAV-TV, only the JL VXi.

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

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...