PE6 Plotter-Addin: How to assign signal?

[bkiepke]

Hi,

I have a symbol file that contains a definition like

Code: Select all

[CGA3_TPDO1]
ID=1D0h-1D3h
DLC=8
Var=Length unsigned 0,32 /u:mm /max:67108863 /f:0.1

How can I plot the signals of the different nodes using the plotter add-in?
The only signal offered in the dialog to assign a signal is
Baumer_CGA3.CGA3_TPDO1.Length

[M.Heidemann]

Hello!

The Plotter-Addin can only work with what's defined in the Symbol-File,
if you need to Plot the data as well you'll need edit the Symbolfile so it includes a singal/variable with
the data-bytes of the message.

In your example the only signal/variable defined is 'Length',
no other Variable is available for this Symbol.

If you need help with editing your Symbol-File, take a look at the
Symbol-Editor Help, which you can access by opening the Symbol-Editor (Tools -> Symbol-Editor) and using
the hotkey F1.

I'd recommend taking a look at the chapter "Signals" under "Working with Symbol Files" -> "Signals" as a starting point to modify your Symbol-file:

WorkingWithSymbolFiles.png (83.39 KiB) Viewed 4191 times

Let me know if you were successful using this approach

Best Regards

Marvin

[bkiepke]

Hi,

that's rigth I have one variable for each of the four messages with ID's
ID=1D0h
ID=1D1h
ID=1D2h
ID=1D3h

Thats, for what I understand is, the purpose of the line
ID=ID0h-1D3h

So how can I select the length of each message? I can see the messages in the send/receive window, so I would expect to have some selector within plotter. Any chance? Any update on this planned?

[M.Heidemann]

Hello,

I am not sure, if i am 100% sure this is what you are asking for but:

You could define a seperate Symbol for each message-Id, each containing a length variable.

The Plotter works symbol based, if there is only one symbol it will only show one symbol, regardless
of the underlying data.

If you prefer to, we can switch to german if that makes it easier to explain the situation.

Please let me know.

Best Regards

Marvin

[bkiepke]

Hi,

english is fine.

That means I need to rework all my symbol files to use the plotter-add-in. Also means that I need to copy / paste hundreds of symbols and set the ID for each.
This is then also true for the panel-add-in right, as it is also "symbol based"?

Might be possible in the future to make symbol-resolution aware of the ID, so a symbol in my case would be fully qualified like: Baumer_GCA3.1D0h.CGA3_TPDO1.Length
Seems not to complicated.

[M.Heidemann]

Hello,

All of PCAN-Explorer 6 is symbol-based,
what i mean by that is that each Signal/Variable has to be assigned within a Symbol,
which in turn represents a specifc CAN-ID(s).
The fact that it works this way has historical reasons.
Seems like you are working with CANopen, in which case we would have recommended
to check out CANopen Magic by our partner EmsA:

https://www.peak-system.com/CANopen-Magic.258.0.html

PCAN-Explorer 6 does not implement any CANopen-specific functionality and therefore
might not be the best solution for your exact usecase.

Best Regards

Marvin

[bkiepke]

Thanks for sharing that tool, really looks interessting.

Yes I am using CANopen in this usecase, but I am also sure it doesn't change the original question.

To check whether my understanding of the current situation is correct:
1. Symbol files provide an ID-tag which can hold a range of IDs. So it's either ID=100h or ID=100h-200h.
2. None of the add-ins is aware of ID-tags that can hold a range of IDs - in fact IDs are ignored by add-ins at all, for historical reasons.

Code: Select all

[A] // this is the symbol
ID=100h-200h // this is ignored by add-ins
Var=Stuff // this is the variable

3. Add-ins can only reference to "A.Stuff" and are not able to distinguish between the different nodes sending "Stuff"
4. Possible workaround

Code: Select all

[A_100h] // this is the symbol
ID=100h // this is ignored by add-ins
Var=Stuff // this is the variable
... a lot of almost equal definitions later ...
[A_200h]
ID=200h
Var=Stuff

Is that correct?

[M.Heidemann]

Hello,

You are correct.

For your usecase it isn't ideal that PCAN-Explorer 6 will handle ID-ranges as one symbol, regardless which ID within that range is currently providing data. Handling each id within that range as their own Symbol would be the workaround.

Best Regards

Marvin