Why is the IQANDesign 6.07 COUT limit 1350 mA? 

An MC43 shows 2500 mA limit. How can the current be increased within the program?

I am sending a 4 byte Hex JPOUT (0x45564153 starting on bit 33).  When sniffing the bus - the 53 is being sent as 80.  Is there some reason for this?  I changed it to two 2-byte JPOUT's and it seems to work as a workaround.  Is there a problem with how Iqan handles integers in this case?

Hello. I am a beginner in using IQAN and have some issues: 1 - I have created a finite state machine for 2 modes. I have also created some function groups for some functionalities. I want certain function groups to only run in a certain mode and be blocked in the other mode (Like a top level conditional statement). However, apparently function groups do not have the option to be blocked like signals. Is there a way around this? Also, the transition happens while the operator is holding a button (name it A). So during the transition process the operator needs to be holding button A and when the button is left midway the transition is stopped (in this phase do we need an additional state? because it is neither in mode 1 or 2). During the transition between the modes I want to lock all function groups. Finally, the transition can only occur if a certain precondition is satisfied. I cannot seem to break down this problem and do it. 2 - As a final question, I have used some sensors to measure the position of a cylinder, but when I am doing a horizontal path, I need to maintain the same y axis for my end tip of the arm. I have done the kinematic calculations and have assigned vin and the cout, but because the simulation is not in real time, I do not know whether the sensor in the next cycle measuring the position of the end tip really gives a vertical lift path or not? How can I do the simulation continuously to see if my final position at the end of each cycle really have the same y coordinate. These questions might be a bit vague but again I am a beginner and would appreciate any help. thank you in advance for the help. 

An external CANBUS node is sending Error Number as Hex-Number. The Hex Number is 2Byte long. I like to show the hex in a simple way in the display because page long dokumentation are available already for troubleshooting based on Hex Numbers. 

Is there any way to show Hex-Numbers a simple way?

Hello, we are thinking of integrating a system that uses UDS CAN communication and we were wondering if IQAN is compatible with this type communication.

Thank you.

Hello,

I am utilizing GFIN to handle incoming CAN messages from a vehicle CAN bus. I am looking at detecting if the IQAN screen has lost communication from the CAN channel it communicates on. I tried using the "Timeout" feature on GFIN, though it seems to have a different definition than the "Timeout" given to the JFIN blocks.

I expect that if the GFIN block does not receive an updated CAN frame within the span of the Timeout value, the GFIN block would return a false pulse. The GFIN block does not seem to react this way. 

If I want to detect if a GFIN block has lost CAN communication, is this the right approach? Or is this not possible to do using the GFIN blocks. Perhaps there is another method I can try? Thanks.

Hello,

I renew my question here, how many version of IQAN TALK exist?

mine is Pro version 2.41 and I think the reason why i can connect the machine as the message says in my laptop is because the software is to old so I would like to install a different version of TALK

thanks in advance

Br

/Adrien

It would be nice if when you make a second screen shot, the save location is the same as the one you used before.

Now every time you make a screen shot you need to navigate to the save location you want to use.

In the master list of CAN ID's there are alot of them missing, but if you go to filter a message you will find it. And if you select only that message it will appear then. 

Ex 1218 does not exist when you show all ID's, but if I filter 1218 only then I can get the data.

When you are trying to reverse engineer a CAN bus and need to quickly know all ID's that are being broadcasted on the bus, this is a Major issue.  Spent hours wondering why my CAN router was not working, Its because I am missing ID's that I did not know existed. 

Camera ISO 17215 compatibility

In IQANdesign, there are two camera modules, the SV camera and Generic camera.

An advantage of using the SV is that more properties can be changed by the application; for example framrate, mirror and flip.

The interface between MD4 and IQAN-SV camera is the standard ISO 17215 (Road vehicles — Video communication interface for cameras), using SOME/IP for communication. 

With IQANdesign 6.08.32, support for this protocol has been improved to make it possible to use cameras from other suppliers in the same way as an IQAN-SV camera. 

Download 6.08.32 from IQAN store

Previous IQANdesign versions have a problem with downloading via the check for updates function, to update download 6.08 from https://www.iqan.se/downloads.html