Adapting the MC4x modules on our first machines now, we had quite a struggle with the various pin characteristics (DIN Pull-up / Down, A15/17 suitable for relays on the MC3, et cetera). Such details can be found in the Specs of course, but it would be quicker & easier if we can see such details in IQAN Design, for example in the bottom-right corner when clicking an in- or output pin.

Hello,

Are there any thoughts about integrating some kind of map app to the MD4?

Like google maps or something for navigation?

For example:

-Add a GPS device in the machine and then add some kind of map function in iqan design for the MD4.

-Connect a smartphone to the IQAN system and use the phones gps to show location in some kind of app on the MD4. Or maybe stream the phones map interface on the MD4.

Just some thoughts and ideas. Not high priority.

Regards

Fredrik Forsberg

Hello,

It would be great if IQAN allowed for Byte Order (Intel/Motorola) to be used on messages that are less then multiples of full bytes. Currently byte order can only be applied on 8/16/32 bit messages, but in some instances we may have a 12 or 14 bit message that requires endianess. We need to do some magic to reorder the bits before sending them, which is a pain.

For example, it is not possible in Parker to send the messages below with different byte orders, as they are not full-bytes.

I am doing a bunch with functional groups in the latest project to clean things up a bit, and it is annoying to have to individually name/rename each of the FGIs, especially when I change the name of the source and then "have to" rename it again in every Funtional Group where it shows up.
Maybe have a box to check to override the default name strategy for the times someone might want another name used.

Is there a way to export the pin list to an excel-friendly format?

The list is superb to use when making for example wiring cross-reference list.

I know of the Tools-->Project documentation but going to pdf and then to excel is not always so efficient .

J1939 -71 is now delivered as a large spreadsheet(digital annex) which makes it much easier to search. J1939 implementations from scratch is still a large task. Have you ever considered adding an SPN library to IQAN Design. Clicking on an SPN automatically assigns a parameter to the correct PGN frame with the default J1939 -71 descriptions. It also automatically adds that SPN to the DM1 list. I think this would speed up J1939 implementations.

Does somebody knows if it is possible to change the colour of for  example a bar graph by a variable.
Now yo have to choose a fixed colour.

I want to change the colour if the input value is above a adjustable setpoint.

The way program it now is to have two bar graph with different colours, and use the visible input to select the color.

Maybe a idea for a next release???

I really would like a lookup table for text. I have a list of errorcodes, now we only give the error number. This is not very clear to the user. So if we get an error code, I would like to be able to display a text to let the user know what the problem is. Because this list is very long, it would be very helpfull to have it in a lookup table where we can import a list. It is mentioned before, but I think it is not an any developpers list.

Idea : Table to manage error code / Software / IQAN