News:

  • June 07, 2026, 02:00:57 AM

Login with username, password and session length

« previous next »
Pages: [1]

Author Topic: ST136 $IOMapError  (Read 9866 times)

Mike Nash

  • Hero Member
  • *****
  • Posts: 652
ST136 $IOMapError
« on: June 09, 2016, 09:00:45 PM »
I was getting a weird error yesterday after installing an additional remote rack, updating firmware in the PLC H2-DM1E to the latest and loading in the program changed offline. It was ST136 $IOMapError but I could not figure out why, only that it was the new rack - 6 slot with EBC-100, F2-8AD4DA-2 and D2-08CDR. The solution turned out to be increasing the WX and WY memory sizes. I don't recall how much I went up, maybe 320 so 0-319 each. But I don't understand why 308 elements each (for WX0-307 and WY0-307) was giving an error when WX307 and WY306 are the last addressed.

Yes manual addressing and also yes, I forgot about right clicking the bar to set the starts.


 
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6158
  • Yes Pinky, Do-more will control the world!
Re: ST136 $IOMapError
« Reply #1 on: June 10, 2016, 08:59:32 AM »
If I'm following, when you increased to 308 with that config, it was unhappy? In the controller, not DmD? Probably an OBOB in the PLC's mapping routine.
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

Mike Nash

  • Hero Member
  • *****
  • Posts: 652
Re: ST136 $IOMapError
« Reply #2 on: June 10, 2016, 01:03:11 PM »
Quote from: BobO on June 10, 2016, 08:59:32 AM
If I'm following, when you increased to 308 with that config, it was unhappy? In the controller, not DmD? Probably an OBOB in the PLC's mapping routine.

I believe that is true as far as the PLC not liking it. I tried to data view the ST136 bit but it never changed state (and I don't recall whether it was 0 or 1, but it was the same as the bits above and below.

It was set for 308 elements which I had figured was good since that gave thru WX307 and WY307. It would not go to run and I think it was faulting but ... My memory type is Dynamic, it requires constant refreshes or it gets corrupted!  ;D
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6158
  • Yes Pinky, Do-more will control the world!
Re: ST136 $IOMapError
« Reply #3 on: June 10, 2016, 01:29:58 PM »
Quote from: Mike Nash on June 10, 2016, 01:03:11 PM
It was set for 308 elements which I had figured was good since that gave thru WX307 and WY307. It would not go to run and I think it was faulting but ...

I would love to see if it works with 309. It's probably just off by one on the range comparison.
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

Mike Nash

  • Hero Member
  • *****
  • Posts: 652
Re: ST136 $IOMapError
« Reply #4 on: June 10, 2016, 05:04:56 PM »
Quote from: BobO on June 10, 2016, 01:29:58 PM
I would love to see if it works with 309. It's probably just off by one on the range comparison.

I know, and I started to do that, but I was already short on time, especially after chasing this a little, so I just made it bigger. I wasn't sure that was even going to help since I couldn't see what was wrong with it. And now I'm back in my home state.

Oddly, the next morning the Cat 5 patch cord to the new EBC100 rack failed after a power cycle. Bad crimped connector (at least I didn't do it!) Easy (OK, went straight to it lucky) find and big relief.
Logged
Pages: [1]
« previous next »