Questions about FF-HSE development

[netto]

We have interest in buying the AT-442 product, so we would like to receive
some information about it.

We will develop a HSE device, so we are particularly interested in the
“sample HSE stack source code for building an HSE Field Device, Example HSE
Field Device, HSE Design Example (provides design information for example
HSE Field Device), C Header Files for HSE Structures and Messages, and
License”.

Our doubts are the following:

1) Does this sample code refers to a complete implementation, including
features like:
- the complete Foundation Fieldbus stack?
- port and device redundancy?
- function blocks development?

2) Can this code be used in an embedded processor? In this case, which are
the minimum requirements? We would like to know if we can use a hardware
module already available for us, with the following features:
- AMD 80186ER-50 processor (50 MHz)
- 512 kbytes RAM (1 wait cycle)
- 512 kbytes Flash Eprom (1 wait cycle)
- two LAN91C111 Ethernet controllers, 10/100 Mbps

3) Do we need a RTOS? Which are the features this RTOS must have? Do you
recommend some specific RTOS?

4) We have a generic doubt about HSE devices. H1 devices can communicate
using scheduled (compel data) and unscheduled (client/server, event report)
methods. Can HSE devices use scheduled communication as well? We heard that
HSE doesn’t have the LAS function, so it is not clear for us some things
like:
- can HSE devices have function blocks running cyclically? Who schedule when
they run?
- can HSE devices publish data cyclically? Who will schedule when this
happens?
- for publishing data cyclically, is it absolutely necessary to have
function block instantiated in a HSE device? Or are there other methods to
publish data cyclically without having function blocks?
- take an HSE OPC server as an example. Does it appear in the “system
configuration”? Can the OPC server run scheduled communication, or only
unscheduled?

[Talon Petty]

Good day to you

We will have one of our technical engineers respond to your request
shortly.

Joe Conklin
Fieldbus Foundation Marketing

[Denise Lloyd]

Netto,

Thank you for your interest in the AT-442. In response to your questions:

1) The Fieldbus Foundation does not sell full stacks, the sample is not a complete implementation. If you are interested in purchasing a stack, we have a list of member companies that do on our website. To find it, go to http://www.fieldbus.org/ProductsAndServices/MemberProductsCatalog/ and search for Product Development.

2) Stack system requirements will depend on the manufacturer, so you'll need to contact them about this.

3) Are you asking about an RTOS for the device or for the computer running the Hse Analyzer Toolkit? The toolkit runs on a Windows® 98/Me/2000/NT/XP platform.

4)Yes, HSE devices can do both scheduled and unscheduled communication. They can run and publish data cyclically using a configured function block schedule downloaded to the device during loop configuration. If you want some more detailed information on how this works, please look at the specification HSE System Management FF-589-1.3 section 2.5.

To maintain interoperability, FF function blocks are implemented in all field devices.


Again, thank you for your interest. I hope this has answered your questions. If you have any more inquiries, please contact us again.

Denise Garvey
Product Specialist, Fieldbus Foundation