Hello,

Recently I had an issue where code meant for machine A was uploaded onto machine B, and machine B was able to halfway function. To prevent this issue in the future, I want to have some sort of identifier that the MD4 or MDL2 can read and either continue running or throw a message saying "Incompatible Code" and quit.

So far I have thought of a few possible solutions. If possible, I would like to do this over CANbus so I don't use up input pins.Ideally, it would be nice to have a module that broadcasts a serial number or identifier over CANbus that the MD4 can read and compare to a list of acceptable machines. Another idea would be to have the MD4 check a certain "identifier" module's address and only run the code if it can find it. Worse case scenario, we can use some sort of hardware tag, like a resistor, to send a voltage to one of the input pins.

Since I am a novice with IQAN software, I am curious if you have any better ways to do this. How would I implement such a feature?

Thanks for any help, I appreciate it!

Since there are no DM1/DM2 blocks to send out 1 or more faults yet, (hint!), I'm trying to implement it myself, using Array blocks. It works, BUT:

- No Array support on MC3 (for safety reasons? why?)

- No looping or "Add" functions to construct the list dynamically

- Arrays are Float by nature. This is inaccurate for 32 bit UINT DTC codes. Would be nice to have a integer (and if doing it anyway, a boolean) variant

- Ability to fill/insert/operate an Array from another block ("adding itself to the list")

Biggest problem is the MC3, where more than 50% of the CPU is currently spend on sending out DM1 & 2 messages. Which is obviously way overkill, but I don't see ways to do it more efficiently with the available tools.

Is there a way to set the J1939 Source Address field in the TSC1 command to an Integer Parameter? That was we can install the same crane software on different truck chassis with different engines.
Cummins/PACCAR like to use SA 7 for TSC1 control. Detroit Diesel likes to use SA 231. It would be nice to allow the J1939 SA field to look at an integer parameter and adjust the code accordingly.

Ability to change TP channel value using Qcode like:

if VDIN-Choice1 = true then TP1 := "Your choice value is:" + MAC-value1 + " that is under the limit"

I have an application where I want to send text strings over CAN on a very occasional basis. A tool for handling extended outgoing CAN frames for this task would be very useful.

Please include an auto ASCII converter in the tool.

Part four of the IQANdesign tutorial is now available, this one is introducing some of the Qcode sytax:

Hi,

I'm currently migrating a fairly large program from older IQAN hardware to the current.

The workspace for large programs is awful to use; can we get some kind of update to make this less frustrating?

I have multiple large function groups (30+ inputs) and there is no way to lay them out that makes it easy to read.

And can we also get some more tools other than comments to organize the software?

With all the FS changes and multi master systems likely becoming more common can we get some tools to help manage multi master systems?

It would be good if I could reference MCXX unit states and display them on my MD5 HMI and have it auto populate.

Thanks,

A

I like the solutions where you can drag and drop them into programs. Is it possible to drop in my own custom solutions? I think this would increase my productivity?