Jump to content

Factory XM RADIO MODULE FOR SALE

pacethis

By pacethis
in Classifieds (Buy/Sell/Trade)

Recommended Posts

99-2door Senior Enthusiast

99-2door

Posted
Posted
dude thouse wires are snipped kinda close.....did you rack up a big xm bill and not pay? cause whoever bought this would have a hard time activating it.

:sigh: WTF?

Looks like plenty of wire left to make connections.

From my experience, the XM bill is pre-paid. ie you pay before you get the service.

I don't think pacethis is the seller, he is just trying to make people aware of the item, but.....

Why would you say that anyway?

Quit crapping on threads....If you don't like what's for sell, just move on.

We don't need your opinion listed on every item that is posted.

lrymal Senior Enthusiast

lrymal

Posted
Posted
dude thouse wires are snipped kinda close.....did you rack up a big xm bill and not pay? cause whoever bought this would have a hard time activating it.

Not at all. For the most part, the wires would be discarded anyway, replaced by the lead-in wiring from an XM antenna. The power leads are likewise no biggie.

 

Activation is easy Just call the toll-free number, or activate via the internet.

 

I think it is a good opportunity. My only question is if the OEM radio has to be flashed to accept the module. Sure would be a nice and neat integration for a cheap price, assuming the bidding doesn't go crazy. If I didn't already have my Pioneer XM, I'd bid on it.

atomoverride Enthusiast

atomoverride

Posted
Posted

 

:thumbs: I was just pointing out some facts for other people before there was a hogwild bidding war started. Thats all, jebus some people are touchy. You just have to be careful when buying stuff like that, and yes mostly it is pre-paid but what if its STOLEN? if its a unit that was re-ported stolen it will not work.

lrymal Senior Enthusiast

lrymal

Posted
Posted
...You just have to be careful when buying stuff like that, and yes mostly it is pre-paid but what if its STOLEN?...

Well, this is the nature of the products on eBay and other auction sites. It is always a "buyer beware". One major clue is that the seller has over 1000 feedback units or so with hardly any negatives.

 

Don't assume everyone here is touchy.... :thumbs: Just that the comment made struck some nerves. A little diplomacy on the good advice given would have helped. These alpha-numeric characters on the computer screen do a lousy job of conveying true messages sometimes.

99-2door Senior Enthusiast

99-2door

Posted
Posted
:thumbs: I was just pointing out some facts for other people before there was a hogwild bidding war started. Thats all, jebus some people are touchy. You just have to be careful when buying stuff like that, and yes mostly it is pre-paid but what if its STOLEN? if its a unit that was re-ported stolen it will not work.

If that's what you were trying to do you would have posted something to the effect of:

Might be a good deal, howeever I would be a little concerned that the module had been stolen and the buyer unable to activate it.

 

But that's not what you wrote. Instead you outright accused another member of trying to rip people off.

 

This forum is a great place to list goodies for sale and finds on e-bay, but if I got a response like that I probably wouldn't bother the next time I saw what I thought was a good deal.

:)

bansell Enthusiast

bansell

Posted
Posted
My only question is if the OEM radio has to be flashed to accept the module.  Sure would be a nice and neat integration for a cheap price, assuming the bidding doesn't go crazy.  If I didn't already have my Pioneer XM, I'd bid on it.

Yes, and the XM module also needs to be programed I believe, I think it contains the VIN number...

 

-Bill

 

P.s. I wonder if the radio wire can be bought from GM? where does it plug into?

I didn't see any spare plugs on the back of my radio...

jhill Enthusiast

jhill

Posted
Posted

Soundgate makes an interface which allows a pioneer xm tuner to be integrated in to allow use of your steering wheel controls and factory head unit for th edisplay.

Archived

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

Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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...