Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Radiant Auto Loader

Status
Not open for further replies.

soustech

Technical User
Apr 25, 2012
14
US
Were running Aloha Table Service Version 6.4.37

Last night our BAR POS Terminal which is usually the Master began rebooting and would stop at the Radiant Auto Loader screen.

It would say Terminal Configuration in Progress and then show
a progress bar labeled Requesting Configuration.

However, it never was able to complete the configuration and would eventually display a RAL Communication Error Popup dialog box, with the choices Abort / Retry / Ignore.
RAL Version is having difficulty reaching the BOH Server.
The Terminal Might Have to be Rebooted.

Rebooting just looped the same error conditions

Choosing Retry just continued the failure(loop)
Choosing Ignore would open up another failure window
Choosing Abort would LET THE SYSTEM CONTINUE.

If I choose Abort all appears to be working. But naturally I have my concerns about what is causing this problem.

1. What is the Radiant Auto Loader?
2. Is it necessary?
3. How do I configure it?
4. How can I figure out why it thinks it's not communicating witht he BOH Server when it is. EDC and all work and they need to communicate to the BOH Server so why is RAL having a problem.

Where is their a dealer / end user manual or guide that explains RAL?


Thanks as always.
SOUSTECH
 
Abort / Retry / Ignore
Dialog Popoup Window Reclarification

Choosing Retry just continued the failure(loop)
Choosing Ignore would REBOOT the systemChoosing Abort would LET THE SYSTEM CONTINUE.

Allowing one to use the POS Terminal. However, since this is the terminal that we would like to be the Master the only way to accomplish this is to shut down the other terminals until after this one is fully booted up. Then start the other terminals. A big pain if you should have to Recycle or Refresh during a busy period for some reason.

Thanks Again

 
Having now moved the Bar Terminal (001 Bar ) back to the bar and telling the system to IGNORE the RAL error and continue I now find were having difficulty with the Cash Drawer opening.

We use the standard Radiant MS Cash 16" drawer with the direct connect RJ11-RJ12 connectors plugging into the Cash Drawer connectors on the terminal.

I have the BOH Server Configured thusly

Aloha Manager - Maintenance - Hardware - Cash Drawers

Under Drawer type select OPOS

On the right side of the screen - select the opos driver RSDirectDC1


The Drawer cable must be a OPOS - not printer driven.

Still I get an error messgage that the Terminal cannot access or communicate to the Cash Drawer.

1. Is it possible that this failing RAL configuration is not letting the Cash Drawer work.


2 Am I using the correct terminology for the right side of the screen RSDirectDC1
or should it be something similar or with periods?

Thanks again
SOUSTECH
 
Figured out the CASH DRAWER problem.
On the right side of the Cash Drawer Maintenance Menu
under the subcategory OTHER INTERFACES ....
the OPOS data field has to say either ...
RSDirect.CD1 or RSDirect.CD2It's very important to have that period "." between the RSDirect and CD#

I am still having problems however with that Radiant Auto Loader RAL Communication Error "Abort / Retry / Ignore"

Terminal Configuration in Progress...
Requesting Configuration
Current Task: Making UDP Calls to validate Configuration
Requesting Configuration

However, it never is able to complete the configuration and would eventually display a RAL Communication Error Popup dialog box, with the choices "Abort / Retry / Ignore".
RAL Version is having difficulty reaching the BOH Server.
The Terminal Might Have to be Rebooted.

Rebooting just loops the same error conditions
Choosing Abort would LET THE ALOHA SYSTEM CONTINUE.
Choosing Retry just continued the failure(loop)Choosing Ignore would REBOOT the system

Thanks again for anyones help
SOUSTECH
 
Soustech,

Check the aloha fileserver RAL software and see if that terminal is set for Reload. It sounds like your terminal is looking for the RAL software on the back office pc to pull the configuration.

In my opinion, RAL isn't the greatest. If you are still having issues, i would remove RAL from the terminal and just run TermInst on the terminal and let it load aloha using ibercfg.bat.

Knectech
 
Might also want to rethink your stance on that terminal being the master. I've seen way more superstition about such things than I would've believed possible from otherwise smart people. If it's the only terminal you have that was manufactured after 1990, then by all means, keep master status there. But if the hardware is the same or close to it at the other stations, let another terminal take over. That's what the failover capability is for.

J
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top