Tag Archives: Android

IP30 Programming – Part 2

The batteries on the IP30 and CN3 are fully charged and ready for some tinkering.

Upgrading the Firmware from 3.01 to 3.16

I looked into upgrading the firmware on the IP30 and it looks to require a MiniSD card. MiniSD is the never-mentioned step brother of SD and MicroSD… meaning stores don’t carry it anymore. I’ve got a MiniSD card and reader on order from Amazon… so updating the IP30 will have to wait.

Available Commands

To receive the available commands on the IP30, the HELP command can be issued. Here’s the response for BRI 3.01 on the IP30:

Reading Tags

Issuing a READ command causes the IP30 to read all tags in the vicinity and report them back in one shot. Tested and this works. Turns out the 8 tags that I have for testing all have the same ID… not optimal but it will work for now.

Next

This is probably it for testing the IP30 with Windows and Tera Term. I’m going to activate my license to Xamarin (have to purchase just to deploy to the device…wish they had some better pricing for education) and get to programming.

Communicating with the Intermec IP30 RFID reader over bluetooth…hopefully with Android

I’m starting work on a project for my MBA program that involves using a mobile RFID reader with an Android device. I’ve purchased a Nexus 7 for the project, and the school has loaned me an Intermec IP30 RFID reader. I’m going to detail my steps in getting this going here.

10/5/2012

Acquired the IP30 from my university. This IP30 is attached to the Intermec CN3 handheld computer, which is running some old version of Windows Mobile. I’ve confirmed that the CN3 can actually communicate with the IP30 and read tags – yay! I don’t plan on using the CN3, but it’s a nice reference for how the communication is supposed to work.

The IP30 is communicated to from the CN3 by bluetooth. Intermec offers some libraries for C# development, but I won’t be using them as this will be an Android application. I’ll be using Xamarin’s Mono for Android (C#), but the Intermec assembly uses some Windows CE libraries so it’s no help. Luckily, it looks like the IP30 works with Intermec’s “Basic Reader Interface” or BRI. This is an ASCII-based protocol over serial/bluetooth. They even have a handy doc on all the relevant commands and how to structure your app if going straight against BRI.

At this point, my goal is to communicate with the IP30 using a hyperterminal on my Windows 7 box. I wore the battery down on the IP30 trying to use PUTTY to for communication and couldn’t manage to get it to respond to any command. I believe that I just wasn’t sending the necessary CRLF at the end of each command for the IP30 to respond, so I’ve downloaded a different hyperterminal – Bray++’s Terminal. Whenever the battery charges up for the IP30, I’ll start whittling at it again :)

Later…

Couldn’t get Bray’s Terminal to connect to the IP30. It would cause Windows to beep, then I’d not be able to connect to the IP30 with anything (including Putty) until I reset the connection by pulling the battery out of the IP30 and putting it back in.

I downloaded Tera Term and have success! It was indeed the newline setting for transmission. I had to change this setting in the Terminal setup and also enable local echo so I could see what I was typing…

This is what I’m seeing when issuing a command through Tera Term:

Luckily in my searching for IP30 related posts, I ran across a page on Intermec’s site where another developer was trying to do what I’m doing through HyperTerminal and had an issue. Issuing FACDFLT4 (which is issued in the BRI manual I referenced earlier) reset the device to factory settings – so I should be good to go!

To be continued…

Samsung Infuse 4G: Adding Ringtones

This is old information to those who’ve had an Android for a while, but it was news to me… To add mp3 ringtones, use the usb cable supplied with the phone to mount the internal SD card (the 2 gig one). Then, create the following folder structure:

/media/audio/ringtones
/media/audio/notifications
/media/audio/alarms

Place your mp3 ringtones into the ringtones folder. Done.

Samsung Infuse 4G: The Super Phone with No Press

Remember this phone? It’s the Samsung SGH-i997, otherwise known as the Samsung Infuse 4G. Originally shown at CES in January 2011. Engadget did a great job covering the Infuse, letting loose the following specs:

  • 4G (HSPA+)
  • 4.5″ Super AMOLED Plus screen – featuring a “50 percent boost in sub-pixel count”
  • 8 megapixel camera on the back
  • 1.3 megapixel camera on the front
  • 1.2 GHz single-core Hummingbird processor
  • Android 2.2
  • textured matte rear cover, described as feeling “exceptionally high-quality”
  • thinnest smartphone on AT&T when it launches at a to-be-determined date

Truth be told, I didn’t care about the Infuse in January. It was another phone in a long list of phones being released. I’ve had my iPhone 3GS for a while and it was working fine. That changed when my iPhone’s screen stopped displayed one of the colors – turning all the colors purple/green and making links on the Internet pink. With motivation, the hunt for a new phone was on. A friend turned me onto the SGH-i997 and I’ve been patiently waiting, watching ever since.

I turned to Google, searching for SGH-i997. Apparently I’m the only one thinking about this phone…at least since January. Gizmodo ran a great piece on the Infuse. Here’s some good quotes:

  • “Why exactly, wasn’t this the new Nexus phone?”
  • “Whoa. This is quality.”
  • “The fastest Android phone yet.”

pdadb.net has the most complete profile of the phone, where we found out a few more specs – notably the battery size:

  • 1750 mAh battery

To top off the specs I care about, a friend in the know informed me that it’s got near field communication.

So – this phone is awesome. Where’s the Android press been? They’ve probably been covering the Motorola Atrix, and with good reason. But surely there’s been some kind of mention of this phone…right? If you don’t count the typical FCC coverage, you’ll find that apparently Samsung is getting ready to silently release this phone into the wild…and Wal-Mart of all places is the first to shout about it! On page 9 of their weekly ad.

If you read the comments on that engadget article above, you’ll see exactly what I’m thinking. With Samsung waiting this long to release the phone, it’s no longer quite as super as it once was. Even if you’re only focused on Samsung, even the Galaxy S 2 starts looking better on paper:

Galaxy S2 Infuse 4G
Android 2.3.1 Android 2.2.1
TouchWiz UI 4.0 TouchWiz UI 3.0
2.0 mp front camera 1.3 mp front camera
Dual core 1.0 GHz Single core 1.2 GHz

There are couple items that I like more about the Infuse, specifically:

  • 1.2 GHz single core processor – I’m not sold on dual core phones yet. 1.2GHz seems mighty fast for an OS that hasn’t had much time to be optimized for dual core.
  • 4.5″ screen – yeah the Galaxy S2 will have a 4.3″ screen, but I’m stretching for things to like here, cut me some slack.

So the press has been absent on the Infuse. Samsung is pushing out a very competitive phone in the Galaxy S2 very close to the release of the Infuse 4G. Should I continue to look forward to picking up an Infuse? Is dual core really worth waiting another month or two with my purple/green screen iPhone 3GS?

I’m hesitant at this point. But if there’s one thing that would help, it would be some kind of announcement by Samsung on the availability of the Infuse 4G and when they will push an update to Android 2.3 to bring it inline with other leading phones. Will it be a few months? Or will they abandon the phone after letting it out? Am I better off just getting a Motorola Atrix?

Picking a new phone is fun at some level, but it feels like buying a car when you’re not sure if next year’s model (to be released in another month) looks better, has a bigger engine, and will have a longer lifespan. Yuck.