Hello,

This happens in a system with just an MC43, and no other connection than Ethernet.

Same hardware and software without problems on previous machines.

After successfully sent the project to the system (through Ethernet, and from IQAN Run or from IQAN Design ), when trying to go online the following screen appears:

(from IQANDesign 5 Latest version, after trying to go online)

(from IQANRun 5.01, after trying to get system info,or enter Adjust, or whatever)

It seems the module lights blink the following way:

4xRed,

2xYellow + 2xYellow + 1xYellow + 3xYellow

All short blinks...probably.

Any hint?

Thanks a lot.

.One of my customer receive this message , this is a MD3. I dont know why ?

I have a customer who has had 2 MD3's fail in 2 years. They are in Puerto Rico and they think this is due to the humidity. Has anyone else seen this? I personally have not seen the MD3 that they are replacing so I don't know if it is beat up or user error. 

We have 2 machines with identical control systems which consists of x2 MC41's and a MD4-7 (programmed in IqanDesign 5.01)  and have come across some timing issues on these systems.

1st issue is with the startup siren:

We have a siren connected to an output on one of the MC41's. When the machine is switched on it should give 2 short consecutive "honks" and then stop. (This function works with a "blinking" method using "internal digital" channel, where when activated it should honk for 333ms and then off for 333ms and then honk again for 333ms and all this happens within 1 sec with another internal digital that blocks the "blink" function when 1sec has been reached and all this seems to work as intended in  a simulation) but in reality, sometimes it takes even longer than 2 seconds to stop the siren which results in 4-5 honks when switching the machine on (this timing issue is very irregular and will work correctly say 1/10 times of switching the machine off and on). Also this function does not transmit anything over CAN which might have causes a delay somewhere but this logic runs locally on the MC41 that activates the siren, so I don't see why this function should not work as intended.

2nd issue is with recording working hours with a timer function:

I am using a normal timer channel that is set to "hours" to record and display the working hours of these machines, but I have realized that it is counting way too fast and I cannot see why.

I am sure I am just missing some minor detail here to resolve this... But I have spend too much time already just trying to figure out this silly little startup siren timing issue, so this is why I have finally resorted to asking for answers on this forum.

We are having issues with a system that has 2 XC10's on the same expansion bus. This is the first system we used multiple XC10's and have been having issues since we got it online.The XC10's expansion bus is connected to a MC43.

Changing different settings seems to have some affect but I feel like no matter how we change settings this issue is still around it just might not popup as much.

We either get a multiple address error or a no contact error. When we get the no contact error if we look online the device is working however any outputs that were active are faulted and we need to cycle them to get it going. This seems normal for a no contact issue. We see these errors on startup and occasionally while running.

Here are settings I changed. When I changed them I cycle power 25 times to try to gauge where we need things set. The settings I played with are the MC43 cycle time, expansion bus divider, delaying and staggering the 'Enable' for the XC10's. And I recorded the occurrences of each message.

There is a pattern but I'm having a hard time decided where to set things. We currently have the system set with settings that didn't give us problems during the test, but during further testing we occasional see them.

20 ms MC43 

Expansion bus divider =  2(40mS)

Cycle util = 11% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000               

0 - No Contacts     

0 - XC10 Multiple addresses

10 ms MC43 

Expansion bus divider =  2(20mS) 

cycle util = 21% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

2 - XC10 -Multiple addresses

10 ms MC43 

Expansion bus divider =  2(20mS) 

cycle util = 21% 

XC10[0] Enable delay = 5000 

XC10[1] Enable delay = 0000             

0 - No Contacts     

2 - XC10 -Multiple addresses

10 ms MC43 

Expansion bus divider =  9(90mS) 

cycle util = 21% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

0 - XC10 -Multiple addresses

 5 ms MC43 

Expansion bus divider =  2(10mS) 

cycle util = 41% 

XC10[0] Enable delay = 0000 

XC10[1] Enable delay = 0000                

0 - No Contacts     

4 - XC10 -Multiple addresses

 5 ms MC43 

Expansion bus divider =  2(10mS) 

cycle util = 41% 

XC10[0] Enable delay = 5000 

XC10[1] Enable delay = 0000               

0 - No Contacts     

3 - XC10 -Multiple addresses

  5 ms MC43 

Expansion bus divider = 10(50mS) , 

cycle util = 41%  

XC10[0] Enable delay = 0000  

XC10[1] Enable delay = 0000                

1(1) - No Contacts     

0 - XC10 -Multiple addresses

5 ms MC43 

Expansion bus divider = 10(50mS) 

cycle util = 41% 

XC10[0] Enable delay = 4000 

XC10[1] Enable delay = 8000                

1(1)  - No Contacts     

0 - XC10 -Multiple addresses

The installation manual states an example for a 2 wire 0-20mA input into the controller, but there is no reference to a 3 wire input. Are these supported? I'm assuming it will be the same connections just the sensor ground (which does not include the signal) will go to chassis or vref -ve? Can anyone confirm?

l have an L90LS valve with proportional soleniods and would like to use a Joystick to operate which is the best choice out of parker range

where on the MC41 I connect LED lamp and how is it controlled it via the program

Has anyone had any luck using 4-20ma sensors to a VIN using a 250 ohm resistor to convert the signal 1 to 5 volts?

It seems to me that this is a good option since most IQAN modules (except MC4X series) don't have current loop inputs, but I haven't tried this yet. Obviously using a low tolerance resistor would help, but would doing this take any of the benefit away of using a 4-20ma signal in the first place?

Is it possible to adjust the default time that Vdin buttons when pressed and held remain 'on' for?

We have a multi-master application using a MD4-10 and a MD4-7. On each we have momentary buttons commanding functions that are slow in operation meaning the button has to be pressed for some time- By default the buttons while still pressed go to the 'off' state by Iqan even though still pressed requiring the user to press again- this is not acceptable to the user. We cannot latch the buttons for safety reasons. The buttons seem to switch to 'off' after about 10-12 secs on the MD4-10 but longer (approx 20 secs) on the MD4-7.