Flexible graphical extension engine

• US 8,239,500 B2
• Filed: 10/22/2008
• Issued: 08/07/2012
• Est. Priority Date: 10/22/2008
• Status: Active Grant

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Pouchak, Michael Andrew
• Primary Examiner(s): NGUYEN, MINH CHAU
• Application Number:
  US12/256,444
• Publication Number:
  US 20100100583A1
• Time in Patent Office: 1,385 Days
• Field of Search: 709220-223, 709/203
• US Class Current: 709/220
• CPC Class Codes: H04L 2012/40247 LON
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A flexible graphical extension engine having a function block engine combined with extensions in communications with a wall module bus to make it possible to provide fixed function, configurable function and programmable function devices which implement additional function block behavior, and provide an automated configuration approach for generating configuration files for a programmable wall module. In other words, the engine not only depends on fixed inputs and outputs (I/O'"'"'s) and fixed features in a control solution, but also may allow for flexible blocks and the ability to change an interface on the fly (i.e., during operation).

Claims

1. A graphical extension engine comprising:

a configuration tool;

a download tool connected to the configuration tool;

a host connected to the download tool; and

a client connected to the host; and

wherein;

the host is a function block engine platform comprising a first function block engine; and

the client is a configurable wall module comprising at least one second function block engine; and

wherein each of the first and second function block engine includes;

one or more function block execution modules;

a block execution list including references to at least one of the one or more function block execution modules, and public variable references to a function block variable space;

an input configuration to configure inputs for use by each function block engine in the function block variable space;

an input convert module to execute the input configuration;

an output configuration to configure outputs of the function block engine in the function block variable space;

an output convert module to execute the output configuration;

the first function block engine has a first public variable identification (PVID) system;

the second function block engine has a second PVID system;

PVID'"'"'s of signals from the first function block engine to the second function block engine, are converted to PVID'"'"'s of the second function block engine; and

PVID'"'"'s of signals from the second function block engine to the first function block engine, are converted to PVID'"'"'s of the first function block engine.

2. The engine of claim 1, wherein the configuration tool comprises:

a bus tool;

a project file mechanism connected to the bus tool; and

a graphical compiler connected to the project file mechanism and the bus tool.

3. The engine of claim 2, wherein the download tool is for conveying a configuration from the configuration tool to the host for the client.

4. The engine of claim 3, wherein the configuration can be conveyed by the download tool on-the-fly.

5. The engine of claim 1, wherein:

the host can convey the configuration to the client; and

the function block engine of the host can affect the configuration on-the-fly.

6. The engine of claim 1, wherein:

the host is connected to the download tool via a first bus; and

the client is connected to the host via a second bus distinct from the first bus.

7. A parallel flexible graphical extension engine comprising:

a first function block engine;

a configurator for providing files to the first function block engine; and

at least one wall module that includes a second function block engine connected to the first function block engine; and

wherein each of the first and second function block engines includes;

one or more function block execution modules;

a block execution list including references to at least one of the one or more function block execution modules, and public variable identifications (PVID'"'"'s) relative to a function block variable space;

an input configuration to configure inputs for use by the function block engine in the function block variable space;

an input convert module to execute the input configuration;

an output configuration to configure outputs of the function block engine in the function block variable space;

an output convert module to execute the output configuration;

the first function block engine has a first public variable identification (PVID) system;

the second function block engine has a second PVID system;

PVID'"'"'s of signals from the first function block engine to the second function block engine, are converted to PVID'"'"'s of the second function block engine; and

PVID'"'"'s of signals from the second function block engine to the first function block engine, are converted to PVID'"'"'s of the first function block engine.

8. The engine of claim 7, wherein the first function block engine is for sending group tables and send tables to the wall module.

9. The engine of claim 8 wherein the wall module has fixed function block I/O'"'"'s and flexible function block I/O'"'"'s.

10. The engine of claim 9, wherein the flexible function block I/O'"'"'s may be changed on the fly.

11. The engine of claim 9, wherein the fixed function block I/O'"'"'s are selectable.

12. The engine of claim 8, wherein the tables are sent via a two-wire polarity insensitive or wireless bus.

13. The engine of claim 8, wherein the send table comprises at least one of:

a group number,

function block destination PVID'"'"'s;

wall module PVID'"'"'s; and

own PVID'"'"'s.

14. The engine of claim 8, wherein the at least one wall module has a PVID different from the PVID of the first function block engine for a given parameter.

15. The engine of claim 8, further comprising an approach for tracking connections between node PVID'"'"'s including PVID source addresses, PVID destination addresses, node source and destination addresses and optional update rates.

16. The engine of claim 7, wherein one or more function block execution modules of the first function block engine are connected to the at least one wall module.

17. The engine of claim 7, wherein the wall module comprises:

a display;

inputs connected to the wall module bus; and

outputs connected to the wall module bus; and

wherein signals on the inputs and outputs have PVID'"'"'s.

18. A method for configuring a wall module comprising:

providing a configuration for a configurable wall module;

downloading the configuration to a host comprising a first function block engine; and

downloading the configuration from the host to the wall module, the wall module comprising a second function block engine; and

wherein each of the first and second function block engine includes;

one or more function block execution modules;

a block execution list including references to at least one of the one or more function block execution modules, and public variable references to a function block variable space;

an input configuration to configure inputs for use by the function block engine in the function block variable space;

an input convert module to execute the input configuration;

an output configuration to configure outputs of the function block engine in the function block variable space;

an output convert module to execute the output configuration;

the first function block engine has a first public variable identification (PVID) system;

the second function block engine has a second PVID system;

PVID'"'"'s of signals from the first function block engine to the second function block engine, are converted to PVID'"'"'s of the second function block engine; and

PVID'"'"'s of signals from the second function block engine to the first function block engine, are converted to PVID'"'"'s of the first function block engine.

19. The method of claim 18, wherein:

the first function block engine has fixed and/or flexible I/O'"'"'s; and

the second function block engine has flexible I/O'"'"'s, fixed I/O'"'"'s, or both flexible and fixed I/O'"'"'s.

20. The method of claim 19, further comprising:

defining customized I/O'"'"'s for the wall module;

selecting fixed I/O'"'"'s as desired for the wall module; and

defining virtually any number of I/O'"'"'s for the wall module.

21. The method of claim 18, wherein the wall module can have fixed algorithms, configured or programmable flexible function block engine algorithms, or both fixed and configured or programmable flexible function block engine algorithms.