Your comments

It would be likely then that we would use IQAN 5.x and 6.x next to each other. Will solution libraries be compatible at least?

Consider using a finite state machine. Also it's worth exploring if you need in-between states ('D to N' or 'N to R'). They might make it easier to link to messages. The button triggers the in-between state. Depending on the output of the IMSG, you go to the next or the previous state.

What I like about the FSM is that you cannot create a situation where you are in multiple states at the same time, something you really want to prevent here.

Hope this helps ;) 

There are more addresses, you can check which ones and their resistances at the IQAN accessoires section.

The T means it has the added function of a 120Ohm end resistor if I'm correct. Should only be used at the end of a CAN-line.

I'm also curious, especially concerning the XA2's

I second this. There's quite some standard text in the application (MD3 in our case), and I can imagine that has been translated to other languages before. Is that available from Parker itself or already in the IQAN environment?

In that case we only need to translate our own custom messages and display items we put in.

I know what you mean Mark, I just got enthusiastic.

Here's two images I used to have a lot on the MD3. It is an indicator for a switch that fits exactly above the F1-F4 buttons.

The gradient in combination with the refreshing of the screen creates a nice optical effect when it switches over.



Here's something I'd like to share ;) A beautiful measurement, art in motion. We're considering framing it for our office. :P

I have some button images as well I can share, will upload those later.


Here's my rough instruction to new IQAN users here:

-Check out these videos:

-Play around with the forklift/wheel loader examples. Try adding/moving stuff and see how it affects the program.

-Use the manual for reference.

Normally I'd also sit with them to explain the interface and give them a few assignments.

- Building input to output

- Adding math in between (e.g. vectors)

- Adding logic (IDCs)

Master math channels and IDCs first, then move to things like finite state machines.

Hope this helps.

Have you tried windows key + left or up?

We've had a similar problem by having an adjust item as the required pin.

Put in a workaround by having the range be 1000-9999. (but decreases the possible pins by 10% ;-) )