There is one thing missing in the example.
As it is you will only be sending out a 1 or a 0 from the input, an indicator of that a message ha been received.
Every time you receive a message i will be a 1 independent on what the actual message contains.
You will need to have parameter in from the input and have the parameter out looking at those instead.
Otherwise you will not get the data to be sent.
Did you record or write down the yellow flashes?
They tell us more exactly what has gone wrong.
Do you have anything else connected the the system?
Like and engine, transmission, CAN sensor or such?
I does work in the MAC channel.
You do have a round down or up function, it is "Floor(xxx)" or "Ceil(xxx)"
I did some changes and used the bitwise and function to simplify your function.
Result:= (round(xxxxxx*100) band 65535 )+ yy
Result:= Round(xxxxxx*100) shr 16
The value type of the MAC channel is also real, so if you want to shift a value from a MAC you need to use the round function on it to convert it to a integer value type.
You do have a Integer math (IMAC) channel that could be used instead also.
You can only use the the bitwise shift on integer value types.
That is why you can use it on the JPOUT channel but not the function parameter that has the value type real.
If you use a integer parameter instead of the function parameter it will work.
Or you can use the round function on the parameter you have in the math to make it to a integer.
something like this;
Result:= round(xxxxxx) shr 16
Currently, there is no phase-out plan for the MD3, MC2, XA2 or XS2.
The MD3 and XA2/XS2 are among our highest volume products, with the majority of IQAN users having at least one of these running in full production.
When they eventually do enter phase-out (it will happen at some point), there will be an official phase out period spanning over several years.
What we are trying to achieve by not including these in the IQANdesign 6 release are two things:
-one is to give the message that one shouldn't base any new machine designs on MD3, MC2, XA2 or XS2, and instead go for the MD4, MC4x and XC4x series
-the other is to give a heads-up saying that these are mature products, and do this in good time before we go into phase-out, to allow machine designers as much time as possible to start thinking about updates on machines designed using MD3/MC2/XA2/XS2.
To support existing designs, the version 5.x branch will live on in parallel with version 6, with new 5.x versions containing bug fixes and a subset of the feature updates from 6.x.
Yes, as long as the calculation order is correct.
Do you know how much power the sensor draws?
The VREF on the MD4 display has a maximum load of 50 mA.
Do you have a shared ground between the sensor and the display?
No, you can not program the DOUT to a specific voltage.
And the DOUT on the MD4 is a low side output, meaning you are grounding trough the display when the output is turned on.
So you do not get anything out from the DOUT.
You can not just send the the array channel as it does not have any value in it self (value type void).
You would first need to use a math channel to get a specific value from the array and then send that.So if you wanted to send the values from an array you would need to extract all the values with math channels and then send those.
Is this happening after you have done a simulation?
We had issues with channels seeming to move when the zoom functionality was used.
Improvements were done in 5.04 to fix the moving channels but looks like it is not perfect.
When you have the view zoomed and then switch function group with simulator running you still have an issue with the channels not being zoomed correctly. after stopping the simulator the channels get moved to the correct positions, but they are not zoomed correctly so it looks like they are in the wrong position. If you then move them manually to what looks like the correct position and then go out and back in the the group the channels will have been move as much as you did, but from the original position.
This can be avoided by zooming one step either way when entering a group to get the correct size and position for channels.
We will need to make more improvements here.
Customer support service by UserEcho