Signal collision when creating panel

[sebnil]

I am trying to add 2 signal indications in a panel. The signals are ECU1.BoatSpeed and ECU2.BoatSpeed. When I add an indication I can only see the variable and not the symbol. There is no way to differentiate between the two variables since they have the same name, but they are on different CAN ids. See enclosed image.

Is this a bug? I would like to create an indication that is more specific using ECU1.BoatSpeed instead of just BoatSpeed.

[M.Gerber]

Dear sebnil,

You have the possibility to set a corresponding option. Go to Tools > Options > General. In the Signals area, change the Signal name display mode to Qualified Short Names. That will show the full name of each signal including the symbol name.

Greetings
Mark

[sebnil]

That solved it for collsions of signals from different ECUs. Now my next issue is collision of the same signal on different busses. What I want to do is have indicators for the same signal but on different busses. The problem is that there is no way of indicating this and the result is indicators that glitch and jump between the two values on the buses.

In short I want indicators for two signals:
ECU1.BoatSpeed on Bus1
ECU1.BoatSpeed on Bus2

The two buses use the same dbc-file.

Thank you for the fast responses so far and a fine product. For the most part, Pcan Explorer is a nice tool to work with.

[M.Gerber]

Sorry, in the Instruments Panel there isn't a possibility to distinguish between different busses.

One idea:

1. Import your dbc file with the PCAN Symbol Editor.
2. Adapt the name of the affected symbol or variable.
3. Save the symbol file.
4. In PCAN-Explorer, add the symbol file to your project.
5. Apply the symbol file to the second connection (i.e. bus).

With this workaround you have different signal names for the same CAN ID coming from different busses.

[sebnil]

Ok, a bit combersome but I guess it will work. I really think you should add this feature though since I probably am far from the only one with this issue. One idea would be to just name the signal like; Bus_name.Symbol_name.Signal_name