We have a MC2 controller that works normally for some time then it stops. It works again after power cycling it. The led flashes in a pattern not in the instruction book. It just flasher red very rapidly. Any idea on what the cause can be?
I have an MC2 that will not accept a new date/time. It's stuck on 01/01/2001 - 00:00:00.
I connected to it, and used IQANrun to set date/time, it says it was successful, but the date/time didn't change. I rebooted the system, did not help.
J1939 TDA is disabled for this machine, RTC is enabled.
Wondering if anyone has seen this before....
I've been working with potentiometers and parker sensors (pressure and temperature) before without any problems, but now i need to use a voltage output (0-5V) from an amplifier as a voltage input on my MC2. The amplifier is connected to a sensor and have a standard +- output. I've tried to connect + to one of the VIN-x and neg to -VREF (or to the common terminal on the power supply). Tried different combinations but the measurement mode on the MC2 shows zero input all the time. Multimeter measurements confirm that the amplifier output around 1V. Logically don't see why it should now work, but maybe you can advise how 3rd party sensors (amplifiers) are connected to parker systems? Thank you!
Using the COUT output from the IQAN MC2, I can adjust the current, but there does not seem to be any way to adjust the voltage. When we measure the voltage across the connector from the MC2, we only get 14V.
Any thoughts on how I can get the IQAN to match the output of the controller from the machine?
I’m experiencing a MC2 VREF error high 6.60v show up on a MD4 display unfortunately the product is not currently here to troubleshoot but I would like to know if this may or may not be an already known Bug with master to master communication/hardware monitoring. In the MC2 I am not using the module diagnostics for VREF, however assuming it still reports that information to the headmaster.
This is on a 12v system and the only place the 5 volts is used is 7 switches (on/off) as a checksum/and direction change sense to high impedance analog inputs. I have done this before without issue however it was 2.6 software, this is the first one with 3.0 software.
I thought seeing as I can’t troubleshoot it at the moment I would ask and possibly save time if this already a known issue.
Customer support service by UserEcho