News:

  • August 30, 2026, 04:04:46 AM

Login with username, password and session length

« previous next »
Pages: [1]

Author Topic: Exceptiion response  (Read 17123 times)

mhw

  • Hero Member
  • *****
  • Posts: 250
Exceptiion response
« 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?
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Exceptiion response
« Reply #1 on: December 13, 2013, 12:30:16 PM »
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.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Exceptiion response
« Reply #2 on: December 13, 2013, 02:16:36 PM »
Quote
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.

Quote
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.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Exceptiion response
« Reply #3 on: December 13, 2013, 02:21:36 PM »
Quote from: mhw on December 13, 2013, 02:16:36 PM
Quote
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.

Quote from: mhw on December 13, 2013, 02:16:36 PM
Quote
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.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Exceptiion response
« Reply #4 on: December 13, 2013, 02:29:51 PM »
Quote
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.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Exceptiion response
« Reply #5 on: December 13, 2013, 02:54:39 PM »
Quote from: mhw on December 13, 2013, 02:29:51 PM
Quote
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.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

mhw

  • Hero Member
  • *****
  • Posts: 250
Re: Exceptiion response
« Reply #6 on: December 13, 2013, 03:22:31 PM »
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.
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6174
  • Yes Pinky, Do-more will control the world!
Re: Exceptiion response
« Reply #7 on: December 13, 2013, 04:09:29 PM »
Ah...a second write is happening before the first is completed and the EDRV100 throwing an exception response.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

plcnut

  • Hero Member
  • *****
  • Posts: 815
    • premiersi.com
Re: Exceptiion response
« Reply #8 on: December 13, 2013, 08:48:50 PM »
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.
Logged
Circumstances don't determine who we are, they only reveal it.

~Jason Wolthuis
Premier Systems Integration, LLC
https://premiersi.com
Pages: [1]
« previous next »