IQANdesign 7.05 released, CAN FD on diagnostics bus
Main features
Configurable speed on Diagnostics bus
It is possible to select between three different speeds:
- 250 kbps, classic CAN (default)
- 500 kbps, classic CAN
- 500/2000 kbps, CAN FD with 500 kbps arbitration and 2 Mbps data
CAN FD gives the highest increase in bandwidth with efficient packaging utilizing up to 64 bytes in the data field.
All IQAN master modules and G12 support speeds above 250 kbps.
CAN FD is supported on IQAN-MD5 displays, IQAN-MC4/MC4xFS CAN-A to -C and IQAN-G12.
To connecting with IQANdesign/IQANrun over CAN, select the correct arbitration speed; 250 or 500 kbps.
When set to 500 kbps, IQANdesign/IQANrun will automatically detect if the system is running 500 kbps classic or FD with 500/2000.
The status bar in IQANdesign/IQANrun shows the Diagnostics bus speed of the connected system.
It is also possible to check the Diagnostics bus speed from the menu system, system info.
NOTE. All modules on the bus must be run the same speed. The G12 automatically detects the speed in use on the bus when it starts up.
If an IQAN master module is started without application (bypass application), it will detect the diagnostic bus speed used by other modules on the bus.
Configurable speed on Master bus
Speed may be 250 kbps or 500 kbps classic CAN, or CAN FD with 500/2000 kbps.
This makes it possible to keep Diagnostics and Master bus mixed when increasing Diagnostics bus speed.
On the master bus data field remains at 8 bytes also with FD (future improvement possible).
CAN FD on Generic bus
FD speeds 250/250, 250/500, 250/1000, 500/500, 500/1000 and 500/2000 is now supported on Generic CAN.
Camera improvements
-Camera modules renamed to highlight the support for 3rd party cameras with SOME/IP, the protocol used by the SV camera. 3rd party cameras controlled by RTPS is now called RTSP (in previous version this was “generic” camera)
-Modified RTSP camera timeout to support more camera models
-RTSP camera will show the currently configured URL in the hint.
(RTSP port number is not shown, it is fixed to 554).
Other 7.05 updates
Several improvements in IQANrun, see:
Also see
Customer support service by UserEcho
Is there a way to update the Diagnostic bus speed in a multi master system program after the first load? I tried changing the diagnostic bus speed from 250 to 500 and when I tried to load the program - it updated the 2 MD4's but when it got to the MC43's it lost communication and I had to switch back to 250 kps to get it to load (the second MD4 required updating via Ethernet to change the bus speed back before loading the program again).
Update - I just loaded a 7.05 version of the same program overtop of the same program in 7.04 with no changes and it stopped again when it started to load the operating system for the first MC43 - no contact. It may not be that bus speed that caused it to fail loading.
Yes, the normal case is that you just send the update with the new diagnostics bus speed to the complete system in one go.
It gets more complicated if the update of some of the modules fail. You could get a situation with modules trying to use different speeds on the diagnostics bus. This was probably the case when you reverted to 250 and had to load the two MD4:s separately.
Separate loading of modules is one solution for fixing a system that has ended up with a mix of speeds.
With all masters already on 7.05, another method is to bypass application on master modules that don't have the right speed, when started without application a master module on 7.05 will autobaud.
There is definitely a repeatable problem with 7.05. I have loaded 3 different programs with no changes other than updating to 7.05 from 7.04 and they all stopped after loading the two MD4's when it tried to load the first MC43 (we have two MD4's and 3 MC43's in all these machines). Disconnected and no replay from the MC43. I tried both IqanDesign 7.05 and IqanRun 7.05 with the same results.