RE: Possible pauses with xPLHAL

["Ian Lowe" <ian.lowe@xxxxxxxxxxxxxxxxxx>]

>From the xPL Protocol spec:

Heartbeat Messages
Heartbeat Messages should be sent by all devices on an xPL network (with
the exception of hubs). The heartbeats allow for configuration, health
monitoring, diagnosis of problems, and logging of events. The heartbeat
interval is defined by the developer, and may be anything from five
minutes to thirty minutes. There are two template heartbeat schemas
currently defined.

Small Devices, such as PIC Systems :
xpl-stat
{
hop=1
source=ACME-LAMP.LIVINGROOM
target=*
}
hbeat.basic
{
interval=[interval in minutes]
(...additional info defined by the developer)
}

PC Based Applications, using Ethernet:
xpl-stat
{
hop=1
source=XPL-XPLHAL.MYHOUSE
target=*
}
hbeat.app
{
interval=[interval in minutes]
port=[listening port]
remote-ip=[local IP address]
(...additional info defined by the developer)
}

It should be apparent to the reader that the .app heartbeat type is an
extension of the .basic type. Heartbeat messages must use one of these
schemas as a template. They may include additional elements within the
message body, however, the base elements must be present.

So, the heartbeat messages are ok! The additional port= and remote-ip=
are added to allow the PC Hubs to operate.

Ian.

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of Neil Wrightson
Sent: 21 July 2005 08:53
To: ukha_xpl@xxxxxxx
Subject: RE: [ukha_xpl] Possible pauses with xPLHAL

Hi Gregg,

My OSD is a RS232 device communication to xPLHAL via the xPLDEVCOM
component, so it does not know anything about port or remote-ip info.

I have an internal timer in my firmware that generates the heart beat.
In all other traffic I have seen using the xpl monitor in the manager, I
have not transmitted an extra heart beat.

Regards,

Neil Wrightson.


> -----Original Message-----
> From: Gregg Liming [mailto:gregg@xxxxxxx]
> Sent: Thursday, 21 July 2005 1:40 PM
> To: ukha_xpl@xxxxxxx
> Subject: Re: [ukha_xpl] Possible pauses with xPLHAL
>
>
> Neil Wrightson wrote:
>
> >Tony,
> >Not sure if this cut & paste will work or not but here goes.
> >
> >An example is at the end of this list but to save you some time
here
> >are two consecutive messages.
> >Note the Date Time stamp and the OSD Time of each message.
> >
> >
> Neil,
>
>     I don't know if this is related to your problem, but isn't your
> device's heartbeat message lacking some info (port and remote-ip)?
> That would definitely explain why you never got comms using mh's hub
> as it relies on the port info to know which port to rebroadcast on
> (for local hub listeners).  Also, from the log, I notice 2 in a row
> with the same time stamp--yet, the interval specifies 2 (minutes).
>
> Gregg
>
> ----------------------------------------------------------
> 20/07/05 17:32:15
>
> xpl-stat
> {
> hop=2
> source=nwe-mtlcd.123
> target=*
> }
> hbeat.basic
> {
> interval=2
> }
>
> ----------------------------------------------------------
> 20/07/05 17:32:15
>
> xpl-stat
> {
> hop=2
> source=nwe-mtlcd.123
> target=*
> }
> hbeat.basic
> {
> interval=2
> }
>
>
>
>
> xPL Links: http://www.xplproject.org.uk http://www.xplhal.com
http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx To Subscribe:
ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx