Geo-fencing app - general query.

I’ve got an opportunity for developing a geo-fencing application for a customer.

It needs to store up to 100 locations (lat, long) which it updates daily by contacting a server over IP/GPRS which I can maintain. It monitors the GPS continually and if the device is near one of the pre-set locations it toggles one of two digital outputs within a second (or maybe two).

After much googling and surfing I’ve stumbled upon the AirLink FXT. It seems to be ideal with the GPS/IO extender board.

The digital outputs will need some opto-isolation and/or relays. I was wondering whether it is fairly easy to create my own extender boards. Can the GPS/IO extender board be used as a reference design? Are the schematics available?
There may not be enough space for the extra circuitry so having an additional external box may be necessary, but it would be nice to have something as neat as possible.

I haven’t found any information yet to the amount of memory available to programs. Memory for code, memory for data. Is there any static memory? Can it be reprogrammed? Can additional memory be added? etc.

Also, I’ve had experience with other ‘programmable modem’ chips but they were only programmable in Python. This was very slow and meant they couldn’t be used for anything remotely intensive. For this application, I will be wanting to compare the Lat/Long feed from the GPS against a list of 100 known locations and generate a digital output if necessary ideally within a second. I’m hoping this is doable.

Any advice would be appreciated if anyone can suggest a better platform, or has experience doing anything similar.

Yes, it should be able to do what you require

That depends entirely on your skill as a PCB designer! 8)

Wavecom’s stated intention when they introduced the IESM concept (before the SiWi takeover) was that it should be an “open” interface, and customers should be able to create their own boards…

See: Fastrack Supreme?

You would have to contact your Distributor or FAE.

You can certainly get DXFs showning the outline, connector positions, and “keep out” areas.

In that case, it may be better to just use the standard IESM and have it control your external kit via SPI or I2C…

It’s in the ADL User Guide - should be plenty for what you’ve described!

Do you mean “non-volatile”? If so, yes!

Which “it” are we talking about here? Both the application & the non-volatile memory can be updated.

No (unless you add it externally)

Open-AT uses native, compiled code.

The nature of the “framework” means that you can’t do really quick IO - but it’s fine for many applications

Yes, that should be fine