I have a problem with a system that uses APP in and out between three modules, one MD4, two MC3. I have found that one MC3 does not appear to be receiving APPIN's. When I monitor the modules in IQAN Run, all modules appear to be talking successfully. When I look at IQAN Design the APPIN's on the module that's faulting says Error, Timeout and its red not green. On the module that's sending the APPOUT, the function block APPOUT is green and OK. Its almost as if the modules are not starting at the same time and the timeout for the first APP in to be received is being reached?

Is there any way of finding out more information about this error?

The machine was working OK for some time and it just happened randomly and now im unable to recover the machine. We also have other machines running this software and same software version and it appears OK.

I have extended the 50ms cycle time to 100ms,on all three modules with no success. Is there any reason why this could have happened? Running Design 3.19.9.

I use IQAN 6 with this display and module. The error pop up message on the MD4 display does not relay the correct MC43 pin. If there is an open load on MC43 pin C2:46, the display shows open load on pin C2:65. The display gets the output name, error, and module name correct, but the pin location is wrong in the pop up. 

Thanks,

would it be possible to have more Command line arguments available in a future update? some ideas are below

IQANdesign: having the ability recompile a converted idax file from txt back to idax.

IQANrun: having the ability to get a clone, Setting and log files from a machine. additional connection option with Bluetooth and sending an additional argument for the Bluetooth paring code. 

As well as a help command to list all the options available for command line arguments. Additionally, having the user manuals have more information in for command line arguments. such as in IQANrun 7 there is no mention on how to use the IQANconnect key if connecting with IQAN connect. 

I have still lot of problem with IQANrun 7.01

I can't connect with IQANrun 7 to a machine that had a 5 or 6 version programme.
I have this error :

And when I connect with the computer of my technicien, I can connect but if I try to get a clone, after few minutes it doesn't work and it shut down the main calculator :

If I try again, I have this :

I could update the soft with IQANrun 6 to put a 7 versus to the MC43, but I can"t connect with IQANrun7...

Still the first error message.

Sorry but a lot of problem with this last version of IQAN 7.

Is there a way to save an IQANdesign7 project to IQANdesign 6 ?

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.

Hi!

SGI Group, in partnership with the Parker-Hannifin engineering team, has developed a solution for replacing Parker IQAN-LM joysticks worldwide.

This solution comes in a Plug&Play replacement kit. In mere minutes, your new joystick will be operating with 100% of the electronic features of the old one. Just simply place the components and connect them with the characteristic green connectors.

The solution comes in two versions so that you can choose the kit that best suits your needs.

https://www.sgingenieria.es/en/parker-iqan-lm-kit-solution/

SGI Group, en colaboración con el equipo de ingeniería de Parker Hannifin, ha desarrollado la solución de reemplazo para joysticks de la familia Parker IQAN LM . Es un kit de sustitución Plug&Play. En pocos minutos su nuevo joystick operará con el 100% de la funcionalidad electrónica del anterior. Simplemente precisa la ubicación de los componentes y el conexionado de sus característicos conectores verdes.

Esta solución se presenta en doble versión, pudiendo adquirir el kit que mejor se adapte a sus necesidades.

KIT_PLUG&PLAY_REPL_JOYSTICK_PARKER_IQAN_LM.pdf

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

I've noticed that if a new "value log item" is triggered while I have that log opened in the MD4 menu, the value that is recorded is the wrong value. Rather than record the channel's value when the event occurs, it records the channel's value when I close the log. Is this the intended behavior for logs or is this a bug?

I notice this in a program made in IQANdesign 6.08.25.8210. 

Hello all,

Back in the history 😊 IQAN TALK !

IQAN DG screen was in German and the MENU button was not working so I could not access any menus or change the languages

I managed to repair it (dirt on the PCB card) and all buttons are working now, I changed the language to ENGLISH and been able to understand the error message on the screen “Release Joystick”

Joystick rubber boots are not in really good shape so first thing is to set up new one if it’s still available, I am looking at it

I can also offer the customer a repair on his JS but in between I would like to increase the deadband with IQAN TALK software

I connect my laptop, managed to get connection on COM PORT 3 but when I tried to GET the application , that message pop up:

No manufacturer ID, this application probably too old

I have connect many machine of that age with IQAN TALK and never had any problem of communication

What do you thing, have you seen that before? 

Br

/Adrien