Anybody knows where I can find out details about the software GECKO is using to communicate with their current models digital packs? They use a flash EEPROM, it looks like Echelon's LonWorks but maybe it's not. Somebody said, it's Motorola? I tried GECKO directly but not much luck.
Thanks for reading my question.
hotharold

Unless you're very experienced with Microcontroller technology and the specific programming language of it, it wouldn't do you any good anyway. Last time I looked, I think they were using Motorola Microcontrollers .


However... if you're talking about a way that a Gecko controller can call home to Uncle Bill? Possibly with lon works but I think it's a stretch.

Now if you want something to put you to sleep, (lol)...

Lon Works is a bit more sophisticated than an et call home solution. They're more oriented towards enterprised based network management solutions, WAN interfacing to existing microcontroller designs, and a few other irons into specialty technologies... but not in the u-controller arena itself. (They took the smart route and provide a way to take existing cool micro-controller technology produced by the biggies, add lon works echelon interface and code... and poof! now your little robot thing can call china via vpn or whatever and give you the temperature of the air or tell you what your ex-wife is doing).

Virtually all digital spa packs use standard off the shelf microcontrollers with imbedded flash eeprom, write once eprom, or the real 'burned' roms. (The Mspa and Tspa versions do have a separate Rom chip I think - the SSPA is all in one). The software used to 'communicate' with the controller is dependent upon the platform used to work with, and the interface that connects to it. (Maybe you already know this, but a microcontroller is basically a complete computer system bundled up into a chip with a lot of cool stuff that allows it to interface with the outside world).

So, if you're running Sun OS, your software will be different to communicate to the microcontroller than one running WinX. But the protocols will be the same.

Now to actually communicate with that microcontroller, you simply need to determine which controller is being used, go to the manufacturer's site, and get the specs there. From that point, you can communicate with any microcontroller directly, given the correct operating hardware and software parameters.

For a real eye opener on microcontroller technology, and the ins and outs of them all, take a look at MicroChip.Com.

There are a few spa controller manufacturers using MicroChip's 16xxx series of microcontrollers, noteably ACC, and CTI.

But think about it... even if you could say, put a 20 pin hijacker on the back of the controller, connect that to the interface box that's plugged into the parallel or usb port on your computer, you'd still need to know the programming language, (or have a disassembler for it), write or change the code or whatever, and then redownload it into the controller.

Then go another step further, microcontroller manufacturers have imbedded protection systems that will prevent someone like yourself from going in and looking at or changing the rom code... unless of course, the folks at Gecko or Balboa Instruments or whomever will give you the pass key to get to it!

Yeah, there's a new turn at every corner.

Thank you very much for the good info!!!!!!!!!!!
Yes, we do have extensive in-house capabilies in these areas (not me personally, but familly members...one used to work for Motorola's microcontroller chip research...)
By the way, Gecko uses an interface plug going into the motherboard, to communicate via ir with a PALM handheld, allowing the service technician to "read" status, error events, etc. and also upload software revisions.

Anybody out there who has actually done anything in this area?? Every bit of info is most appreciated!

hotharold