Your comments

The difference between IQAN-MC3 and IQAN-MC31 is that the IQAN-MC3 is design for safety related machine controls, and thus needs to have calculation of the probability of dangerous failure. This calculation is only valid within the specified lifetime, after that time there will at some point be a higher probability of failure. 


So in practice, the modules (MC3 and MC31) will last longer than this, that is a reason not to specify it for MC31, while for the IQAN-MC3 application, the lifetime has to be specified and considered in the application, so that the module can be replaced or the machine decommissioned before random hardware failures become more frequent. 



For the MD4, there is a component that is more subject to aging than the others, the backlight. Its intensity will be dropping as it is aging, but it is not easy to give an accurate statement. 

The component specs says brightness >50% at 40.000 hours for MD4-5 backlights and >50% brightness at 70.000 hours for MD4-7 and MD4-10 backlight, but this data given for 25°C, and with 100% backlight the temperatures will be higher, say 40-45°C. 

The selection of VREF-A, VREF-B or None on the VIN property for VREF is used in case there is a VREF error. 

The VIN:s are automatically assigned error value and the status VREF error if its associated VREF has an error on it. 



When you use the module VREF to supply a radiometric sensor, errors in absolute accuracy of the reference voltage is cancelled out. It is not a software function, it is just an effect of using the same 5 V reference for the VREF supply as for the AD conversion. 

That is why you on in the Appendix A information on the VIN:s can read that the absolute accuracy differs between using the module VREF and an external reference. 




If the adjust item for the TMR channel is placed in an adjust group, then would be possible to reset it via the menu system.


If an update is sent to the master where the component ID of the TMR channel is different it would be cleared (as it is no longer the same channel)


If an update is sent via IQANdesign with the send option for overwriting stored values, it would be reset.


Sending a settings file would also overwrite it, unless the adjust item has been placed in an adjust group and protected by a higher access level. 

The IQAN-MC3 has a specified liftime of 10 years or 40 000 hours, whichever comes first. 


This is not to say that this is the technical life of the product, this is the limit that is necessary to set to know how long the PFHd values are applicable. Because this is a precondition for calculating the PFHd, it also means that the SIL2 certification that depends on it is not valid after this time expired. 

The information is found in the safety manual for the IQAN-MC3 (instruction book)




For the IQAN-MD4 modules, we have not given any statement about the lifetime.

No, IQANcustomize is being discontinued from version 5 and onwards. As a replacement for IQANcustomize archive pages in IQANrun, it is possible to build up similar functionality using IQANscript, although it will look different. The possibility to create IQANrun setup files with alternative names and certain buttons disabled was almost never used. 

IQANscript 5.00 works with the license for IQAN Productive Studio (versions 2.x to 4.x )

There are changes in the license handling, but earlier IQANdesign and IQAN Creative Studio licenses are supposed to work on 5.00. We are investigating.

As an additional comment: 

In a single master system with only PC tools, modems and G11 on the Diagnostics bus, the IQAN diagnostics traffic is using  11-bit identifiers and will not collide with J1939 traffic. 

In IQAN multi-master systems, the diagnostics traffic between the masters is based on J1939 PDU1 messages, so there it would be possible to have a conflict with other 29-bit CAN

That makes it quite tricky to upgrade to version 4 where a Diagnostics bus is necessary.

The workaround I can think of is to replace the GFIN and GFOUT channels with JFIN and JFOUT channels that give the same identifiers, and connect the GPIN and GPOUT channels to these instead. With the properties for J1939 Prio, PGN and SA it will be possible to set all bits except for the J1939 EDP bit, that is always zero.