We would like to be able to trigger the log page of a non display log (MC43) use a text button action in the MD4. Currently one action available for the text button is to trigger a log located in the MD4, but it does not allow triggering a log in another master. We utilize this function to allow the user to quickly review historical data for important machine events. For instance, when we winterize the machine, we log that it was winterized. We also log when the machine is de-winterized (water is sensed in the system again). The winterization page has a history button that allows the user to see each event. In our multi-master system, the winterization function is handled by the MC43, so the log is in the MC43. So, my history button does not function. The only solution I can see is to send winterization event status to the MD4 using a CAN message and move the log to the MD4. 

Alternatively, you could add a show trigger to the log. I would have to pass the VDIN to the MC43 via a CAN message and then use this to show the log page. 

We are having issues which started with 6.05.( same results 6.06) Upgrading program software with MD4 and Mc43 via Md4 ethernet port, it proceeds till loading up Mc43 then says no contact and stops. Only fix we found is load up through Can adapter or Bluetooth( can take few hours) Anyone else have issues upgrading through ethernet?

Is there a way to add informations about External Functions file (project name/project version) in the main application .idax, under the system information page?

Actually, in my project, under System Information page, only the .idax Project name and version appear. 

But no information from the different .idex files is displayed. 

I am setting up a communication between the IQAN system (MD4) and Anybus Ethernt/IP gateway on a logic controller(CANBus). I am interesting in configuring a query/response transaction between the two. Is it possible to generate a message on iQANDesign so that the Anybus will receive? 

I know this questions has a few answers already, but none of them seem to be working for us.

I now have separate J1939 'modules' assigned for each master and their addresses identical to their masters, and have tried connecting the J1939 bus to both the Diagnostic & master bus, but with no luck. I still get no contact with one module and the second is not found.

Any direction or help would be appreciated.

Would it be possible to allow disabled inputs to still be measured from measure groups?

I think this is a bug, but I might be doing something wrong.

I am trying to send a large number over J1939, i.e. 1,292,122,139

The resulting HEX value should be 4D 04 38 1B, however, what I receive is HEX 4D 04 38 00 resulting in 1,292,122,112.

Seems anytime I use 4 Byte messages, the last byte is always 00.

Same is true if I send: 1,000,000,001, 1,000,000,015, etc..

I am using IQAN Design 5.05.10.5539, and IQAN Analyze 5.009.1890

We recently found a bug where a math object appears underneath the Hiding column within an IMSG. The math object cannot be clicked and only appears if the user first selects the grey background and then the IMSG channel. If the user moves from a different channel to the IMSG the additional math object does not appear. I have deleted the IMSG entirely and then recreated it and the problem is replicated. If any of the object list components are removed then the issue does not happen. When simulating the program the issue is similar but the rogue math object only appears briefly before disappearing.

I want to know why this error is appearing, and how to fix it (ideally without having to change the contents of the IMSG channel).

Note: this issue appeared after the program was updated to version 6.06

I think I have a GUI bug in iQANdesign 6.06

The activating object "B" in this channel shows up also as a blocking object.

If I click anywhere in the blocking window it disappears but will reappear as soon as the channel is closed and reopened.

It will also disappear if the property inspector is resized or the center divider is moved.

If the channel is opened with the activating window too small the ghost duplicate will be cutoff at the same point

The duplicate channel does not exist in a text export:

          BEGIN 92488
          Internal digital channel (IDC)
          Name=Allow elevated idle
          Description=
          Toggle=No
          Delay on=0
          Delay off=0
          Function selector=Not used
          X=620
          Y=480
            
            BEGIN 92489
            Function
            Name=Default function
            Description=
              
              BEGIN 92490
              Object group
              Name=Activating
              Description=
              Method=Or
              Valid=True
              Expression=
                
                BEGIN 92497
                Math object
                Name=A
                Description=
                Operator=not
                Operand 1=Production running instant
                END 92497
                
                BEGIN 92499
                Math object
                Name=B
                Description=
                Operator=<
                Operand 1=Engine Speed Limit Request - Minimum Continuous [rpm]
                Operand 2=1300
                END 92499
              END 92490
              
              BEGIN 92491
              Object group
              Name=Blocking
              Description=
              Method=Or
              Valid=True
              Expression=
                
                BEGIN 92495
                Math object
                Name=A
                Description=
                Operator=>
                Operand 1=Engine Speed Limit Request - Minimum Continuous [rpm]
                Operand 2=2005
                END 92495
              END 92491
            END 92489
          END 92488

Hello,

We use text buttons without text all over our systems.

We put transparent symbols in the buttons showing then what the button does.

In the latest update 6.06 you made the change: Automatic text on text button.

This put text all over all of the buttons in our programs.

Making all of our programs unusable.

We have migrated back to 6.05.19 but hope you will reconsider this change.

Regards,