+1

COUT overload error when PWM HS is shorted to GND

minh lam 2 years ago in Master modules / MC4x updated by Gustav Widén (System support) 2 years ago 0

We are using a MC43 and using PWM and COUT channels. What we have noticed is when a PWM HS output is shorted to ground, one of our COUT outputs goes into overload. In our case, C2:51 was shorted to ground but C2:67/C2:15 had the overload error. 

+1
Will be answered

ID-Tag 4-7 for Molex MX123

Fredrik Forsberg 5 years ago in Master modules / MC4x updated by Gustav Widén (System support) 5 years ago 1

Hello,

ID-tag 4 to 7 does not exist for Molex MX123.

We use 4,5 and 7 today and have to re crimp those ID-Tags for MX123.

When do you plan to offer ID-Tags 4 to 7 for MX123?

Regards

Fredrik Forsberg  

+1
Under review

MC4X CAN bus labelling different in manual and IQAN Design

Kevin 6 years ago in Master modules / MC4x updated by Ulrik Zakariasson (Software development) 6 years ago 1

IQAN Design refers to CAN bus on the MC4X as A, B, C etc, manual (under installation) refers to it as numbers 1, 2, 3 etc. Although its obvious to work out, its better for us if its one designation across the board to avoid confusion when cross referencing documents.

+1

MC41 losing CAN comms

Captain Sprocket 6 years ago in Master modules / MC4x updated by Gustav Widén (System support) 6 years ago 1

We are using a MD4-7 and x2 MC41's on some of our machines (we actually wanted to use only x1 MC42 for these jobs but we are still waiting for the parts to arrive and have deadlines to meet so we are just using what we have available to get the job done)


But last night we started testing the machine and went through all of the procedures and functionality when all of a sudden an error appeared on the display telling me that one of the MC41 controller lost comms, but the other one was still fine and giving readings... So the 1st thing we tried to resolve this was typically switching the machine off and on, but this time there was no CAN comms at all.


We went though the wiring harness and made sure that everything was correct and the wiring was all good, so we then went and replaced both these controllers with new MC41's we had in stock, we plugged it in uploaded the software and the system was happy again with the new controllers and it is still working fine at this moment... So I took the 2 faulty MC41's to my office and connected it all together to try and diagnose the issue. 


Each time I tried uploading software (using IQANDESIGN 5.01 via ethernet) it kept on warning me about the incomplete system and that only the MD4-7 will be updated.


Eventually we switched from CAN-A to CAN-B only on the MC41's. but upon each attempt to upload the software, the same "incomplete system" warning appeared. 


So I just left it for a while and a few minutes later decided to just try again uploading once more. Well it worked all of a sudden and that is also a big problem, because I didn't change anything where I could say " there, that was the problem".


This is worrying us a bit, because we have no idea why this happened in the first place and secondly these machines are going to the middle of Africa... So this sort of thing must not happen at all!


I have only been using MD4's and MD3's with XA2's in the past without any problems at all, these are our first machines using the MC4x family and this is also the 1st time that I encountered any issues like this on IQAN.


Have anyone else experienced this before?  I have no idea why it failed or why it started to work again and this is definitely not the correct answer to give the person asking this question when there are deadlines to meet.


The other thing to mention also is the LED's on the controllers which blinked bright yellow 3 times then blinked dimmed yellow 3 times while it was not communicating. which also does not correspond with these fault codes in the manual. There was no RED LED blinking at all. 

Image 1044

0
Answered

OUT pins a/b

Peter Tan 2 months ago in Master modules / MC4x updated by Gustav Widén (System support) 2 months ago 2

Apologize that I have to use the wired topic.  Otherwise the submit window will go to search result and not be able to submit my question.

Why there are OUT_xxa and OUT_xxb?  Are there any relationship between them?  Have to use them in pairs?

Image 4175

0

Open Load status not resetting in all situations

Russell Gunn 3 months ago in Master modules / MC4x updated by Gustav Widén (System support) 3 months ago 1

I am having a problem with the open load detection on a COUT on am MC43FS

  1. I am running IQANdesign 5.03.14.5040
  2. The manual indicates that the output detects open load two different ways which may be true, but the controller responds in three different ways.
    1. When the output is off, if the load is disconnected, the controller will set the open load status to TRUE, when the load is reconnected, the controller will set the open load status to FALSE and allow normal operation.
    2. When the output is on and passing some normal current, if the load is disconnected the controller will set the open load status to TRUE and turn off the output, if the load is reconnected, the open load status remains FALSE, and the output remains off until the command is set to zero. Setting the command to zero causes the controller to reset the open load status to FALSE, after which the output will respond to a normal current command.
    3. When the output is on, AND some fault causes the resistance of the load to increase such that less than 50% of the commanded current can be pushed through the load, the controller will, set the open load status to TRUE and turn off the output. Unfortunately commanding the output to zero does not cause the controller to reset the open load status to FALSE. This acts like the open load status is latched to TRUE if it was tripped by “extreme saturation”
  3. It is my belief the third response is a bug in MC43FS because, a MC2 running IQANdesign 4.07.7.4605 works as expected I.E. commanding the current to zero would reset the open load status to FALSE Such that the controller could lower the current and try again.
0

More (HS)* (LS)* MC43FS

Dartagnan Léonard 4 months ago in Master modules / MC4x updated by Gustav Widén (System support) 4 months ago 3

Hi, 

I have a applciation with alots of safety control Dout. 

Like i could read a the page 97 and 99 of the instruction book manuel of the MC43FS. 

We can have 5 Dout.

In safety function we need to combine one HS and one LS pin to a output. 

In Dout i have acces to 5 direcly and would need 6. 

I would like to know if it is possible to use the pin C2:71 HS and combine with a other LS for example C2:16 ? 

Else my other solution would be to use Cout as a ON/OFF signal output unidirectional. 

Thanks 

Dart 

0

Using a resistance output sensor on MC43

Deanne 4 months ago in Master modules / MC4x updated by Anders Olsson 4 months ago 1

A customer has purchased a resistance output level sensor (240-33 ohms). I have tried to find more information regarding converting this to a VIN, but couldn't find too much. I am wondering what else needs to be done other than incorporating a voltage divider in their circuit.

0

MC42 supply

hongxiang yu 6 months ago in Master modules / MC4x updated 6 months ago 3

Hi 

  I have a project MC42 for embedded Simulink models which is only possible in MC4x. But I got a information that Parker do not produce MC42 module anymore.  Is that true ?  If yes, Have any solution for simulink models in IQAN ?   

0

DOUT voltage when not enabled

Kai Rasporich 6 months ago in Master modules / MC4x updated 3 months ago 2

Hello,

I am having some trouble with the Parker MC41. I have a display button on another MD4 that enables / disabled the output on Pin 45 (DOUT-HS). I am seeing a proper system voltage of 12.26V when the value is true, however when I set it to false Pin 45 goes to 11.68V. Is this normal behavior? Should I have some sort of diode in there to get the desired on/off I am expecting?

Thank you.