Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: mhw on December 13, 2013, 12:22:41 PM
-
I have a couple of different locations that have a H2-DM1E CPU using MWX and MRX to talk to a GS-EDRV100. Both give the following error: "Exception response in MWX @00000272 (MWX at VFD_COM@34)" The response code is blinking a 4. The drive is working but I always have the yellow error light on in DMD. Any ideas on how to eliminate the errors?
-
Sounds like you are writing a location that the drive is unhappy about.
Is there a reason that you aren't using the Ethernet I/O function to control the drives? It should be much easier.
-
Sounds like you are writing a location that the drive is unhappy about.
I am only writing to two addresses. It gives a maximum of three errors before a success. I am not counting successive successes or I should say summing successive successes. I love alliterations.
Is there a reason that you aren't using the Ethernet I/O function to control the drives? It should be much easier.
That's the way I've always done it. :) The other reason is that I think I read that the PLC will drop out of run mode if it looses communication with an attached device. While I prefer this with remote IO, I do not like that idea with a drive.
-
Sounds like you are writing a location that the drive is unhappy about.
I am only writing to two addresses. It gives a maximum of three errors before a success. I am not counting successive successes or I should say summing successive successes. I love alliterations.
I smell a nerd. ;)
Not sure. The exception response is the slave device telling the master he doesn't like what he asked for. Why? Not sure.
Is there a reason that you aren't using the Ethernet I/O function to control the drives? It should be much easier.
That's the way I've always done it. :) The other reason is that I think I read that the PLC will drop out of run mode if it looses communication with an attached device. While I prefer this with remote IO, I do not like that idea with a drive.
That is configurable. You can set each slave up to stay in run mode on failure. Use the built-in. It's sexy...and might even make this problem go away. Be sure your EDRV100 has the latest firmware.
-
Be sure your EDRV100 has the latest firmware
That may be a problem also. I know I had to revert to an older firmware in one of these EDRVs because the firmware in the GSdrive is too old.
-
Be sure your EDRV100 has the latest firmware
That may be a problem also. I know I had to revert to an older firmware in one of these EDRVs because the firmware in the GSdrive is too old.
Ah...yuk. Yeah that may be an issue.
-
I put a timer in that will delay the JMP from the MRX stage to the MWX stage. A minimum time of 29ms will keep the error from occurring.
-
Ah...a second write is happening before the first is completed and the EDRV100 throwing an exception response.
-
I had this same problem with my GS2's over RS485. I added a slight delay between the round robbin read/writes and it took care of the problem.