Re: VW Golf5 interior parts | Posts 16+

Yes, he did.

I'm saying, let's simulate... Then maybe add BSG, and that should be enough... 'If in doubt, please also send the gateway's intended configuration list...'

I received my Climatronic control panel today.
I guess I'll probably install it tomorrow.
From that point on, I can also help out with some testing and similar tasks.
Since I have PDC (presumably referring to a specific condition or technology), maybe I can see something.

Sure, Maxx.

If you're already using can tool, could you please run a trace for me for a few minutes?

'Thank you in advance.'

Sure, no problem .

Since you're talking about simulating it so casually with NM, do you both have the appropriate equipment (CANoe) for that?
If so, what are you using?

Sure, Maxx.

So, I have CANoe, CANalyzer, and CANape , but I only use them from work. I also highly doubt that I would personally buy a CAN card for more than 20,000 euros. ;)

And theoretically, NWM (presumably a specific function or feature) could also be simulated using the CANHack interface. It would just require someone to write the necessary software. NWM isn't really that complicated.

So, I have CANoe, CANalyzer, and CANape , but I only use them from work. I also highly doubt that I would personally buy a CAN card for more than 20,000 euros.

Okay, that explains quite a few things .

And NWM can theoretically also be simulated using the CANHack interface. One should just write the SW once.

Is it quite complicated? If not, that would be a brilliant addition to can tool .

NWM isn't really that complicated.

If you check it, it's not .

Here you can find the specifications for OSEK-NWM. Derived from that is the VW NWM, and the differences are very small and recognizable even to a layperson .



Integrating all of that into can tool doesn't really make sense, since each manufacturer uses a slightly different Network Management (NWM) system.http://portal.osek-vdx.org/index.php?option=com_content&task=view&id=9&Itemid=13{MARKER}

Okay, thank you. I'm just going to browse around there.

So, network management is actually relatively easy. Is a 'circle' of news items associated with a few status bits.

These are the IDs between 400 and 43F.


I'm looking for the OSEK COM 1.0 standard. Does anyone still have a copy they could send me?

If you want to simulate a control unit yourself (in my case, the auxiliary heater), you have to add it to the gateway's configuration list, right?
From this point on, network management will inevitably become a necessity, right?

When you register the control unit in the parts list, you would likely also expect other control units to send messages using that same control unit. This applies not only to the NWM but also to other messages. The specific details depend on the respective control unit.
and exceeds my level of knowledge.

Luckily, I already know which IDs the auxiliary heater normally transmits.
The question now is whether this information is also forwarded to the Climatronic system, even if the gateway's parts list does not include the auxiliary heater.
Does anyone know the answer to that?

Okay, my understanding (from what I've gathered from various forums) is that when you 'code' a device in the gateway, it essentially only monitors whether the device is present. If it's not there, the gateway logs an error, but that's all the coding does.
Conversely, if a device is not encoded, it can still function because it registers with the network management system. However, this only applies to the various internal CAN buses, not to the powertrain CAN bus!

So, are these functions interesting for the management, right?

SG_Address
Ring Message
Alive Message.
'Limp Home Message'
BusSleep Indication
BusSleep Acknowledged.