I was called to look at a program I had written in 5.0. They said that the video stream had a glitch and that text behind the video stream was flashing through the video stream image. After a few hours of observing the issue without success I reverted the program back to 5.0 and the program worked as designed.

The program was designed for various machine set-ups, (i.e. if there is one or two cameras, if it is a forklift or a container handler or both etc... various screen options are turned on or remain unseen in the background).

In this bug a video Rear-view Mirror video stream should have been turned off due to the machine set-up. The area used by the Rear-view Mirror stream would be replaced by information regarding the condition of the handler. If the screen went to a video page, (once), and returned back to the screen that had the turned-off Rear-view Camera image, the video image would be displayed and information that should be displayed was covered up. A flashing message would flash through the unwanted video stream with every pulse. Only cycling power would reset the logic. 

Reverting back to the native firm-ware fixed the issue.

For whatever reason updating the Rev-level of IQAN-Design caused the issue with how and when the video stream is displayed. Possibly if I removed the troublesome logic when updating the firmware and re-wrote it in 6.05 this may have worked fine but I did not try this.

Have you noticed similar issues with logic is translated/mapped during firmware updates? 

Very new to IQAN so my first project is try to set LED lights on a Grayhill 6-button keypad using J1939 protocol. I looked at the spec sheet and set up the FIN. There are values to each LED indicator (blinking, solid), but I am a bit stuck now and I am getting a warning that a parameter is overlapping.

This may not at all be the intended purpose of the IQAN ecosystem, but have you ever considered implementing the possibility to execute code outside of and in parallel with the control system loop?

This would greatly expand the usage potential of the system, as it could allow for such things as big integer computations, string manipulation, cryptography, more advanced protocols for data exchange built on top of CAN, etc.

The interface between the control system application and the out-of-loop thread could be similar to the JFIN/JFOUT structure, i.e. the control system loop could "transmit" and "receive" data to/from the thread. Code could be written in a superset of QCode, or maybe in C.

Hie guys....I'm designing an iQAN system with 2 master controllers...the MD4-7 and MC43. Have ordered an XC43 but it will take time to be delivered so need to use MC43 as an expander. The MC43 module is blinking red twice and yellow 3 times. Measured resistance bettween CANH and CANL with modules powered off and it was 2.3K and with modules ON was around 120 ohms. Kindly assist 

Hi,

I observed a bug on our machine.

If a sensor is detected in error, a defaut Error value is applied.

For us, this error value is 500 bar.

We made an Internal Digital Channel to detect if the value is egale to 500.

If true, the channel change to TRUE value.

But when the MC43 is a new one, the channel doesn't work.

As you can see on the picture, the channel value is 500, but the Internal Digital Channel is still FALSE :

Whereas the Qcode is simply :

If I just change the defaut error value to another in IQANRun, and set back to 500, the channel starts to work.

Did you already see that ?

The value tested comes from a filter channel, maybe that's the point, but it is strange that it's working if I change the value and set it back to the same defaut value :

We already observed something similar if we update a machine with a new soft on which one we change something on an existing variable. But here it's a new MC43.

IqanGo app have too small fonts for the values. If there would be large font mode, you could see important values more easily.

I recently encountered an error on a machine in the field where an MD4 will not boot up if it has 24 volts coming into C2 pin 1 or C2 pin 2.  MD4 is running IQAN Design 6.08.  Instead it will say "IQAN-MD4 Safe mode! Application no loaded Open or short circuit on ADDR pins."  I was able to replicate in a lab.  

We recently renewed our IQAN license and updated to the latest  version of design which is when this problem started.  As a test, I reflashed the exact same program except that it was written in IQAN design 6.02.  I did not encounter the same issue with IQAN 6.02 so I believe this problem was introduced in 6.08.  

Please review as we have machine in the field that have been running for a while that are using C2:1 and C2:2 as rocker switch inputs.  The MD4s will not boot while the rocker switch is in the ON position.  

Is there a programmatic way turn off a MD4 display but leave the controller and program running in the background?

Good morning,
I kindly ask for help regarding the following problem:
as soon as I start the engine, the system detects an "Abnormal update rate" error SPN639 FMI 9 and a warning SPN1235, FMI9. I want to clarify that after a while that the engine works, the RPM + and RPM- command does not work anymore until I switch it off and on again. All engine data are correctly displayed and managed. Can you help me please?
Thanks.

Best regards,
Lorenzo Simonetti