Welcome to EpoS Wizard!

As you’ll no doubt have noticed if you’ve previously visited any time in the last decade or two, EPoS Wizard has undergone some quite drastic changes!

YOU WILL BE REQUIRED TO CHANGE YOUR PASSWORD
(See below if you are unable to receive a password reset request)

Read on »

Share:
Notifications
Clear all

Destructive RAM test

6 Posts
2 Users
0 Reactions
932 Views
Posts: 8
Topic starter
Active Member
Joined: 14 years ago

I'm curious how much info the destructive RAM test actually destroys in the ECR. If I have the whole program saved in PLM2000, would there be a lot of work to get the registers running after doing this? I'm trying to wipe an error in the table map that seems to be associated with old bills and I'm at the point where wiping the RAM seems to be the only option.

Dylan

Reply
5 Replies
Posts: 25
Eminent Member
Joined: 15 years ago

what uniwell model are you using? you do not have to do a destructive ram test to clear blocked tables.

Reply
Posts: 8
Topic starter
Active Member
Joined: 14 years ago

I'm working on a pair of networked DX-895's. I posted about them a few days ago, and here's the problem:

"They are linked through ethernet and share a table map. The map shows three tables as pink (multiple tracks), but with "1" in the spot for how many tracks there are. I cannot access the supposed tracks, as "picking up" the table just creates a new track (even in training mode), and nothing prints out under a full clerk track report. I am even able to do a Z1 auto full transaction report (which I cannot do if open tracks exist).

Any suggestions on how to get the tables back to green?

To add to the history, these errors might have occurred when the two ECR's were out-of-sync on the IRC (showing ECR1: OK, ECR2: Busy, etc.) I initialized the IRC to fix that problem, but may not have cleaned up all the problem tracks before the Z1 was taken for the day."

I poked around to see if I could clear the tables, but had no luck. If you have any recommendations, I'd really appreciate them!

Dylan

Reply
Posts: 25
Eminent Member
Joined: 15 years ago

hi,
log in with engineers code and cleat table tracking area, that will solve the problem?
where are you based?

Reply
Posts: 8
Topic starter
Active Member
Joined: 14 years ago

It's fixed! Sort of.

I was changing the maximums for track lines, and I think when it shuffled the RAM, my table map problem was fixed.

j3dl3wis, when you spoke of clearing the table tracking area, is that the "Initialize Tracking Data" engineers program? I tried to do that, and the machine did a dull beep when I tried to press enter. Was I trying to do the wrong thing? Or is there something I'm missing?

Thanks for all your advice

Dylan

Reply
Page 1 / 2
Share: