Defining incoming layer 2 packet buffers, Functions – Echelon LonTal Stack User Manual

Page 41

Advertising
background image

LonTalk Stack Developer’s Guide

29

Updated Symbol File

Destination Folder on

Development Computer

Source/Target/Neuron/L2ML

IB/ Ver14/sys3150l2mlib.sym

C:/LonWorks/Images/Ver14

Source/Target/Neuron/L2ML

IB/ Ver14/sys3150l2mlib.nx

C:/LonWorks/Images/Ver14

Defining Incoming Layer 2 Packet Buffers

You can define incoming Layer 2 packet buffers using the following syntax:

[length] [miCOMM|miINCOMINGL2] [backlog/altpath] NPDU [CRC_HI]
[CRC_LO]

The length field includes the 2 bytes before the NPDU, the NPDU itself, and the
two CRC bytes.

Functions

The following table describes the functions included in the l2mlib.h file that you
can use to create a custom network interface.

Function

Syntax

Description

l2ml_gol2()

extern system far void
l2ml_gol2(void);

Switches the network

processing to L2 mode. If it

is already in L2 mode, this
method does nothing. You

can return to the scheduler

when in L2 mode as the
network processor believes

there is no incoming traffic.

l2ml_gol5()

extern system far void
l2ml_gol5(void);

Switches the network

processing to L5 mode. If it
is already in L5 mode, this

method does nothing.

l2ml_getl2packet()

extern system far
unsigned
*l2ml_getl2packet(void);

Returns any L2 packet

buffers in the receive queue.

This method returns NULL
if there are no L2 packet

buffers available.

Advertising