Well, this is probably my last post on this topic.
I went to my eye doctor today and he is very pleased with the progress. My left eye is basically perfect, but my right eye has a very slight -0.025 diopter nearsightedness, but this is starting from over -8 in both eyes. He said the right eye is still healing and this is just the tail end of the process. I am now down to only doing the FML steroid drops once a day.
My observation is that my vision - especially at a distance - is spectacular! Not having minor optical distortions or smudges or scratches from glasses is great and having back all of my peripheral vision is also fantastic. One of the best items of recent progress was that I found I didn't need reading glasses to work on the computer and I could get all my screens back to their regular fonts sizes!!
There are still some downside. I do have haloing at night which is irritating while driving but should clear up over the next few months. I do have to wear reading glasses now for reading in bed or playing games on my iPhone. Having to remember my reading glasses so I can read menus at restaurants and so on is irritating. Hopefully this will get slightly better, but I expect this is something I may be stuck with at my age. I do need to keep using artificial tears regularly, but my eyes don't seem to feel dry or uncomfortable except at the end of a long day.
When I was researching the procudure I found several useful diary blogs like this through Google. So, for those who might come upon this blog from the interwebs looking for info on PRK surgery, here are links to all the entries in sequential order:
It's been quite a journey!
Wednesday, August 11, 2010
Thursday, August 5, 2010
Arduino-Twilio Dialer Application
Well, it has been a while since I posted an Honest-to-God Arduino project here! What with getting my eye surgery done and one thing and another, this has taken me quite a while. Besides, there were more than a few challenges in getting it all to work along the way!
This project is a concept for an information kiosk or unit that could be placed in a public area where passers-by could request information. A user enters their mobile phone number into the keypad and they are then immediately called by the Twilio cloud-based telephony system (check out Twilio here) and presented with a simple phone menu that allows them to:
Here is the obligatory video showing how it works:
Hardware
The hardware consists of:
The hookup of the keypad is based on this article by amando96 on Instructables. You will have to sign up for membership to see the whole article or you can just follow the above diagram. One odd thing I noticed was that the pull down resistors turned out to not be required. Originally I had them included and everything worked fine, then at a certain point in the development the keypresses started looping and I removed the resistors and everything worked fine!
This just uses the standard “keypad.h” library found on the Arduino website, but slightly modified so the pins do not interfere with the Ethernetshield. There is also an Instructable post on multiplexing the button input to use fewer digital pins, but since I didn’t need any extra digital pins I figured this was simpler.
The serial LCD is quite straightforward to hookup, but just note that I am using one of the A1 Analog pin as the Tx for the serial since I am not using any analog inputs anyway.
Software
As with the previous Twilio-Arduino project, this one requires:
This diagram shows the overall flow:
The first part is the Arduino software:
This uses the Arduino Ethernet library to set up a client application, the Keypad library to get the keypresses, NewSoftSerial to send information to the LCD and finally the TextFinder library to parse the result codes from the server. I have put all the LCD messages into functions just to clean up the code since each message needs to have a screen clear send and some delay. I’m sure I could further clean that up to just have a function that did the screen clear, but this works.
The Arduino client in term communicates with the PHP server program (dialer_twilio.php):
Anything marked “XXXX” above is info on the account and phone numbers to be used.
This script does a quick and dirty check if the number is valid (just making sure there are no stray “x” or “#” characters and it is the right length) then uses theTwilio REST API to set up the call. Twilio will go to the “twi_test.php” script for info on how to handle the call.
So, when Twilio goes to twi_test.php it sees:
This sets up the top level menu of the simple IVR and then directs to go to “twi_action.php” once a button is pushed. The XML such as and are the Twilio “verbs” that defines actions on the Twilio cloud system.
So here is “twi_action.php";
This parses the digit pressed from the POST command and then takes action on the digits, which is either:
This one is very simple. It just plays back the message that was just recorded. That’s all there is to it! :-)
Conclusion
This project could have some practical uses as a low cost way to place a simple information service in some public place. It does, however, have the obvious limitation that there is no validation that the number entered really does belong to the user’s cell phone and not to some little old lady in Detroit, so in it’s current form it could just be a nuisance generator. This could probably be fixed with an exchange of a PIN via SMS.
What other things could this kind of project be used for? Here are some ideas:
This project is a concept for an information kiosk or unit that could be placed in a public area where passers-by could request information. A user enters their mobile phone number into the keypad and they are then immediately called by the Twilio cloud-based telephony system (check out Twilio here) and presented with a simple phone menu that allows them to:
- Talk to an operator
- Leave a voice message
- Receive an SMS message
Here is the obligatory video showing how it works:
Hardware
The hardware consists of:
- Arduino Duemilanove
- Arduino Ethernetshield
- Sparkfun serial enabled 20 x 4 LCD display (LCD-09568)
- Sparkfun 12 button keypad (COM-08653)
The hookup of the keypad is based on this article by amando96 on Instructables. You will have to sign up for membership to see the whole article or you can just follow the above diagram. One odd thing I noticed was that the pull down resistors turned out to not be required. Originally I had them included and everything worked fine, then at a certain point in the development the keypresses started looping and I removed the resistors and everything worked fine!
This just uses the standard “keypad.h” library found on the Arduino website, but slightly modified so the pins do not interfere with the Ethernetshield. There is also an Instructable post on multiplexing the button input to use fewer digital pins, but since I didn’t need any extra digital pins I figured this was simpler.
The serial LCD is quite straightforward to hookup, but just note that I am using one of the A1 Analog pin as the Tx for the serial since I am not using any analog inputs anyway.
Software
As with the previous Twilio-Arduino project, this one requires:
- An account with Twilio
- A web-server with PHP
- An Ethernetshield
This diagram shows the overall flow:
The first part is the Arduino software:
/* * Twilio Arduino Information Service Dialer * When used in conjunction with "dialer_twilio.php PHP script and the Twilio cloud-based * telephony environment (www.twilio.com) this allows a user to enter a phone number into a keypad * on an Arduino and have a call placed to their cell phone with various options for information. * * Uncomment the //Serial lines for troubleshooting/debug info. * * This code is in the public domain. Please provide credit if it is used * in another project. * * written by Chris Armour, August 4th, 2010 * * Full description psted at http://opensource-torchris.blogspot.com/ * */ //=====================Libraries=============/ #include#include #include #include byte mac[] = { 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED }; //MAC address for Arduino byte ip[] = { 192,168,0,34 }; // IP address you wish to assign to Arduino byte server[] = { 192, 168, 0, 171 }; // IP address of your PHP server int ServerPort = 55455; const byte ROWS = 4; //four rows const byte COLS = 3; //three columns char keys[ROWS][COLS] = { {'1','2','3'}, {'4','5','6'}, {'7','8','9'}, {'*','0','#'} }; byte rowPins[ROWS] = {5, 4, 3, 2}; //connect to the row pinouts of the keypad byte colPins[COLS] = {8, 7, 6}; //connect to the column pinouts of the keypad boolean ConnectedState = false; char DialNum[12]={"xxxxxxxxxxx"}; int a; NewSoftSerial mySerial = NewSoftSerial(14,15); //osft serial running off of Analog Pin 1 Keypad keypad = Keypad( makeKeymap(keys), rowPins, colPins, ROWS, COLS ); Client client(server, ServerPort); TextFinder finder( client); void setup(){ Ethernet.begin(mac, ip); // Serial.begin(9600); mySerial.begin(9600); mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Started - Press any key to conect to the server."); //Display initial message on LCD. } void loop(){ char key = keypad.getKey(); if (key != NO_KEY){ if (ConnectedState == false){ if (client.connect()){ if(finder.find("results:") == true){ char c = client.read(); // Serial.print("Value of the connect code: "); // Serial.println(c); mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Connected. "); delay(2000); WelcomeMsg(); //If connection successful, then print Welcome Msg and flip the connected state variable. ConnectedState = true; // Serial.println(DialNum); } } else { ConnectedState == false; ConnectFailMsg(); //If connection fails, then print an error. delay(2000); } } if (key == '*') { //When it picks up the "*" then it starts gathering the digits. // Serial.println("Got the *"); EnterNumMsg(); do { key = keypad.getKey(); if (key != NO_KEY){ delay(150); // Serial.println(key); mySerial.print(key); //Prints the keypad input to the LCD for user feedback. DialNum[a] = key; //Puts the key info entered into an array. a++; } } while (key != '#'); } if (key == '#'){ //When the "#" is pressed, the info is sent over to the PHP script. delay(250); mySerial.print(DialNum); client.println(DialNum); //Dialnum array sent to PHP. if(finder.find("results:") == true){//PHP script evaluates number & sends back response. char c = client.read(); // Serial.print("Value of the return code: "); // Serial.println(c); if (c == 'Y'){//Y back from the script means it is a valid number & success displayed. NumAcceptedMsg(); } if (c == 'N'){//If it is not a valid number, then N returned & error displayed. NumNotAcceptedMsg(); // client.println(DialNum); delay(3000); WelcomeMsg();//Go back to Welcome message. } delay(200); if(finder.find("results:") == true){ char c = client.read(); // Serial.print("Value of the return code: "); // Serial.println(c); if (c == 'O'){//If the call was successully placed display success then go back to Welcome. NumCalledMsg(); delay(4000); WelcomeMsg(); } if (c == 'X'){//If the call couldn't be made then error message & return to welcome. NumNotCalledMsg(); delay(3000); WelcomeMsg(); } } // Serial.println(DialNum); // Serial.println(a); a = 0; } } } } void WelcomeMsg(){ mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Welcome to the Information service.Press the * key to start."); } void EnterNumMsg(){ mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Enter your 10 digit phone number followed by #: "); } void ConnectFailMsg(){ mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Connection Failed. Press any key to reconnect."); } void NumAcceptedMsg(){ // Serial.println("Number accepted by server"); mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Number Accepted. "); } void NumNotAcceptedMsg(){ // Serial.println("Number NOT accepted by server"); mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Number not valid."); } void NumCalledMsg(){ // Serial.println("Number called successfully."); mySerial.print(254, BYTE); delay(200); mySerial.print(1, BYTE); delay(200); mySerial.print("Number called successfully."); } void NumNotCalledMsg(){ // Serial.println("Number cannot be called."); mySerial.print(254, BYTE); delay(100); mySerial.print(1, BYTE); delay(100); mySerial.print("Number cannot be called."); }
This uses the Arduino Ethernet library to set up a client application, the Keypad library to get the keypresses, NewSoftSerial to send information to the LCD and finally the TextFinder library to parse the result codes from the server. I have put all the LCD messages into functions just to clean up the code since each message needs to have a screen clear send and some delay. I’m sure I could further clean that up to just have a function that did the screen clear, but this works.
The Arduino client in term communicates with the PHP server program (dialer_twilio.php):
request("/$ApiVersion/Accounts/$AccountSid/Calls",
"POST", array(
"Caller" => "XXXXXXXXXXXXXXX",
"Called" => $dial_num,
"Url" => "http://xxxxx.xxxxx.xxx/twi_test.php"
));
if($response->IsError){
echo "Error: {$response->ErrorMessage}\n";
socket_write($spawn, "results:X\n");
echo "Sent over X\n";
} else {
echo "Started call: {$response->ResponseXml->Call->Sid}\n";
socket_write($spawn, "results:O\n");
echo "Sent over O\n";
}
} else {
echo ("Invalid number\n");
socket_write($spawn, "results:N\n");
echo "Sent over N\n";
}
usleep(5000);
}
}while(true);
?>
Anything marked “XXXX” above is info on the account and phone numbers to be used.
This script does a quick and dirty check if the number is valid (just making sure there are no stray “x” or “#” characters and it is the right length) then uses theTwilio REST API to set up the call. Twilio will go to the “twi_test.php” script for info on how to handle the call.
So, when Twilio goes to twi_test.php it sees:
header("content-type: text/xml");
echo "\n";
?>
Hello. Welcome to the Arduino Information Service.
Press 1 to be connected to an operator.
Press 2 to leave a voicemail.
Press 3 to receive an SMS message.
Press 4 to repeat this menu.
Press 5 to hangup.
This sets up the top level menu of the simple IVR and then directs to go to “twi_action.php” once a button is pushed. The XML such as
So here is “twi_action.php";
$stringData = $_REQUEST['Digits'];
switch($stringData){
case 5:
echo "";
echo " Thank you, Good bye. ";
echo "";
echo " ";
break;
case 4:
echo "";
echo "";
echo "http://xxxxx.xxxxx.xxx/twi_test.php";
echo " ";
echo " ";
break;
case 3:
echo "";
echo "You are being sent an SMS message. ";
echo "You are receiving this message from the Twilio Arduino dialer application. ";
echo " ";
break;
case 2:
echo "";
echo "Leave your message after the tone and press # when you are done. ";
echo "";
echo " ";
break;
case 1:
echo "";
echo "XXXXXXX ";
echo "Goodbye ";
echo " ";
break;
}
?>
This parses the digit pressed from the POST command and then takes action on the digits, which is either:
- Connect to an operator (in this case it dials through to my Skype account).
- Leave a voicemail. Currently this records a sound file which you can download from the Twilio website, but it could also have the sound file sent to an email address or transcribe the voice into text and have that sent along.
- Receive and SMS message. This sends a canned message that could be some general information to the cell phone that made the call.
- Repeat the menu.
- Hangup.
header("content-type: text/xml");
echo "\n";
?>
Thanks for the message. Here is what you recorded.
Goodbye.
This one is very simple. It just plays back the message that was just recorded. That’s all there is to it! :-)
Conclusion
This project could have some practical uses as a low cost way to place a simple information service in some public place. It does, however, have the obvious limitation that there is no validation that the number entered really does belong to the user’s cell phone and not to some little old lady in Detroit, so in it’s current form it could just be a nuisance generator. This could probably be fixed with an exchange of a PIN via SMS.
What other things could this kind of project be used for? Here are some ideas:
- Make a super secure lock by combining this project with an RFID reader lock so that once the card is swiped the user also has to enter a PIN and a code received via SMS at a cell phone that has been pre-registered with the system. This way an intruder would have to steal not only the users RFID badge, but also their phone and their PIN number.
- This could also be adapted to trigger phone calls or SMS messages for various conditions driven by digital or analog inputs - such as temperature readings or intruder alarms. Conversely, as discussed in my Twilio LED project, a call could be used to control switches, motors or valves remotely using a telephone.
- If it used Power Over Ethernet it would eliminate the extra power supply requirement. Even better would be using wi-fi or GSM cellular data to eliminate the need to have it wired to a router.
- Clever use of the PROGMEM would probably allow all the response strings to be stored on the Arduino so it might be possible to dispense with using an outside webserver altogether!