The Zero3 XLT is a powerful interface to your existing controller. There are numerous potential benefits and implementation possibilities. Something this big generates a great many questions! Please contact us if you don't see your issue addressed here.



  • Q: “What’s needed to connect the XLT package?”
    •
  • A: There are three possible methods: First, the package can go on the in-store private network. Then a VPN or bridge is installed at company headquarters. Second, a DSL line can usually be installed in the store. Third, we have a cellular ethernet modem available that avoids all wiring issues. One way or another, we can get you on the net. Short of that, installation requires sticking the XLT on the wall, and pushing an on-screen button to learn the site’s system, and doing a small sketch of the floor plan for that site (Optional).


  • Q: “What Legacy Systems does the XLT support?”
    •
  • A: The ComTrol 5000/4000 series. The CPC RMCC. The Danfoss EIL. The Danfoss ZX/NC25, CPC Einstein, Altech’s XPert systems, a BacNet translator, and others are all in various states of progress and testing, as are the Scottish Honeywell Elm and Germanys Linde-Eckelman. Others will be added as business requires. It is entirely possible that future versions of controllers from some manufacturers will come with the XLT protocol built in, making them even easier to put on our network.


  • Q: “What’s securing my Corporate network if I allow you to pass through it to your equipment?”
    •
  • A: The XLT goes on the in-store private network. Then a VPN or bridge is opened at company IT headquarters, pointing to the SERVER at ACIWebs in Blacksburg, VA, on the campus at Virginia Tech. In point of fact, this method is also the most secure. As we stated earlier, the XLT does NOT do it’s own web screens. It only provides raw data from the Legacy machines. So when a technician calls up Site123 to look at the Ice Cream case, he’s not actually talking to Site123; He’s talking to the SERVER at ACIWebs, which is building his requested web screens according to the data the SERVER gets from the Site123 XLT. The ONLY computer that’s allowed to talk to Site123’s XLT is the SERVER at ACIWebs itself, not the eventual client. The VPN will only allow incoming messages from that one IP address, and only to the specific port designated. Any request from any other address or port is rejected. The protocol flowing over this connection is very directed, and does not allow excursion into operating systems or redirection. The possibility of hacking a system like this is vanishingly small.


  • Q: “What technique(s) does the XLT use to communicate with my existing controllers?”
    •
  • A: The XLT communicates via Teletype, Terminal or Protocol interfaces. This is better explained on our Translation page.


  • Q: “Isn’t Screen Scraping Obsolete?”
    •
  • A: Yes it is, but it works just fine. So are the Legacy Control Systems that it’s used with, but they work just fine. The advances in supermarket control systems came long before the advances in communications. The funny thing about the word ‘Obsolete’ is it means there is something newer available, not necessarily something better.


  • Q: “What if Legacy Manufacturers change screen software?”
    •
  • A: Just how many times has that happened in the last 10 years? And why would you allow them to change it if the equipment in place does a proper job. But just in case there is some good reason for such a change, the Screen Scraper can be updated just as easily, if not much more so, than the Screen software itself.


  • Q: “What if the Legacy Manufacturer changes the protocol?”
    •
  • A: The same answer applies as in the prior question. The protocol may be added to, in which case we’ll add to our translator. But, changing their prior standard would be a very costly and foolish thing, since all their users would have to change to new communication software. Finally, if the remote lightning does strike, the XLT can be uploaded with a new translator in about 30 seconds per site.


  • Q: “What about interfacing to new Controller models?”
    •
  • A: Again, with true neutrality, we can do a new translator for the new ‘Legacy’ equipment, usually before it ever really hits the market. It is entirely possible that future versions of controllers from some manufacturers will come with the XLT protocol built in, making them even easier to put on our network.


  • Q: “What about differences in operations of Legacy types?”
    •
  • A: An example: What Com-Trol calls ‘Ambient Modified’ operation of Condensers, CPC calls ‘TD’ operation. But the setpoints and approaches are similar enough to make common data easy. (We called it ‘TD’). When there are real differences, the protocol and screens provide for either/or displays and data.


  • Q: “Is there more?”
    •
  • A: The XLT can provide structured answers to queries about your entire chain, in minutes. For instance, if you would like to know which stores, if any, have case probes in override, simply select the info you want on the Chain Query page, and hit submit. Within 5-10 minutes, you will receive an e-mail with a readable report on the results.


  • Q: “Any more?”
    •
  • A: The XLT can provide structured commands to all your stores as well. When the original legacy systems were installed, no-one thought being rigid about task names was critical. However, today, if we wish to alter the schedule for all parking lot lights, we need an operator to look at each task in each store to resolve issues such as the difference between “Parking Lot” and “Outside Lights”. With the XLT, during set-up, the installer optionally adds a number identifier to each task. So when we go out to add a half hour to each parking lot task, the system searches for #900 tasks, not by name.


  • Q: “Yeah, I get it, but what about...?”
    •
  • A: The XLT can do much more than we have already thought of. Let us know what you want, and we can probably do it.