[Gav]

I’d say you’ve got a wiring fault or the adapter you’re using isn’t compatible but I’m no expert

 

[timo]

When you plug it in the dash doesn’t light up like a Christmas tree does it?

see here on my x260

https://www.jaginfo.org/threads/how-to-add-options-to-your-car-via-ssd-part-1-of-2.112926/?post_id=2856022#post-2856022

Here you are using that cheap chinese clone mongoose on your X260 ??
Thatmeans those MY17 x260 arent DOIP yet, otherwise you couldnt do that with sdd on you that x260 ??? correct me if im wrong ?

And most of these chinese mongoose has on theyr description also that they wont support for x260.
So im a little confused

 

[Gav]

Here you are using that cheap chinese clone mongoose on your X260 ??
Thatmeans those MY17 x260 arent DOIP yet, otherwise you couldnt do that with sdd on you that x260 ??? correct me if im wrong ?

And most of these chinese mongoose has on theyr description also that they wont support for x260.
So im a little confused

Yeah I used a mangoose! Cable had to snip pin 13 though for the x260 as if you didn’t simply plugging in the lead made the dash light up!

 

[timo]

Yeah I used a mangoose! Cable had to snip pin 13 though for the x260 as if you didn’t simply plugging in the lead made the dash light up!

Ok thats good to know. ill remember that.

But on this page is also written, that my VXDIAG VCX NANO is compatible device

http://blog.obdii365.com/2024/10/17/free-download-jlr-sdd-v165/

So it should work .

 

[timo]

I’d say you’ve got a wiring fault or the adapter you’re using isn’t compatible but I’m no expert

Just to be sure , a few questions.

1. Pin 13 in the x260 obd connector isnt used ?? I can disconnect it and do still all the programming and stuff ? Or is it just the chinese mongoose so called feature

2. Maybe the pin 13 is also driving me vxdiag vcx nano crazy (or car) and that why it wont connect to most of my modules also ? I just dont know about it cause a lot of my light and errors were allready lit up before i connected the interface to the car ?? It might be a possibility ?

 

[Gav]

Just be be clear, IF when you plug your mongoose cable into the obd2 port and turn on the ignition, and it lights up, then you need to snip pin 13 on the mongoose cable NOT the obd2 port.

Stock photo, check you’re actually snipping pin 13 on the lead they should be numbered

 

[timo]

One more question, if i start trying to unplug modules and find wich is bad, how is this done ?

1. Just rip the plugs out of module

Or

2. Battery off first, then unplig the module then battery on again ??

 

[cutlea01]

Unplug the 2 fibre cables and use a fibre link bridge on them. No need to remove power each time.

 

[timo]

Unplug the 2 fibre cables and use a fibre link bridge on them. No need to remove power each time.

Im a lityle confused. I actually havent found any fibers on my modules. Opticals i mean with that. There are some regular coaxial cables but i habent seen any optical cables yet. Should all the modules have 2 opticals, 1 in and another that goes forward ?

 

[Gav]

Think you’re right most of the modules are on the ms-can bus so should just be wired. No optical as that’s fast and not needed.
Have you tired SDD with a suitable power supply and a snipped pin 13 on your mongoose yet?

 

[timo]

Think you’re right most of the modules are on the ms-can bus so should just be wired. No optical as that’s fast and not needed.
Have you tired SDD with a suitable power supply and a snipped pin 13 on your mongoose yet?

Tried Mongoose with snipped pin and vxdiag both with SDD, but no changes.

Also had a power supply on the car, so sdd showed green battery icon.

Most modules we see are on pt_hscan, also changing constantly what are visible and what not. Some rare times few modules from bo_mscan also pop up, but when refrehing the sdd, they are gone again.

Any idea were to start, i cant turn ignition on as both keys dont work anymore, and cant sync them with sdd, throws an error after asking wich instrument cluster i have, doesnt matter wich one i choose, cluster type or digital type.

 

[cutlea01]

I'd put an oscilloscope on the MS and HS data buses and see what's going on there. My thinking is a duff module is breaking comms protocols and is transmitting on the bus out of turn so bringing the bus down, then repeat, maybe that's why you sometimes see modules and then lose them to regain them later. Unplug a module at a time, the connector with the twisted copper pairs to remove it from the bus, they're joined to the bus in parallel so very easy to remove by simply unplugging their bus connection.

 

[Gav]

Check resistance on the bus too should be around 120 ohms

 

[timo]

I'd put an oscilloscope on the MS and HS data buses and see what's going on there. My thinking is a duff module is breaking comms protocols and is transmitting on the bus out of turn so bringing the bus down, then repeat, maybe that's why you sometimes see modules and then lose them to regain them later. Unplug a module at a time, the connector with the twisted copper pairs to remove it from the bus, they're joined to the bus in parallel so very easy to remove by simply unplugging their bus connection.

Thanks, i think i start todo that soon
Oscilloscope isnt a thing everybody have though Any other way to check if there is something strange happening there ?

Can a bad module on Bring down a whole bus ?
And even Another BUS ??

LEts say i have a bad module on a CO_HSCAN, can it bring down all other modules on the CH_HSCAN

Just explain like you would to 5 tear old

 

[timo]

Check resistance on the bus too should be around 120 ohms

You mean the resistance on the twisted copper pair ?????

Or measured from module with can bus disconnected ?

 

[cutlea01]

Can a bad module on Bring down a whole bus ?

Yes. The bus is 1s and 0s, over the 2 wires. A 1 being transmitted would cause the CAN high wire to show a high voltage (3.5v) and the CAN low wire to show a low voltage (1.5v). A 0 would have both wires at 2.5 volts. A module waits for bus availability before transmitting, but it is possible for modules to talk over each other causing an error, where the module would then send an error frame and retransmit its message. You can do basic measurements using a voltmeter. Any more than basic you need a 'scope to see what's going on, the speed of a MS bus is 125kbit/s and HS is 1Mbit/s (I think, from memory) so you can see visually what's going on.

A handy quick guide to general CAN bus networks:
CAN BUS Troubleshooting Guide

 

[Gav]

You mean the resistance on the twisted copper pair ?????

Or measured from module with can bus disconnected ?

120 ohms at each end so if measuring across the two wires 60Ohms

 

[timo]

120 ohms at each end so if measuring across the two wires 60Ohms

I think that there is a little language barrier and i dont exactly know what you mean by "Measuring across the two wire" or "At each end "

I would really appreciate if you could help out there with a small example.

 

[Gav]

this is how the can bus is wired, so if you measure across can high and can low with a meter with everything off you should read 60 Ohms - 120 Ohm’s in parallel = 60 Ohms

The can bus I think is blue/white and white/blue
The resistors could be anywhere, they’re there a load for the signal to drive into and to stop reflections on the wire

 

[timo]

View attachment 203913
this is how the can bus is wired, so if you measure across can high and can low with a meter with everything off you should read 60 Ohms - 120 Ohm’s in parallel = 60 Ohms

The can bus I think is blue/white and white/blue
The resistors could be anywhere, they’re there a load for the signal to drive into and to stop reflections on the wire

OK, i got it now what you mean by across can hi and can low.

Stilla little faque about the paraller part

And Wich of the can bus wires is hi and wich is low ?

I actually cant thank you guys enough
I might even have a chance to get this paperweight running with your knowledge and patience with me