The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Hardware BSC mapper


  • Subject: RE: Hardware BSC mapper
  • From: "Andy Laurence" <andy@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 14 Jul 2006 08:09:42 +0100

From: Kevin Hawkins [mailto:lists@xxxxxxx]
> Not yet Andy - Phaedrus are looking at the possibility of adding BSC
> Mapping within the xAP Netiom - (by all means drop them an email
saying
> how wonderful this would be - always helps).

Oooh!  That would be *very* handy.

> I'm also considering adding
> it to the C-Bus embedded xAP gateway, or perhaps even a standalone
> mapper as that would have much more free space - but nothing likely to
> appear in the near future on this...  I have some code done that does
> this in one of my development units here but everything (the
> sources/targets) are hardcoded.

I guess user definable sources/targets are the difficult thing, eh?  Still,
if my xAP NetIOM will be able to do it, I'll be a happy chappy!

> I have  re-written Ascentiums' BSC Mapper application  - to utilise
> James' OCX rather than Patricks' - and this appears to have fixed the
> memory leak issue. Available on request - and reminds me I must post
it
> to the xAP downloads area.  Just thinking on my feet here about the
> practicality of running two Mapper applications at the same time on
> different PC's should you be concerned about the OS stability. ....
> would probably work as long as there were no 'toggle' commands
involved
> of course.

True.  However, I would prefer something standalone, purely because I won't
be tempted to use it for anything else.

Cheers,
Andy




xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.