The Minidisplay supports using Scenes the possibility of different CAN-IDs. This is working fine.
[variable1]
name="speed"
canid=0x100 // ID
position=0,8 // Bit start and length
In our System, the CAN-ID is not the only way to seperate values. Unfortunately we seperate the Content by using additionally Byte1 of the CAN-Message.
Example
canid=0x123, Byte1= 11, Variable1 is on Position 16,8
canid=0x123, Byte1= 12, Variable2 is on Position 24.16
Is there any possibility to seperate the variables not only using the CAN-ID?
At the Moment we always overwrite variable1 by variable2 if the next CAN-message is received.
Seperate variables by CAN-ID and content of ByteX
Re: Seperate variables by CAN-ID and content of ByteX
Hello,
it is possible to define "multiplexer" to interpret the databytes differently.
At least Firmware V1.1.5 is required.
Start with the definition of the multiplexer:
[variable1]
name="Var1_mux"
messagename="testmessage1"
position=0,8 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=1 // 0=none, 1=multiplexer, 2=multiplexed
muxval=0 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
timeoutval=0
Then define the "multiplexed" variables. Here two variables Var2a and Var2b are defined.
In case the multiplexer-value is "1" Var2a is updated.
In case the multiplexer-value is "2" var2b is updated.
[variable2]
name="Var2a"
messagename="testmessage1"
position=32,16 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=2 // 0=none, 1=multiplexor, 2=multiplexed
muxval=1 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
[variable3]
name="Var2b"
messagename="testmessage1"
position=32,16 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=2 // 0=none, 1=multiplexor, 2=multiplexed
muxval=2 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
it is possible to define "multiplexer" to interpret the databytes differently.
At least Firmware V1.1.5 is required.
Start with the definition of the multiplexer:
[variable1]
name="Var1_mux"
messagename="testmessage1"
position=0,8 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=1 // 0=none, 1=multiplexer, 2=multiplexed
muxval=0 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
timeoutval=0
Then define the "multiplexed" variables. Here two variables Var2a and Var2b are defined.
In case the multiplexer-value is "1" Var2a is updated.
In case the multiplexer-value is "2" var2b is updated.
[variable2]
name="Var2a"
messagename="testmessage1"
position=32,16 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=2 // 0=none, 1=multiplexor, 2=multiplexed
muxval=1 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
[variable3]
name="Var2b"
messagename="testmessage1"
position=32,16 // bitstart,bitlen
byteorder=0 // 0=intel, 1=Motorola
muxtype=2 // 0=none, 1=multiplexor, 2=multiplexed
muxval=2 // if muxtype=2, variable is updated in case current multiplexor has this value
scale=1 // scale set to 1
offset=0 //
vartype=0 // 0=unsigned, 1=signed, 2=float, 3=double(not supported)
datatype=0 // result is unsigned
- PEAK-Support
- Sales & Support
- Posts: 1646
- Joined: Fri 10. Sep 2010, 19:34
Re: Seperate variables by CAN-ID and content of ByteX
The latest Package incl. the Firmware could be download from here
--------------------------------
PEAK-System Technik
Technical Support Team
support[at]peak-system.com
-------------------------------
PEAK-System Technik
Technical Support Team
support[at]peak-system.com
-------------------------------