My internal variable is false but my result is true and it is not a latching function? 

I  want to use a Text Formatting Channel to concatenate two or more text parameters into a single cohesive blob of text to overcome the 100 character Text Parameter limitation and help format the text neatly.  I found two bugs:

1. TFC doesn't carriage-return/word-wrap when using a fixed pixel width.  Static text labels do word-wrap correctly.  TFC should also word-wrap rather than truncating to a single line of fixed width.  The designer shows TFC word-wrapping but the simulator and real display do not word-wrap.
2. My TFC is freezing and failing to concatenate some of the strings in the attached example.  The channel measure tool in IQANdesign shows the TFC updating and concatenating two TPs correctly but the real display and simulator view do not refresh.  

IQANdesign shows the TFC updating:

Real display and simulator TFC freezes in state 1 when TPs are on state 2:

Please see the attached example, you will find the concatenation works some of the time but not all of the time:

junk test TFC bugs.idsx

Thanks,

Lucian

Does 7.00 also have a fix for ref case 57049 (IQAN 6.08.24). Sometimes it is very difficult to get to the ID tag our machines so removing it takes a lot of effort. It would be very nice if a firmware update could be performed without removing the ID tag.

Why does the below relational function evaluate incorrectly? sensorInput of 37.50 should evaluate to a result of 60. It does the same when I try using Object List.

As of mid February we have released IQANconnect so that no more connection fees apply.

The IQANStore is updated accordingly.

More information about how it works can be found here IQANconnect article

Have fun connecting!

I use IQAN 6 with this display and module. The error pop up message on the MD4 display does not relay the correct MC43 pin. If there is an open load on MC43 pin C2:46, the display shows open load on pin C2:65. The display gets the output name, error, and module name correct, but the pin location is wrong in the pop up. 

Thanks,

Hi,  I have a system were I have a MD4-7 and MC43 in the system.  Occasionally  the MD4 starts displaying every second a loss of contact with MC43.  i can see this being logged as well.  the MC43 seem ok, no loss of contact with MD4.   also I have checked the BUS, no errors no frame errors.  all I can see that every time this MSG pops up the 0EF00  84->83  message stops, when the CAN message restarts the MD4 pop up message disappears.  any help would be appreciated.

.  

Hey,

Not sure if this has changed in Version 7 but in Version 4, 5 and 6 the DateTime stored in Logs does not include Milliseconds.  Since the Cycle Time is in Milliseconds, would it be possible to add milliseconds to the Log DateTime?

DateTime is currently formatted like:

2/20/2024 8:04:16 PM

Perhaps a format like this....

2024-02-20T20:04:16+0250

Or something along those lines.

would it be possible to have more Command line arguments available in a future update? some ideas are below

IQANdesign: having the ability recompile a converted idax file from txt back to idax.

IQANrun: having the ability to get a clone, Setting and log files from a machine. additional connection option with Bluetooth and sending an additional argument for the Bluetooth paring code. 

As well as a help command to list all the options available for command line arguments. Additionally, having the user manuals have more information in for command line arguments. such as in IQANrun 7 there is no mention on how to use the IQANconnect key if connecting with IQAN connect. 

After I upgraded my program it generates an error, i use cycle time and the error stats that the the name is not unique. the is not the case, copying the code in a function in the application it will generate no error

code used in the evend log:

Same code but used in an ID in the application: