I run a dedicated J1939 Bus to speak with the Vehicle CAN. I imagine most do it this way.
Now that I have to cover for the possibility of both 250kbs and 500kbs J1939 vehicle CAN buses, and do not want to have multiple versions of software floating around if I can help it (tried it, can be a bit of an unneeded mess), I am running out of CAN Buses on my MD3s.
The way it is now, I am planning on setting up 2 vehicle can buses, each with their own "engine", then pick which engine to enable in the settings (250kbs, 500kbs, or disabled). Unfortunately, that leaves me with a wasted Bus since I can not run both the 250 and the 500 to on the same physical CAN Bus pins. An empty Bus might even throw an error. I haven't tested it yet.
It would be nice to be able to select J1939 bus speed in the software settings or be able to disable the unused bus in the settings. Either would free up a bus on the MD3 so I wouldn't have to put absolutely everything else (Master, Expansion, Diagnostic, and J1939 components) all on the same physical bus.
Hi we have had a customer report 'IQAN Network Key Not Recognised' error appearing on MD4-7 with a 3 master system (2 x MC3). We are currently unable to access logs and see if this error has logged. There is no photograph of the error displayed on the screen, the operator only recalled it after the shift, therefore the error may have been worded slightly different.
Is there information on this type of error and what it means? I have looked through the manual and cannot find anything along these lines. I wondered if it was a project ID mismatch error?
Is there any way to add more digits as 4 to the pincode
Standard, every pincode in IQAN has 4 digits, so standard, it is not possible to have more digits
This is my système
In my log fil, i have toow calculateur
Coffret démarrage log = MD3
Coffret électrique log = MC3
When the Log MC3 is full, the MD3 not saved the news erreur yet the log full behavior is put on Continue logging.
In the help his write :
Continue logging makes the log delete its oldest records to make room for newer. Use this option if it is more important to see the latest events.
Why my news erreurs is not saved ?
Thank you for you help !
In IQAN design how do I select from a joystick input or potentiometer input to drive a the same current output
I'm trying to select from two different inputs to drive the one output, using a joystick for travel mode input and a potentiometer for sweep mode input. IAny ideas or any programming examples.
We have a machine in the field running 3.19 and we need to update the software remotely. To avoid updating the firmware (it takes too long and sometimes fails half way though updating) i need to revise the software using the correct version of IQAN Design originally installed on the machine. The machine appears to be running on firmware version 22.214.171.12443 in the MD3 and 126.96.36.1990 in the MC3. This is a multi master system.
Can anyone confirm which version of 3.19 I need to build the software change into to prevent having to update the firmware in the machine please? There are multiple versions of 3.19.9 and if I choose the incorrect one it will update the firmware.
I have tried to simulate 3.19.7 and 3.19.9 and use IQAN Run 3.19 to look at the firmware revision but the firmware does not appear to match what we have running in the machine. When I simulate I get 3.19.2.
We are getting fault code 2 orange / 1 orange / 1 orange / 9 orange / 4 red / 1 orange on MC3 controller. Does this error code mean internal error/OSC (4:1 in MC3 manual)? If so is there any way of getting more information on why the controller is switching off and more details on that specific error code? Fault appears to be random and only sometimes goes into error state, sometimes module boots fine with no issues or error codes. System is 1 x MD4, 2 x MC3. Intermittent fault present on both MC3 controllers. Both MC3 controllers have CAN Open device attached to each. We have used these CAN Open devices before with success.
Does anyone have the pin out for the MDL side of the USB connection? A previous employee had de-pinned the MDL end for some "testing" purposes but never put it back together or wrote down the pin out. I have searched threw any literature I have to no avail.
I have been using an MC2 as a control module for an excavator attachment. It was working fine until I added tried to add some CAN communication to send pressure sensor pressure values and joystick inputs to a Data Acquisition System. There were 9 signals. I attempted to load the file on, and at the end of the load it through an error saying something like "no return handshake from Master Module." I tried to reconnect to the system repeatedly but it would not establish a connection. I attempted to use the attachment and the MC2 was not sending out any signals.
After turning the power supply on and off and trying to reconnect unsuccessfully, I tried to read the lights. The following sequence repeated:
-2 long yellow followed by 3 short yellow. While not exact (extra long yellow), does this mean "Waiting for Restart"?
-4 Short Red followed by 1 short yellow: Internal Error
-18 short yellow - is this just the "there is something abnormal going on"?
I read this thread: http://forum.iqan.se/topics/98-mc2-cause-of-internal-errorose/ which seems to describe a similar issue. It seems like the advice is to short the ID pins and start in "safe" mode.
If the "waiting to restart" error keeps appearing even after cutting power and repowering, does that mean I need to try and start the program in "safe" mode and reload the program?
Anyone have a nice clean way to short the ID pins? Should I just put 2 clips on the end of a single wire? And what happens once I successfully reload the program? Should I cut power and then remove the shorting wire so it does not restart in "safe" mode?
It looks like there was an error in the software: I specified it try to broadcast the CAN data out over the wrong bus. The CAN data was also unconnected. In this case the information was not vital to the operation, but I am thinking this would be enough to throw an internal error and cause problems. Can someone confirm or deny that a module shut down could be due to a CAN comm error due to incorrectly spec'd bus OR unconnected CAN Comm cable?
Thank you, Graham
Customer support service by UserEcho