XBS uppgrade to EBI Honeywell

[digo]

Also, I'd like to see what you are doing with 120 devices on your channel. Heck I'd like to see what you are doing with 60.

Here's one with 74 devices, counting the router and the JACE - which happens to be a 403 (slow).
Rename "network summary.doc" to .zip
There are 3 reports in txt format (unckeck word-wrap in notepad)

network summary.txt - Device/Channel/Address/NeuronId
transmission errors.txt - Transmit/Timeout/ReceiveFull/LostMsg/MissedMsg
net mgmt symmary.txt - all proxy points, and links.

Merry Christmas.

[sysint]

Thanks--
That's not 60 devices per channel though... You have 2 cards in this one?

[digo]

Thanks--
That's not 60 devices per channel though... You have 2 cards in this one?

It's a 403 - there's only one lon card. The devices are evenly split among 2 TP/FT-10 channels. I'm using an LPR-10 setup as a configured router.

[sysint]

Got it thanks.

[leaflying]

It's fine to compare a true LNS client software package with Tridium solution. But EBI is a bad example. Have you seen a LNS client providing NO network management functions?

[Droshi]

Hi guys, this thread is interesting to me because I am in a similar situation as the OP.

We are looking to upgrade from an old XBS version to something new and have not set our minds to what it should be yet. The obvious choice from a non-technical standpoint is to go with EBI, but limitations you are mentioning may or may not be a problem for our project. Obviously it seems we can be assured that EBI will work as a direct upgrade, but performance is something I don't want to see suffer just for convenience in the short-term.

I have mostly XL500 controllers as well as MC's and VAV controllers for that side of things. As old hardware is starting to degrade, it's becoming increasingly important for us to upgrade (at least by replacing the hardware with BNA type adapters). But we also don't want to jump into a terrible solution, the "Windows ME" reference sure made me shudder (I'll be the guy using this!).

If anyone has the time and would like to pm me about the size of our facility and more specifics that would be much appreciated, but I figured I would post here to avoid creating separate threads.

Thanks for any help!

(edit) Just to add, everything is on C-Bus and connected to 5 separate computers which then is combined by a shared database through the network by XBS currently.

[Sazor]

Did you know that XBS 1.7 supports BNA's? (it could be the first step in your upgrade)

[Droshi]

We have XBS 1.6 and it has room for BNA communication, but during testing it had reliability issues for us (stopped working after a couple weeks). Whereas EBI and the BNAs were more stable. Uninterruption to our controls is of importance so we would like to be sure as we move from stage to stage that things will be stable.

[T87F]

There is no tool to directly convert an XBS database into an EBI database.

However, there are ways to make the job easier....
What controllers are you using? (eg. XL5000 series - if so import CARE software into EBI quickbuilder)

All graphics, will need to be redrawn (XBS used designer 3.1 - EBI uses HMI Web builder)

The XBS database CAN be converted to EBI using the CDI tool, it works just fine. BNA's with EBI work well together, there speed is dependent on the C-Bus baud rate.

[tuncos]

The XBS database CAN be converted to EBI using the CDI tool, it works just fine.

Where is this CDI Tool found?

Is it part of EBI only?

[T87F]

Where is this CDI Tool found?

Is it part of EBI only?

It is not part of EBI, it is a seperate software tool from Honeywell.

[tuncos]

How can I get this tool? Is it only available to the branches?

[tuncos]

It is not part of EBI, it is a seperate software tool from Honeywell.

OK then, how /where did you get this CDI Tool?

I'm in the Honeywell Applied Market and have never heard of this software. I'm wondering if it's for the branches only.

Thanks.