MC3 Current Consumption (and any other module)
Does the current consumption of the module (170mA @ 24V) increase if we start connecting sensors on the VREF pins or does this value include the max draw on both the VREF (140mA x 2)?
Does this apply to all master / expansion modules?
LED light patterns
Does Parker Hannifin have an LED status/error light pattern guideline for it's products in general?
Hello.
If you look trough the instruction books you will find that the blink panthers have roughly the same meaning on each of the current IQAN products.
The difference is if the unit in question have all the different blink codes or not.
There can also be a difference in the description of the error, this is why i said roughly.
For example, you have the blink code for output error 1:1.
On the MC2 it is only described as 'Output'.
On the XC21 it is described as 'DOUT error (open load)'.
This comes from that the only output on a XC21 is the DOUT and the only error detection we have on it is the open load.
On the MC2 we have more types of output channels that can generate this error so it is only described as 'output'.
These blink codes come from the MC3 instruction book.
Using these you can get a good idea of what is wrong with the unit.
1:1 Output
1:2 Input
1:3 VREF
2:1 Power Supply
2:2 Temperature
3:1 CAN, no contact
3:3 System mismatch
3:4 CAN error (bus off)
4:1 Internal error/OSE
4:2 Critical Temperature
4:3 Critical Stop
Measurement of current consumption on MC3 Vref
Is there a way of detecting how much current draw there is on the VREF supply on an MC3?
I have experimented with a SIL2 pressure transducer connected to an MD4 (don't have an MC3 to hand) and noticed that disconnecting the -VREF and leaving +5V supply and VIN signal wires connected to the controller will generate 2500mV signal into the MD4 VIN. This is not desirable as it simulates a pressure in the system which is not true. I can only imagine its how the internal electronic circuit is manufactured inside the transducer causing the false signal, but its not unique to one manufacture of pressure transducer. The current consumption of the sensor drops from 6mA to zero when the -VE is removed, wondered if this would be a good way to detect disconnected -VREF connection?
Aside from the method above or monitoring for a sudden change in VIN signal within the software, can anyone suggest any other solution to this issue?
MC3 Output Error on Start Up
One of our field units is getting the an "Error" on start-up. It occurs on every startup.
After the error is cleared, everything is working fine. The solenoid(s) showing the error function with no issue.
In the past we have seen open load and overload output errors but not just a generic error message. We replaced the MC3 module and the problem was resolved.
Just curious on what this means? Thanks
Use IQANsync to set Machine ID
It would be nice if there was a way to use IQANsync & a G11 modem to set the Machine ID. We program MD4's in batches, then after installation we have to go back to the vessel with a laptop to save logs, clear logs, and set the machine ID. It's convenient to be able to handle the logs with an iPhone, but we still need to laptop to set the Machine ID.
MC3 Module Input Error
Hello,
I have a drill rig (Geoprobe 6712DT) which has an MC3 Module installed. Recently, the hydraulic pump would intermittently would stop building operating pressure, and the only workaround I can find is to bypass the MC3 Module and manually force the pump to build pressure. The Module is giving me a 1:2 error code, or "Input" error. Could someone help elaborate what this error could mean in the general sense? Any info would probably help with my troubleshooting. I'm guessing it could be something as simple as a loose wire, but I can't seem to find any so far.
The drill rig comes with the MC3 Module installed, and has worked fine up until recently. The manufacturer doesn't really provide any troubleshooting in regards to said module, so I'm kind of just winging it. The manual for the module tells me that it is an Input Error, but I'm not really sure what could be causing that.
Thanks in advance for anyone who can help me out. My apologies for being somewhat ignorant as to this thing... I'm just a humble driller.
MDL2 Log Error - Failed writing
A 5 year old MDL2 is giving us this exact (system) pop-up message:
"
Log error
Failed writing. The log has been stopped!
"
My guess is that the (flash?) memory is full or corrupted, so system events like a startup or sensor error can't be written anymore. Not a big deal, but:
* How to get rid of the message
* In case the log memory is corrupt, would that also threaten other memories? In other words, should we replace this MDL2?
As far as I can see, this a fixed system message, not a custom pop-up.
Blank MD4 SCreen at start-up
I am using an MD4-7 screen on a test bench. 3 out of 4 starts I get either a White Screen or a black screens with some colored dots. Once I saw what seemed to be blocks of black and white.
Looks like the video driver is not starting properly. The application appear to be running since the canbus messages are being generated.
Can this be caused by the regulated switching power supply during start-up or do I have a defective MD4 screen?
Thanks for your inputs.
Ethernet port introduce to other master modules
Is there any plan to introduce Ethernet port to other master modules than MD4? It is quite a good feature in my opinion,
TROUBLESHOOTING A CAN NETWORK WITH IQAN INTERNAL RESISTORS
Our company uses an IQAN MDL2 setup which ties into the J1939 network of a Caterpillar system.
Our setup is using the internal resistor on the MDL as the terminating resistor on one end of the network and has a standard 120 Ohm resistor wired into the other end.
A machine in the field is having CAN network issues. Typically I am used to checking the resistance of the CAN network and the resistance of the terminating resistors as a standard checkout of the wiring. However with the internal resistor this is proving difficult.
In our lab I powered up a test MDL2 and checked resistance at the MDL with the MDL powered up but no other wiring attached. I found that I would measure ~69 Ohms across the internal resistor at first power up. If I shorted the CAN Hi and CAN Lo together by touching together my multimeter probes it would cause a CAN C "CRITICAL ERROR". After this error I would measure ~115 Ohms across the resistor until the power was cycled on the MDL.
All this said, my questions are:
-Do you have any recommendations for a standard procedure for troubleshooting CAN wiring/resistance?
-In light of the testing I did in our lab could you provide an explanation on how the internal terminating resistor on these IQANs work?
Thanks
Customer support service by UserEcho