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.

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

Using an old Danfoss JS700 J1939 joystick and having trouble getting a position reading. I believe I have the correct bit parameters assigned, source address, PGN and I am getting a good metered reading on the wiring. I am wondering what other parameters I'm missing.

Can anyone advise why Canbus parameters in Designer can only be 1,2,4 bits or 1, 2 4 bytes in length? I ask in that I have a device that Im connecting to that has parameters of 14 bits, followed by 5 bits then 9 bits lengths  etc because that optimizes their use of the bus for the data types they need. I can of course achieve the same by defining an interim Byte 1 through 8 integer math channel and use heaps of shift left and shift right and band functions to build my own structure.  and then add into byte by byte parameters.

If the parameter channel allowed length of any bit value then we wouldn't have to jump through hoops to build our own structure just let designer do as it does already for the existing options?

Or is there some other SAE standards related reason why that can't be done, in which case the manufacturer of the device Im trying to connect to  must be out of standards?

I have an application where the IQAN system need to communicate with a other CANBUS controller via CANopen. 11bit identifiers are used. Unfortunately the data length is often packed in a data block up to 32byte. IQAN is limited to 8xbytes. Is it possible to extend the length?? 

Hello,

When a Function Group is provided with appr.150 MEM channels and appr. 30 controlling SMC and appr. 200 IDC (see attached file) and a random propery needs to be changed, there is a great delay to enter the property or to navigate or to save the changes that have been made in the proporty. (very time comsuming)

Is this a normal phenomenon? Do I have to keep the Function Group with less contents to keep the (working)speed ok?

I'm using the latest IQANdesign version (6.08.30.8216)Property Delay.png

ThrottleControl.idsx

Hey People

Im interested in what occurs on a IQAN master when a Timeout that is attached to a J1939 JFIN occurs. I cant find anything int he manual that comes with Design and suspect that teh standards might well cover it, but I dont have them.

Why the question?

I have a 3rd party J1939 module on an MD4-10 Canbus C bus that is shared with a wired CanOpen remote and a wireless CanOpen remote. Due to e recent change requested of me I was seeing disconnects occurring with the module that controls the engine RPM via a 0-5V output. When the module disconnected it never reconnects, until I shut down the IQAN master and restart it. The disconnect next time occurs at roughly the same sequence of events that caused the first so its repeatable. prior to the last change I made in the throttle control we had seen very occasional disconnects, but with the change it occured every time we tried to advance from high idle to work rpm

I changed the 2 JFOUT channels from "Continuously" (100mS interval) to "On change" and changed the JFIN timeout from not set to 300mS (The device was set to continuously every 100mS). This meant that when the disconnects occurred and they still did at the same point in sequence but within a short time after the comms were reestablished. The small timeframe of disconnect meant that the end rpm on the engine may not have ended up being exactly what it should have been but any subsequent press of a throttle control that resulted in a changed frame value meant that we got what we needed. I suspect that the issue was actually solved by the timeout on the JFIN and not the change to the JFOUT frames. I didn't have sufficient time on the machine to test this, but will make a new load including this change for the next mechanics on site.

So:-

1) what exactly does a timeout  occurring trigger within the master, why does it reconnect when it didnt without the timeout set

2) How can i fault find the disconnect and understand why its occurring. The other bus members are not disconnecting and we are seeing no remote lag that might be a disconnect reconnect process occurring. I presume that our USB canbus dongle wont help because what ever is occurring is probably outside of the j1939 protocol and further down the stack closer to the physical interface? Logic Analyser??? Which is probably as big a project in itself as the whole rest of the design project

Would appreciate any guidance from you who have been here before

Ive attached a subset of my project (First line of the post) that relates to the J1939 module I'm talking about. The settings are as they were when the issue causing the disconnect occurred.

Andy

Hi, I am getting the following MC43 code R4:1 6:1:6:2, it is not in the documentation. Does someone know what is the critical stop reason? I happens randomly at very long interval. Is there a list of all the codes somewhere or does someone know the meaning of that code?

video: https://photos.app.goo.gl/xbFbLxKePhzq28tz5

thanks! 

I am doing a conversion of an old IQAN system using the MDM screen with XS and XT2 modules. So far everything is translating over pretty clearly, but was wondering if there was any guidance on how to mimic the functionality of the Locking objects. From the IQANdevelop help file, it looks like if the Locking objects are true, it will freeze the output of the function.