Page 1
078-0140-01G Provides reference info for writing programs using the Neuron C programming language. Neuron C Reference Guide
Reference manual for the Neuron C Version 2.3 programming language, document number 078-0140-01G. Describes ANSI C extensions for developing LONWORKS applications on Neuron Chips and Smart Transceivers, with distinctions for host-based device model files. Covers predefined events, compiler directives, built-in and library functions, timers, network variables, configuration properties, message tags, functional blocks, built-in objects, syntax, and reserved keywords. A companion to the Neuron C Programmer’s Guide.
The first 5 pages, shown as text so search engines and readers can find this document.
078-0140-01G Provides reference info for writing programs using the Neuron C programming language. Neuron C Reference Guide
Echelon, LONWORKS, LONMARK, NodeBuilder, LonTalk, Neuron, 3120, 3150, ShortStack, LonMaker, and the Echelon logo are trademarks of Echelon Corporation that may be registered in the United States and other countries. Other brand and product names are trademarks or registered trademarks of their respective holders. Neuron Chips and other OEM Products were not designed for use in equipment or systems, which involve danger to human health or safety, or a risk of property damage and Echelon assumes no responsibility or liability for use of the Neuron Chips in such applications. Parts manufactured by vendors other than Echelon and referenced in this document have been described for illustrative purposes only, and may not have been tested by Echelon. It is the responsibility of the customer to determine the suitability of these parts for each application. ECHELON MAKES AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY OR IN ANY COMMUNICATION WITH YOU, AND ECHELON SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Echelon Corporation. Printed in the United States of America. Copyright © 2006, 2014 Echelon Corporation. Echelon Corporation www.echelon.com
Welcome This manual describes the Neuron® C Version 2.3 programming language. It is a companion piece to the Neuron C Programmer's Guide. It provides reference information for writing programs using Neuron C. Neuron C is a programming language based on ANSI C that is designed for applications that run on Neuron Chips and Smart Transceivers (Neuron-hosted devices). Neuron C includes network communication, I/O, and event-handling extensions to ANSI C, which make it a powerful tool for the development of LONWORKS® applications. A subset of the Neuron C language is also used to describe the interoperable interface of host-based applications that are designed with the ShortStack® Developer’s Kit, FTXL™ Developer’s Kit, or the i.LON® SmartServer. This interoperable interface is contained within a file called a model file, which contains Neuron C declarations and definitions for the device interface. This guide focuses on the Neuron C language used for Neuron-hosted application development, and only highlights differences for model file compilation where necessary. Audience The Neuron C Programmer’s Guide is intended for application programmers who are developing LONWORKS applications. Readers of this guide are assumed to be familiar with the ANSI C programming language, and have some C programming experience. For a complete description of ANSI C, consult the following references: • —. 1989. American National Standard for Information Systems Programming Language C. Standard number X3.159-1989. New York, NY: American National Standards Institute. • —. 2007. International Standard ISO/IEC 9899:1999. Programming languages – C. Geneva, Switzerland: International Organization for Standardization. • Harbison, Samuel P. and Guy L. Steele, Jr. 2002. C: A Reference Manual, 5th edition. Upper Saddle River, NJ: Prentice Hall, Inc. • Kernighan, Brian W. and Dennis M. Ritchie. 1988. The C Programming Language, 2nd edition. Upper Saddle River, NJ: Prentice Hall, Inc. • Plauger, P.J. and Jim Brodie. 1989. Standard C: Programmer’s Quick Reference Series. Buffalo, NY: Microsoft Press. • Plauger, P.J. and Jim Brodie. 1992. ANSI and ISO Standard C Programmer's Reference. Buffalo, NY: Microsoft Press. Related Documentation The following manuals are available from the Echelon Web site (www.echelon.com) and provide additional information that can help you develop Neuron C applications for LONWORKS devices: Neuron C Reference Guide iii
• Introduction to the LONWORKS Platform (078-0391-01A). This manual provides an introduction to the ISO/IEC 14908 (ANSI/CEA-709.1 and EN14908) Control Network Protocol, and provides a high-level introduction to LONWORKS networks and the tools and components that are used for developing, installing, operating, and maintaining them. • I/O Model Reference for Smart Transceivers and Neuron Chips (078- 0392-01C). This manual describes the I/O models that are available for Echelon’s Smart Transceivers and Neuron Chips. • IzoT Commissioning Tool User's Guide (078-0514-01 ). This manual describes how to use the Izot Commissioning Tool to design, commission, monitor and control, maintain, and manage a LONWORKS network. • LONMARK® Application Layer Interoperability Guidelines. This manual describes design guidelines for developing applications for open interoperable LONWORKS devices, and is available from the LONMARK Web site, www.lonmark.org. • Neuron C Programmer’s Guide (078-0002-01I). This manual describes how to write programs using the Neuron C Version 2.3 programming language. • Neuron Tools Errors Guide (078-0402-01D). This manual documents and explains the various warning and error messages that can occur for the various Neuron C development tools. • IzoT NodeBuilder FX User’s Guide ( 078-0516-01). This manual describes how to develop a LONWORKS device using the IzoT NodeBuilder tool. All of the Echelon documentation is available in Adobe PDF format. To view the PDF files, you must have a current version of the Adobe Reader, which you can download from Adobe at: www.adobe.com/products/acrobat/readstep2.html. Typographic Conventions for Syntax Table 1 lists the typographic conventions used in this manual for displaying Neuron C syntax: Table 1. Typographic Conventions Typeface or Symbol Used for Example boldface type keywords literal characters network { italic type abstract elements identifier [square brackets] optional fields [bind-info] iv
Typeface or Symbol Used for Example | vertical bar a choice between two elements input | output Example: The syntax for declaring a network variable is: network input | output [netvar modifier] [class] type [bind-info] identifier • You type the keywords network, input, and output as shown • You replace the abstract elements netvar modifier, class, type, bind-info, and identifier with the actual modifier, class, type, bind information, and identifier for the network variable • The declaration must include either input or output, but not both • The elements netvar modifier, class, and bind-info are all optional When a particular element or expression includes punctuation, such as quotation marks, parentheses, and semicolons (but not including square brackets and vertical bars), you must type that punctuation as shown. Code examples appear in the monospace Courier font: #include <mem.h> unsigned array1[40], array2[40]; // See if array1 matches array2 if (memcmp(array1, array2, 40) != 0) { // The contents of the two areas do not match } Neuron C Reference Guide v
Doxxly editorial guide
This guide helps you understand the scope of Neuron C Reference Guide before or alongside reading the original document. It is based on the catalogue record, credited creator, source, classification and topics shown on this page. It does not replace the original work and does not invent claims about passages that Doxxly cannot verify.
Neuron C Reference Guide is a 285-page documentcredited to Ada Q. Underhill. Reference manual for the Neuron C Version 2.3 programming language, document number 078-0140-01G. Describes ANSI C extensions for developing LONWORKS applications on Neuron Chips and Smart Transceivers, with distinctions for host-based device model files. Covers predefined events, compiler directives, built-in and library functions, timers, network variables, configuration properties, message tags, functional blocks, built-in objects, syntax, and reserved keywords. A companion to the Neuron C Programmer’s Guide. It appears in the Technology & Security collection, which groups it with other material that readers may use for comparison and further study.
The item can be approached in several ways. A reader looking for a quick orientation can begin with the free five-page preview, inspect the page structure and use the metadata to judge relevance. Someone undertaking deeper research can work through the complete file, search its indexed text, record useful page references and compare its treatment of Neuron C, Programming reference, LONWORKS, Neuron Chips, Smart Transceivers, Compiler directives, Event-driven programming, Network variables, Configuration properties, Functional blocks with the related resources linked below.
Rather than reducing the work to a single claim, this page treats it as a source that should be read in context. The title, creator, publication source, licence and format all help explain what kind of evidence it may offer. Readers should distinguish the original author's statements from Doxxly's catalogue description, and should cite the original edition when using the material in academic, professional or published work.
The catalogue connects this document with Neuron C, Programming reference, LONWORKS, Neuron Chips, Smart Transceivers, Compiler directives, Event-driven programming, Network variables, Configuration properties, Functional blocks. These terms offer practical entry points rather than a substitute for close reading. Start by identifying the definitions, examples, arguments, tables or visual explanations attached to each topic. Then note where the creator draws connections, makes distinctions or moves from background material to a conclusion, recommendation, calculation or narrative development.
A useful reading method is to separate description from interpretation. First record what the item actually presents: names, headings, figures, formulas, quotations or stated propositions. Next consider why those details matter within the whole work. Finally compare them with another source from the same subject area. This process helps turn a long digital file into evidence that can be evaluated rather than merely skimmed.
The following is an editorial content guide based on the verified catalogue topics. It is not represented as the original author's formal table of contents. Use it to organise notes while moving through the 285 pages in the player.
Use this section of the reading guide to identify how Neuron C appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Programming reference appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how LONWORKS appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Neuron Chips appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Smart Transceivers appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Compiler directives appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Event-driven programming appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
Use this section of the reading guide to identify how Network variables appears in Neuron C Reference Guide, note important terms, and connect the subject to the wider purpose of the work.
When a heading in the original differs from this guide, follow the original heading in your citation. Page numbers can also vary between editions. Doxxly's direct page field is useful for navigation, but formal references should include the title, creator, source and edition details available in the file itself.
Doxxly credits Ada Q. Underhill as the author or creator of Neuron C Reference Guide. This page does not add an unverified biography, job title or institutional affiliation. The attribution is preserved so readers can distinguish the creator from the hosting library and follow the original record when an external author link is available.
Author context matters because a work reflects a particular purpose, audience and point of view. Before relying on the material, consider what the creator set out to explain, when the source was produced and whether later research or revised guidance should also be consulted. For literature and philosophy, compare translations and editions; for technical material, check whether a newer version has superseded the one shown here.
The recorded source for this item is renesas.com. Doxxly provides access and discovery tools but does not claim to be the original publisher unless explicitly stated. Source links, creator attribution and the recorded Publicly available file collected for editorial review licence are displayed to help readers assess provenance and permitted use.
Provenance is especially important for reports, standards, presentations and working spreadsheets. Check the original source for amendments, supporting files and current policy. A trustworthy research workflow keeps the source URL with any notes or downloaded copy, verifies important figures against the original, and avoids treating an archived document as automatically current.
Visit renesas.comBegin with the title and opening pages, then use the guide above to decide whether to read sequentially or move to a particular topic. The Doxxly player provides previous and next navigation, a direct page field, zoom steps, fit-to-width and fit-to-page modes, rotation and fullscreen. These controls are useful when a page contains small type, a wide table, an image, a scanned layout or a dense sequence of notes.
The first five pages are open to every visitor. A plan unlocks the complete item and full-document search. Search is best used for distinctive names, technical terms or short phrases; broad words can produce too many possible contexts. When you find a useful passage, read the surrounding pages so that a sentence, chart or formula is not separated from its explanation.
If downloading is enabled, members can obtain the original PDF file. Keep the original format when formulas, slide sequencing, pagination or layout carries meaning. Respect the Publicly available file collected for editorial review terms displayed on this page, and use the rights-report link if you believe the attribution or availability needs review.
As you read Neuron C Reference Guide, ask which audience the creator addresses, what problem or idea organises the work, what evidence is presented, and which assumptions remain unstated. Note whether important terms are defined consistently and whether examples represent a broader pattern or a narrow case. For quantitative material, record units, time periods, formulas and data sources. For interpretive material, separate the creator's language from your own summary.
A second set of questions concerns relevance today. Which parts remain durable, which depend on their historical or institutional setting, and what would need confirmation from a newer source? Following the tags and the Technology & Security collection can reveal useful comparisons. Agreement between sources can strengthen confidence, while disagreement can point to changing definitions, methods, evidence or priorities.
Finally, decide what you need from the item: background knowledge, a quotation, a worked example, a model, a visual explanation or a starting bibliography. That purpose should guide the depth of reading and the notes you keep. Doxxly helps locate and navigate the source; careful interpretation remains the reader's responsibility.
Practical answers about reading, downloading and understanding this document on Doxxly.

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology

National Institute of Standards and Technology