We have a system with 1 x MC43FS, 1 x MD4-7, 1 x XC21 and 2 x MC41FS, running 6.08.30.8216.

On MC43FS we have 2 x CAN Open encoders on CAN Bus E that are sending PDO and heartbeat information as soon as we apply power. These are configured to run at 125kbps. We established that when updating the project it would update all the modules except MC43FS which hangs and crashes out. It seems to begin updating the MC43FS module (does it last in line after all the others), but stops halfway through and crashes out. System has to have power cycled and screen says no application and have to reload the software. Occasionally it will load in, around 10% success rate. When it drops out i get flash 'no application available' as in instruction manual.

Unplugging one encoder and IQAN will allow me to update the system including the MC43FS with occasional dropout.

Changing the bus speed of the encoders has improved it, seems to allow me to update the system with both encoders connected smoothly, occasionally hangs but significantly better.

Is there an interaction between the MC43FS firmware and speed of CAN devices? We had this issue a few years back on a MC3 and that was conflicting speeds on firmware check before boot. Seems it may also be present on these newer modules?

Weirdly also it says 6.08.24 for the MC43FS, however we are using 6.08.30. I noticed the IQANDesign 6.08.30 only has this for the MD4 and not the MC43FS, which mislead me somewhat when trying to establish the fault.

Has anyone had any success using IQAN and CANopen to control and monitor VFD parameters?

I've seen a fair amount of VFDs that have CANopen communication modules as options, just wondering if anyone has had any success stories or recommendations.

I'd much prefer J1939 for ease of programming in IQANdesign, but I haven't seen any VFDs that support J1939 messaging.

I'm trying to run an IQANScript from the command line. The goal is to probe every truck in our field once in a while, eventually to be used to schedule software update during the night, when the truck is not operational. The script has to be running on its own without human intervention, but everytime I'm trying to connect using IQANconnect, it pops a message for the user to enter the credentials. The only property in the CONNECT action from script is the machine ID, and the action to LOGIN is not working either in from or after. Is there a way to prevent the pop-up and connect automatically? 

An other bugs, or bad evolution also in IQANrun 7,

I am using two MC43 on my machines, and I know MC43 don't have RTC.

But I added an external RTC to my project, and to set it, I use IQANrun to set Time and Date in my calculator, and then I can send the good Time and Date in my external RTC.

Each time I start my machine, my external RTC set my calculators and they are with the good time and date.

But now, if I understand well, because using MC43 (without RTC), setting Time and Date is not allowed in IQANrun.

I spend hours and hours to make it working :

https://forum.iqan.se/communities/1/topics/1632-tda-message-to-set-date-and-time-of-mc43#comment-7397

Hello,

We create a clone file with run 6 from an Iqan 2 application with MDL2, reopen the clonefile not possible anymore, because the MDL is in design not supported anymore.

How can we open the clonefile in this case?

And when it is not possible, why is it possible to create a clonefile with Run 6 of an application version 2.63

Kind regards

Laura 

Are there any example programs for the LC5 joystick?

Currently utilizing the 2007699 (lc5-c01-mpb2w2t1) joystick

using iqan design 6.02. I get the LC5 and link it to an MC43 on system layout but how do i get the axis outputs and button digital io? I can find no EDS file or instructions as to PDOs for the outputs?

Thanks in advance

Our service computer with IQANRUn is defunct and we received new one. But the new computer with IQANRun is without any password stored. How do I generate new password in the program? There is no possibility to get it from the old computer so I cannot get the iqd file. Unfortunately this basic problem is not explained anywhere here.

Since version 7 I get a "Impicit value type conversion" warning when I use a Derivative function in the activation part of a value log item.

Does anyone have a idea how to solve this?

Why is the IDC delay on / off time [ms] limited at 3276750 in version 7

(and unlimited in version 6)

We are swapping out from the XA2 to the XC43 and we originally thought we were going to be using the PWM HS output so we attached a ark suppressing diode on the 4-way 3-pos cart valve (HSP 10-47CB-0-v-24ER). We however ended up using the PWM HS-LS output which has a internal free wheeling diode. Is the newly installed ark suppression diode going to case problems down the road. and is it best practice to just use the internal diode on the PWM HS+LS output?