04-12-2005 05:24 AM
04-12-2005 07:32 AM
04-12-2005 11:49 AM
04-16-2005 11:28 AM
@tbob wrote:
I suppose you could use a modem tied to the serial port and use Labview serial vi's to send commands (text) to the modem to make it dial a number. However, the receiving end would hear nothing but modem tones. Maybe a modem connected to a computer on the receiving end could be made to receive text and display it on a computer. The receiving computer would have to have a program running that is waiting to receive the text. Or maybe you could design a circuit that lights an LED or sounds a buzzer when the receiving modem's Carrier Detect goes hi.
04-26-2006 06:17 AM
Well... it is a fairly simple task, if you simply need an indication of an event (without transferring any info). Have two GSM modems: one on the site and the other at your control station. As discussed in the above, on alarm conditions at the remote site, dial the number for your control station (command ATDxxx\r, where xxx is the telephone number. The other modem will detect the call, start to pulse RI (ring indicator) of serial port and send "RING" to serial port.
If you want to be sure that the call comes from the specific number, you can either set "waiting for call", or restrict the allowed incomming callers, or set the modem to tell you who is calling (using the appropriate CLI-related command on your modem, and getting a string like +CRING voice, yyyy).
The other option is to send an SMS.
If you would want to transfer some data, there are many options. The easiest ones:
* use the GPRS modem as a standard modem under windows (in linux it would be KPPP, if I am not mistaken), establish the GPRS connection and do NOT disconnect (you pay per MB-s, not per minutes). You would probably want to set the connection to automatically re-establish itself, if disconnected. This is proably the best way: a) the least hussle, b) full TCP/IP functionality in the sense that your remote PC is "permanenty" present on the Internet, and you can use DataSocket, shared variables etc..
* use modem's built-in PPP and TCP/IP stack to handle the connection. You will need to write software to control it (or use a commercial library, like www.lysko.com - > products) but become independent of the operating system and know what happens and when. The limitation here is that you have limited number (often only one) port on TCP and therefore have to handle many detals of data transfer by yourself. On the other hand, this is better than firewall since the TCP is handled by the modem, not by the operating system.
From the same link, you can also look at the real-world performance of different levels of wireless connectivity (GSM, GPRS, E-GPRS (EGPRS), EDGE, 3G and HSDPA) and economics of the subject.
04-26-2006 12:40 PM