[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: xAP 1.3 and BSC 1.4(!?)
--------------050406030204030401000703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Kevin,
I'm happy to help try and revise xAP 1.3 then do either an addendum or,
my preference, a 1.4 BSC revision.
Is there a base Word doc?
I just had a look back to July but couldn't find a mail re xAP 1.3.
Yes, a menu structure schema would be useful for the displays. The next
iteration is a 128x64 which also
supports some primitive graphics. The new board has the great advantage
of more RAM on chip.
I'm also 50% though a hardware xAP to DMX bridge using the Wiznet
interface and a
PIC24F, which includes a listener facility so in some cases a mapper
isn't required (you assign a source UID to
a DMX channel/endpoint).
Regards,
Lehane
Kevin Hawkins wrote:
>
> Been away on hols Lehane - so only just seen this...
>
> There have a been a few posts re this on the lists but its woeful that
> we still haven't got a published xAP v1.3 spec. I only got one reply
> (from James) to my last direct email to everyone with the outline
> changes that I thought were in the spec :-( Having said that there
> are a lot of application out there now implementing xAP v1.3 and I
ahve
> tried to ensure with the developers thay they all meet the spec - or
at
> least my interpretation of it ;-) We do need to get this documented
> and published !
>
> Re BSC v1.4 - or at least an addendum to BSC1.3 to handle xAP v1.3
UID's
> - again we need to do this although I hope it's fairly obvious - you
> just need to cope with the longer UID's that xAP v1.3 supports.
> ID=xxxx ID=xxxxxx etc . In BSC v1.4 there has been the ongoing talk
> about a 'choice' device and Edward and I are both using his suggested
> way of implementing this - and it is in the released HouseBot plugin.
> We have not persued an actual menu structure type treatment of this -
> which is something that you might like for your switches, this
probbaly
> should be its own schema. I know IanB was looking at this.
>
> There are some clarifications we need to make to the existing BSC v1.3
> spec as it is ambiguous in some areas. I'm happy to work with you on
> this and the xAP v1.3 spec if you wish ??
>
> Kevin
>
> about Lehane Kellett wrote:
> > I've just been working on updating the LCD switch display to use
a
> > newer board. As part of this I added support for extended UID's
but
> > found there isn't a reference on the web. I guess this needs some
> > focus before we create mildly different variants in our code.
> >
> > In the same way, ID=xxxx needs adding to BSC and some clarity
added.
> >
> > I'm willing to have a go at BSC 1.4 for the extensions but what
else
> > needs adding or changing?
> >
> > Lehane
> > http://www.mm-wave.com/honeycottage/xaplcd2.htm
> <http://www.mm-wave.com/honeycottage/xaplcd2.htm>
for the display. I'll
> > add photos in the back box shortly.
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>
>
--------------050406030204030401000703
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Kevin,<br>
I'm happy to help try and revise xAP 1.3 then do either an addendum or,
my preference, a 1.4 BSC revision.<br>
Is there a base Word doc?<br>
<br>
I just had a look back to July but couldn't find a mail re xAP
1.3.<br>
<br>
Yes, a menu structure schema would be useful for the displays. The next
iteration is a 128x64 which also<br>
supports some primitive graphics. The new board has the great advantage
of more RAM on chip.<br>
<br>
I'm also 50% though a hardware xAP to DMX bridge using the Wiznet
interface and a <br>
PIC24F, which includes a listener facility so in some cases a mapper
isn't required (you assign a source UID to<br>
a DMX channel/endpoint). <br>
<br>
Regards,<br>
Lehane<br>
<br>
<br>
<br>
<br>
Kevin Hawkins wrote:
<blockquote cite="mid:492FFACC.8020809@xxxxxxx"
type="cite">
<div id="ygrp-text">
<p>Been away on hols Lehane - so only just seen this...<br>
<br>
There have a been a few posts re this on the lists but its woeful that
<br>
we still haven't got a published xAP v1.3 spec. I only got one reply
<br>
(from James) to my last direct email to everyone with the outline
<br>
changes that I thought were in the spec :-( Having said that there
<br>
are a lot of application out there now implementing xAP v1.3 and I ahve
<br>
tried to ensure with the developers thay they all meet the spec - or at
<br>
least my interpretation of it ;-) We do need to get this documented
<br>
and published !<br>
<br>
Re BSC v1.4 - or at least an addendum to BSC1.3 to handle xAP v1.3
UID's <br>
- again we need to do this although I hope it's fairly obvious - you
<br>
just need to cope with the longer UID's that xAP v1.3 supports. <br>
ID=xxxx ID=xxxxxx etc . In BSC v1.4 there has been the ongoing talk
<br>
about a 'choice' device and Edward and I are both using his suggested
<br>
way of implementing this - and it is in the released HouseBot plugin.
<br>
We have not persued an actual menu structure type treatment of this -
<br>
which is something that you might like for your switches, this probbaly
<br>
should be its own schema. I know IanB was looking at this.<br>
<br>
There are some clarifications we need to make to the existing BSC v1.3
<br>
spec as it is ambiguous in some areas. I'm happy to work with you on
<br>
this and the xAP v1.3 spec if you wish ??<br>
<br>
Kevin<br>
<br>
about Lehane Kellett wrote:<br>
> I've just been working on updating the LCD switch display to use
a<br>
> newer board. As part of this I added support for extended UID's
but<br>
> found there isn't a reference on the web. I guess this needs
some<br>
> focus before we create mildly different variants in our
code.<br>
><br>
> In the same way, ID=xxxx needs adding to BSC and some clarity
added.<br>
><br>
> I'm willing to have a go at BSC 1.4 for the extensions but what
else<br>
> needs adding or changing?<br>
><br>
> Lehane<br>
> <a moz-do-not-send="true"
href="http://www.mm-wave.com/honeycottage/xaplcd2.htm";>http://www.mm-<wbr>wave.com/<wbr>honeycottage/<wbr>xaplcd2.htm</a>
for the display. I'll<br>
> add photos in the back box shortly.<br>
><br>
><br>
><br>
>
------------<wbr>---------<wbr>---------<wbr>------<br>
><br>
> Yahoo! Groups Links<br>
><br>
><br>
><br>
><br>
> <br>
<br>
</p>
</div>
<!--End group email --> </blockquote>
<br>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=1946/stime=1227884942";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xAP_developer/join;_ylc=X3oDMTJmamZybnJnBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyMjc4ODQ5NDI-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkbTFvMWpxBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjI3ODg0OTQy";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</body>
</html>
--------------050406030204030401000703--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|