Our latest generation of controllers are finally ready for production. The IQAN-MC4x family is the fastest and most capable controller range we have ever done. It comes in three sizes to support any application size, from the entry level task oriented control up to the high I/O configuration for complete machine control.
First out from the production line and available now for deliveries is the performance optimized version of IQAN-MC43. The IQAN-MC41 and IQAN-MC42 will start shipping next month (December 2016).
Work is ongoing with the Functional Safety versions and units capable for implementation of SIL2/PLd safety functions is planned for production Q3 2017.
Find more detailed info at: http://solutions.parker.com/LP=7632
On December 15th, we released the IQAN-MC4xFS series, with safety certification by RISE.
The release means that we now have SIL2/PLd versions on all three sized of the MC4x series:
You can read more about the new product in the press release.
In the press release, we make a reference to the EN 13849-1:2015 update. The EN 13849-1 standard lets machine designers create safety functions either based on electronic components certified by the manufacturer (like the MC4xFS), or design safety functions based on the EN 13849-1 architectures.
With the original 2006 release of the EN 13849-1 standard, there was great emphasis on on calculating hardware reliability, but requirements on safety related embedded software was not as clear as in IEC 61508. Now with the new 2015 update there is a clear limit, implementation of PLr=a and PLr=b functions are accepted on standard controllers, for PLr=c and higher, the use of controllers with safety certification is necessary.
To learn more about this topic and how to design complete safety functions in accordance with EN 13849-1, you can sing up for the IQAN focused training on functional safety.
For documentation of the MC4 product series, see the instruction book.
I recently discovered that the MC4x family does not have a RTC pin and therefore when you go to pull a log on a file, it simply gives you a "start number" and a base line of 12:00:00AM. This is not sufficient for what most of my customers needs are.
Are there any plans to add in an RTC pin to enable us to have actual time available when logging.
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?
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.
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.
I have a MC43 with the following blink code 4 red, 2 yellow, 1 yellow, 1 yellow, 1 yellow. What do the 3 yellow blinks at the end mean? This happens intermittently when the module first gets power.
If it's occurring on start up, the likely causes are battery voltage exists on an output before the module powers up or a slow rise in power supply voltage. Possible causes are covered in appendix B of the instruction book.
I am considering using an MC41 with PWM signals as inputs. These signals come from joystick thumbwheels on excavators made by a large multi-national OEM. My problem is the spec on the frequency of the PWM signal from the thumbwheel is 500Hz +/- 50Hz. I see the max allowable frequency from the MC4x catalog is 500Hz. Wondering if the MC41 will work with 550Hz PWM frequency input.
How this can be done? Did not find from channel properties.
You find the property on the pin in the module view.
Customer support service by UserEcho