RE: Re: Proposal for iPaq Touchscreen systems (in place of C BUS Switches)

["Ward, David" <DAvid.Ward@xxxxxxxxxx>]

Mal, Dave,

thanks for the info.  It's something I'm interested pursuing later on.

Dave

-----Original Message-----
From: Mal Lansell [mailto:mlansell@xxxxxxx]
Sent: 13 September 2004 12:10
To: ukha_d@xxxxxxx
Subject: [ukha_d] Re: Proposal for iPaq Touchscreen systems (in place of
C BUS Switches)


I use Embedded Visual C++ 3.0, and the PocketPC 2000 SDK, both of=20
which can be downloaded for free from Microsoft.

No learning curve for me - I'm a games programmer by trade, so I'm=20
well used to the Visual Studio environment and C++.  The only changes=20
I needed to make to my xPL codebase to get it to work on PocketPC was=20
to use winsock 1 instead of 2.  I also had to find a version of STL=20
that I could use on Pocket PC.

I have to say I was pleasantly surprised by the ease of debugging on=20
the Pocket PC, though - it all worked seamlessly through the=20
ActiveSync connection.

I'm going to make the C++ code I use as a basis for xPL apps and=20
windows services available for download at some point.  It makes=20
developing a new application fairly straightforward, but I need to=20
document it and sort out my website first.  Unfortunately(?) I'm off=20
to the good ol' US of A for a couple of weeks, so it may be a month=20
before it's up there.=20

Mal






--- In ukha_d@xxxxxxx, "Ward, David" <DAvid.Ward@s...>
wrote:
> Mal,
>=20
> What tools are you using to develop your PDA applications and=20
was/is it a
> steep learning curve?
>=20
> Dave
>=20
> -----Original Message-----
> From: Mal Lansell [mailto:mlansell@f...]
> Sent: 13 September 2004 10:32
> To: ukha_d@xxxxxxx
> Subject: Re: [ukha_d] Proposal for iPaq Touchscreen systems (in=20
place of
> CBUS Switches)
>=20
>=20
> I started something along these lines a couple of weeks ago.  I've=20
been
> getting into xPL, and decided to xPL-enable my PDAs to use as remote
> controls.  So far I have the xPL part working - I just need to add=20
the
> graphics, and an editor to allow the customisation of the display!
>=20
> Rather than go to the expense of new PDAs, I just bought wifi cards=20
for my
> old HP Jornada 520s.  The SH3 processor is a bit slow, and it only=20
has a 256
> colour screen, but it's perfectly adequate for this application.=20=20
There are
> usually a few of these Jornadas available on Ebay - IME, they can=20
be had for
> around =A350, plus another =A325 for the wifi cf card from Ebuyer.com
>=20
> I'm not sure a PDA would make a good replacement lightswitch unless=20
it was
> always on - if it's dark you want the lights to come on as soon as=20
you touch
> the screen, not after it's connected to the access point.  Perhaps=20
it would
> be possible to connect some local control via the serial connection.
>=20
> Mal
>=20
>=20
>=20
>=20
> ----- Original Message -----
> From: "Andy Laurence" <andy@a...>
> To: <ukha_d@xxxxxxx>
> Sent: Saturday, September 11, 2004 11:42 AM
> Subject: Re: [ukha_d] Proposal for iPaq Touchscreen systems (in=20
place of
> CBUS Switches)
>=20
>=20
> > From: "Gareth Cook" <g@xxxxxxx>
> > > 1. Looking at the iPaq website, one of the units states
it=20
needs 5V @
> 2A.
> > > This is achievable, and eBuyer do a generic PoE adaptor
which=20
will
> deliver
> > > 5V @ 2.5A. We can remove the inbuilt lithium battery as if
the=20
iPaq
> needs
> > > a kick, we can do it from Node0. You don't want to have to
keep=20
pulling
> it
> > > out of the wall !
> >
> > Not sure I fancy sending 2A over CAT5, but the IPAQ will use=20
virtually
> none
> > of that anyway.  I'd be amazed if it ever required more than=20
500mA.
> >
> > > 2. Network you think would be easy - but this will require a
CF=20
card to
> > > RJ45 - will have to get a unit to look at the space needed
for=20
this in
> the
> > > wall.
> >
> > If you're running cable toit, why not use the serial/USB=20
interface?  Saves
> > buying a network card, and saves on space too - solder the=20
connections
> > directly to the PCB.
> >
> > > If an iPaq were to be used, then this will require a
fairly=20
deep hole in
> > > the wall - but at least it may be possible to dig out a
British=20
double
> > > gang standard hole which could be then retrofitted back to
a=20
British
> light
> > > switch of sorts (as opposed to a J box that CBUS requires).
> >
> > Sounds good.  Have you measured an IPAQ and a double gang hole?
> >
> > > 3. An alternative network source is of course a built in
wifi=20
or CF wifi
> > > card - but hey if a cable is there, I'd prefer it.
> >
> > Agreed.
> >
> > > Another idea struck me - but the electrical bods out there
may=20
have to
> > > confirm this - we have a standard light switch there
already=20
delivering
> > > power to the light (and the light is going to be changed to
a=20
star wire,
> > > hence rendering the power to the light switch out of
commission)
> > >
> > > 4. Use the lighting ring to power the ipaq - the iPaq needs
12V=20
@2A -
> can
> > > we mount the PSU for the iPaq in the wall and connect to
the=20
light ring
> to
> > > be powered ? May need some hacking to the PSU module itself.
> >
> > Sounds more than feasible.  Of course, the usual caveats of mains
> > electricity apply - don't electrocute yourself!
> >
> > > 5. With the method in point 4, we would need to use a
WiFi=20
card - but
> that
> > > means NO retrofitting of CAT5 for CBUS. I like this method
:-)
> >
> > I like that method too!  Of course, you still have to change
the=20
wiring
> from
> > standard to get the dimming module going.
> >
> > > Comments appreciated - have I had a mad moment or is this=20
workable ?
> >
> > I'd say that's more than workable!  It's also something that=20
software like
> > Xlobby would cope ith well - build a landscape skin!
> >
> > Cheers,
> > Andy
> > --
> > http://www.andylaurence.co.uk
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
>=20
>=20
>=20
>=20
>=20
>=20=20
> Yahoo! Groups Links





=20