Modbus rtu to Lontalk interface

[ddcme]

I need to interface a honeywell modbus module on a Cleaver Brooks boiler to a lontalk link on a Tracer Summit BCU. I am using a Controls Solutions "Babel Buster" gateway which needs to be programmed. Has anyone ever done this,if so do you have a config file or advice on how to accomplish it?

[lonboy]

I'd use an iLON100 which has the Modbus datapoint drivers built-in.
Cheers,
lb

[ORCA_GUY]

I was going to use a babel buster but decided not too. I would be curious to know what you think of it when your done. Instead of the babel buster I used a device from Loytec....great support!!! Let me know how the babel buster works out.

[misternorth79]

In the past, I've used FieldServer gateway products to take anything into Lon or BACnet. The Modbus and LON sides of FieldServer are pretty solid and have worked well for me on some sites.

However, one thing I do know is that the Babel Buster is a relatively cheaper solution that the smallest FieldServer gateway (x20). I'd be interested in hearing about your experience with the Babel Buster. Price is attractive...

[choosewisely]

The BabelBusters are pretty easy to use.
The trick is to download the free configuration utility from their website.

The downside of the BabelBuster is the fact that is can only read/write a total of 42 modbus points (because of the 64 nv limit)

I've used them in about 10 different systems now and they always work

They are cheap enoug h, you should just buy one and test it out

[sysint]

....The downside of the BabelBuster is the fact that is can only read/write a total of 42 modbus points (because of the 64 nv limit) The ilon 100 doesn't have a variable restriction like this.

[choosewisely]

The BabelBuster is smaller than an iLon100.


I took me a few minutes to think of a reply that Sysint couldn't argue easily;)

For a system where you only have to pick up a few points (like a Emg generator, or ATS) it works fine

Anyway, as far as the point count limitation, that's why I listed it as a downside
The fact is that the BabelBuster has a fixed .xif
and all of the Lonworks snvts are visible (even if they are not mapped to a valid Modbus address)


Sysint,
What's it called when a lonworks device supports a variable .xif?
isn't that called a MIP interface (or something like that)?

And what allows a lonworks device to support more than 64 nvs? Is it a different type of chip or something else


Thanks

[joey791]

This might sound wierd but I believe you can also do that with an Exor Epad

http://www.exor-rd.com/bin/site/templates/splash.asp?NC=229X

[sysint]

The BabelBuster is smaller than an iLon100......What's it called when a lonworks device supports a variable .xif?
isn't that called a MIP interface (or something like that)?

And what allows a lonworks device to support more than 64 nvs? Is it a different type of chip or something else
It is smaller... I just mention the ilon because of the anti-LON crowd that oftentimes erroneously claims this IS a restriction. It is simply a choice. Companies like Semco and Tekmar have been lied to about this. (unless they lied to me when I've asked about it)

As far as a name for a variable XIF? I don't know it would have a name as to me all XIF files could be "variable".

If you want to still use a Neuron you can increase the variable count to 4096 if you only use it as a communication processor and add a co-processor for the application. Echelon does have the MIP for this. They also have their short stack when utilizing an ARM processor. However, I think they have dumped support for this and my personal experience with a third party product designed this way was a complete disaster.

A company like Loytec isn't using the Neuron, so you would have to research their platform to see what they do for their large variable counts.

[choosewisely]

OK, Thanks Sysint.

My question was poorly stated.

What I really meant was, it seems like we get two types of lon devices

type 1:
Rigid in XIF strucure (from the installers point of view)
Fixed application (although configuration options can adjust how application works)
Any NVs that can be defined are already defined
only supports a max of 64 NVs

Example: BabelBuster

type 2:
XIF file is created dynamically inside the device (depending on how it is configured)
Can hold a custom application (usually needs it's own software to create application)
NVs are defined as needed
Supports more NVs than 64

Example: Fieldserver


And I had heard the term MIP interface applied to a couple of devices of type 2


Anyway your answer cleared this up for me, thanks

It all depends on what the product develper whats the end device to end up costing

[sysint]

It all depends on what the product develper whats the end device to end up costingThat's it. A company like Functional Devices isn't going to use a MIP (or similar) with a co-processor for a relay. That's a little extreme. I don't think anyone using an ASC controller sees the need for more than just working with a Neuron.

That being said your Babel buster should be fractional in cost compared to the Fieldserver or the ilon100.

[choosewisely]

The BabelBusters are around $320 each.

I know thats fractional compared to a Fieldserver

It's probably 1/2 of what an Ilon100 costs