Jump to content

Anyone know part number for trailer camera that plugs into ports on rear bumper?

Sunshine39
 Share

Recommended Posts

Gecko50 Enthusiast

Gecko50

Posted
Posted

2 more observations, it appears that there is a hex type of crimp made, which is common for coax. I also see it appears the ferrule appears to be threaded as it has a grip type exterior to assist in tightening without slipping on the connector. But why is the inside of the boot a small round metal, what was the mating part, was that lost on the cable destruction? 

 

Chuck 

  • Replies 144
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

tgodrich
tgodrich

OK, so I have a 2020 Chevy 3500HD.  I do not like having to string a cable from the rear of my 34' trailer to use the camera option.  From my understanding, the cable has a DC bias for the camera with

sdelam
sdelam
keithaz22
keithaz22

Fakra z connectors 

Posted Images

  • 3 weeks later...
kf9yr Enthusiast

kf9yr

Posted
Posted

It looks like that is coaxial cable, not triaxial.

They could send power and signal on the same cable. Just like they do with Direct TV satellite dishes. It makes aftermarket cameras more difficult...

If you know any Ham Radio operators one of them could probably crimp or solder a different connector (maybe a SMA)?

You would need to do this on both the truck end and camera end.

Search for RG58 SMA connector on You Tube there is a video that shows how to install a crimp on connector if you have the Hex crimper.

If you were in Phoenix I could install the connectors in a few minutes, there is bound to be someone that could do it in your area.

When I have time I will see how much extra coax there is under the truck. If there’s a little slack it would be easy to cut the coax and put connectors on both ends. I could add a set of camera jacks in the bed for a fifth wheel or gooseneck.




Sent from my iPad using Tapatalk Pro

hogcard Enthusiast

hogcard

Posted
Posted

I currently have a furrion wireless camera on the back of my fifth wheel with extra monitor.  Would love to be able to use the gmc screen so I wouldn't have to have an extra screen sitting there.  However the GMC camera is a "wired" camera.  How do you run the wiring from the back of your camping trailer to the plug without it looking cheesy? 

hptulsa Enthusiast

hptulsa

Posted
Posted

i found a 'hole' at the front of my horse trailer where the manufacturer had run the wires for the brakes/lights.  There is a track all the way to the back of the trailer so i used it for my camera cable also...at the front, it drops directly down around the gooseneck hitch, so i cable clamped it backwards to just over the trucks connection.  CAUTION! i did not allow for a sharp turn of the gooseneck and the first time i did that the camera cables ripped out of the truck connection and i will have to get new connectors which have been difficult to find!! 

 

Could you also cable clamp the wiring underneath your trailer to the rear? i used self tapping metal screws and it was fairly easy...

hptulsa Enthusiast

hptulsa

Posted
Posted

I agree it looks like 'mini' coax and seems to have the same type of termination, but when i was researching the type of camera/connectors, i found a site that said the cameras were using triaxial.. i will look back to see if i can find that again.  

kf9yr Enthusiast

kf9yr

Posted
Posted

I looked under my truck today.

The camera cable is RG-58, 50 ohm coax.

0439423b5b04dc8ea8149c593096f251.jpg

If I had damage to the connector I would just replace it with a compression F connector. Direct TV uses these outdoors in all US climate zones.

Put in a splitter and you can have jacks for your 5th wheel and on your bumper. I would cut off the camera plug and replace wi a F connector as well.

0b4195921ae6ed514f524b612c0efb26.jpga9eb68568b20b55a3edf477e8794465e.jpg


Sent from my iPad using Tapatalk Pro

  • 2 weeks later...
Strick 8187 Enthusiast

Strick 8187

Posted
Posted

Not sure if this has been said but dealer ran my vin and this P/N 84876818 is what came up replaces 84580657. 

yousaveone Enthusiast

yousaveone

Posted
Posted
On 1/15/2020 at 8:19 PM, kf9yr said:

I looked under my truck today.

The camera cable is RG-58, 50 ohm coax.

0439423b5b04dc8ea8149c593096f251.jpg

If I had damage to the connector I would just replace it with a compression F connector. Direct TV uses these outdoors in all US climate zones.

Put in a splitter and you can have jacks for your 5th wheel and on your bumper. I would cut off the camera plug and replace wi a F connector as well.

0b4195921ae6ed514f524b612c0efb26.jpga9eb68568b20b55a3edf477e8794465e.jpg


Sent from my iPad using Tapatalk Pro

WRONG. RG-58 is a standard in radio and GPS. we commonly use it in aircraft. Directv does NOT use this. They use RG-6 and sometimes RG-59 if the installer is lazy. In addition you cannot use a splitter in this application. If you listen to this guy your camera will be damaged at the least.

kf9yr Enthusiast

kf9yr

Posted
Posted

I didn’t say Direct TV uses RG59 or RG58. I said they use F-connectors...

 

They use RG6 because it is lower loss at the microwave frequencies they are using than RG59.

 

RG58 is 50 ohm RG59 is 75 ohm. At the signal levels used here they would be interchangeable but I didn’t suggest that.

 

Putting a splitter won’t damage your camera. Even if you were so incompetent that you inverted the signal and ground it wouldn’t hurt the camera. The voltage that powers the camera is supplied by the truck. I would put a 50 ohm terminating cap resistor on the unused terminal.

 

It wouldn’t be a good idea to ground the unused terminal.

 

I will order a camera.

 

 

 

 

Sent from my iPad using Tapatalk Pro

 

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...