Jump to content

My iPad Mini install in 2014 Sliverado


Recommended Posts

Posted

This is my third install of my iPad mini (64GB with Verizon service). I had it in my 2011 RAM and also on my boat.

I use RAM Mount components and they work great. As my Chevy does not have the center console I used the "ashtray" compartment under the radio to mount the iPad Mini.

 

You can get all the parts on RamMounts website, and in my case I used:

- 1" ball with diamond base (two screw holes)

- 3.5" extension

- Ipad mini X-Grip mount (work with or without case - OtterBox Defender in my case)

 

I took maybe 30 minutes to do it...I pulled out the compartment tray/ashtray out and went to the hardware store as I needed 2 screws, washers, and nuts. One screw is facing out, one in...One screw did not have enough clearance to accommodate the nut and still keep the tray latched. Not a big deal, unless you look closely.

 

Went to BestBuy and found a coiled 3 foot iPad charging cord, which is only 1 foot long and it works great (not on the pictures)

 

Now, I have the iPad paired up with the head unit for music and I can use Google Maps or iPad built in navigation. I have used it for 4500 miles so far and the mount is holding up well.

On the boat I used the larger base with the 1.5"ball as I wanted to make sure it is strong enough to sustain boat/waves movement. It works great for music, weather forecast, and navigation.
Let me know if you have any questions or need help with the install...

 

P.S. One key difference between the iPad Mini Wi-Fi and 4G is the GPS receiver. The Wi-Fi version does not have one. In other words, you can not use the Wi-Fi version for navigation. If you do not want to pay extra monthly service you can download navigation maps locally on the iPad (tom-tom maps are not free, but there are some free ones)

post-125122-0-51169500-1391488490_thumb.jpg

post-125122-0-73444200-1391488499_thumb.jpg

post-125122-0-10404100-1391488509_thumb.jpg

post-125122-0-79069000-1391488731_thumb.jpg

post-125122-0-51169500-1391488490_thumb.jpg

post-125122-0-73444200-1391488499_thumb.jpg

post-125122-0-10404100-1391488509_thumb.jpg

post-125122-0-79069000-1391488731_thumb.jpg

post-125122-0-51169500-1391488490_thumb.jpg

post-125122-0-73444200-1391488499_thumb.jpg

post-125122-0-10404100-1391488509_thumb.jpg

post-125122-0-79069000-1391488731_thumb.jpg

post-125122-0-51169500-1391488490_thumb.jpg

post-125122-0-73444200-1391488499_thumb.jpg

post-125122-0-10404100-1391488509_thumb.jpg

post-125122-0-79069000-1391488731_thumb.jpg

Posted

Thanks...I love the portability of the iPad mini...winter months are cold in Michigan, so It takes no time to pull the iPad with me every night. Also, in the summer time it is very easy to move it from the truck onto the boat...RAM MOUNTs are really versatile and well built...

Posted

I had the Ram setup for my Xoom. It mounted to the seat bolt. They make a great product.

2013-02-01_13-01-08_137_zps428e58e8.jpg

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...