5 Great Ideas for NFC Tags – NFC Advice

By , October 13, 2014 4:43 AM

5 Great Ideas for NFC Tags – NFC Advice

1. NFC Task Launcher
Launch your favourite apps and update your phones settings with a simple tap of your mobile phone. Using free mobile apps such as NFC Task Launcher for Android you can easily programme your NFC tags to trigger tasks on your NFC-enabled mobile phone. Examples include tapping an NFC tag on your car dashboard to launch a navigation app and enable GPS or tapping an NFC tag by your bedside to turn your phone to silent and set an alarm for the morning. The options are endless ! Click here for the RapidNFC step-by-step guide for NFC Task Launcher.
2. Out of Home Advertising
Enhance traditional printed media with the interactivity of NFC. NFC Smart Posters allow customers to download mobile vouchers, access local information, ‘like’ and ‘follow’ on social media or even purchase products by simply tapping their phone ! NFC Smart Posters are created by attaching a visible NFC tag to the front of the poster or applying a hidden NFC tag to the reverse of the poster, aligned to an NFC graphic or call to action.
3. Interactive Events
Supply each guest with an individually programmed NFC tag and offer a seamless experience. Each NFC tag acts as an ID chip and can be used for access control, registering interest and creating unique experiences. Better still each interaction can be logged via a mobile app so there is no need for expensive hardware or infrastructure. NFC tags are available in a range of event friendly formats such as NFC wristbands, access cards and badges.
4. Tourist Trails and Treasure Hunts
Place NFC tags at different points of interest, providing location specific information and content when they are scanned. A great example is the South Downs Way National Park, who have used NFC enabled sign posts to help visitors better explore their surroundings. This same logic can also be applied to treasure hunts, simply place an NFC tag at each location and log each ‘find’ via a mobile or web app.
5. Keep Customers Engaged with Dynamic Content

Just because an NFC tag is encoded to the same web address it doesn’t mean your content has to stay the same ! Regularly update promotions and information to encourage repeat scans of your NFC marketing. NFC tags are available in a large range of promotional products and include everything from NFC fridge magnets and window stickers through to NFC pens and even beer mats.

The Difference Between NFC and RFID – Explained

By , October 13, 2014 4:42 AM

The Difference Between NFC and RFID – Explained

RFID and NFC are two closely related wireless communication technologies that are used globally for a vast number of applications such as access control, asset tracking and contactless payments. RFID was first patented in 1983 and is the precursor to NFC, so we will begin there.
Radio Frequency Identification (RFID)
RFID enables a one way wireless communication, typically between an unpowered RFID tag and a powered RFID reader. RFID tags can be scanned at distances of up to 100 meters without a direct line of sight to the reader and as such RFID is used globally for asset tracking in warehousing, airport baggage handling, livestock identification and much more. RFID operates at a range of radio frequencies each with their own set standards and protocols.
RFID Frequency Band
Scan Distance
120-150 kHz (Low Frequency, LF)
Up to 10 cm
13.56 MHz (High Frequency, HF)
Up to 1 m
433 MHz (Ultra High Frequency, UHF)
1-100 m
865-868 MHz & 902-928 MHz (Ultralight High Frequency, UHF)
1-2 m
2450-5800 MHz (Microwave)
1-2 m
3.1-10 GHz (Microwave)
Up to 200 m
Near Field Communication (NFC)
NFC operates at 13.56 MHz and is an extension of High Frequency (HF) RFID standards. NFC therefore shares many physical properties with RFID such as one way communication and the ability to communicate without a direct line of sight. There are however three key differences.

1. NFC is capable of two way communication and can therefore be used for more complex interactions such as card emulation and peer-to-peer (P2P) sharing.

2. NFC is limited to communication at close proximity, typically 5cm or less.

3. Only a single NFC tag can be scanned at one time.

These properties were developed primarily to enable secure mobile payments and it is for this reason NFC is limited to singular and close proximity interactions. An important by-product is that NFC is now available in the majority of mobile phones and this is perhaps the most important difference between NFC and RFID.

NFC-enabled phones offer both businesses and day-to-day users slick and intuitive communication between mobile phones and between a mobile phone and an NFC tag. Examples include file sharing via Android Beam, instant connection setups between electronic devices and the ability to link everyday objects such as posters to online content. For more great NFC ideas – click here.

HF RFID
NFC
Operating Frequency
13.56 MHz
13.56 MHz
Communication
One way
Two way
Standards
ISO 14443, 15693, 18000
ISO 14443
Scan Distance
Up to 1 m
Up to 10 cm
Scan Tags Simultaneously
Yes
No

WAVECOM CLONE SERIAL SETTINGS

By , September 3, 2014 12:21 PM

 

to connect to the serial port use putty

select the COM port and settings can be

When the port is selected click Ok, to get to the Port configuration form

On this form specify the port settings.

The most common port speeds for GSM phones and modems are 9600, 19200, 57600 and 115200.

The Data bits should be set to 8. The Parity to none the Stop bits to 1 and the flow control should be hardware.

Set the appropriate serial port (usually COM1)
Baud rate (speed) = 9600
Data bits = 8
Stop bits = 1
Parity = N

 

ENTER

AT
Will give you a response OK if you are connected

THEN
I can check in PuTTY GSM modem information using commands:
Manufacturer: AT+CGMI -> “WAYECOM MODULE”
Model: AT+CGMM -> “MULTIBAND G850/900E/1800/1900MHz”
Revision: AT+CGMR -> “652B09gg.Q2406B 1961548 103107 17:50″
IMEI: AT+CGSN

VMware Vcenter corruption

By , March 3, 2014 4:27 PM

mount -n -o remount,rw /

e2fsck -f /dev/sda3

DELL WIRING

By , February 10, 2014 1:50 PM

0 VMN A0
1 VMN A1
2 SCSI A0
3 SCSI A1
4 SCSI B0
5 SCSI B1
6 VMN B0
7 VMN B1

Duplicate Outlook 2013 Calendars and how to remove them

By , January 30, 2014 6:23 PM

Can you restore the .pst? It needs unloading from outlook before just deleting it.

If not:

You can solve the errors rather easily – just remove the data links in ‘Control Panel’/’Mail’/[Data Files]. Don’t do this yet.

See if you have options to remove the calendars there (probably not – now would be a good time to backup/export the working PST+calendar) and do so.

If you can still expand the contents of the deleted .pst in the Navigation pane then goto the folder view and right click and delete the offending calendar. More than likely you won’t have this option so just remove the data files from the Account window (as mentioned above).

If the calendars are still showing, do you have the option of unselecting them from the Calendar window?

Kanel and Moxa

By , January 19, 2014 10:26 AM

Hi

I use terminal servers since over 5 years with no problems.

As Cezary said, you should use rawtcp or telnet mode to conect to the
modems connected to your moxa device. Therefore no need to install any
driver nor kernel module. That is only needed if you want your OS to
show ethernet port as a virtual local serial port and then have kannel
connected to the local virtual serial port.

You should define each of your modems with its IP and port so kannel
will connect directly to it via TCP/IP:

group = smsc
smsc = at
smsc-id = modem1
log-level = 0
modemtype = auto
speed = 115200
log-file = “/var/log/kannel/modem1.log”
allowed-smsc-id = modem1;modem3
sim-buffering = true
keepalive = 60
max-error-count = 8
################################
#### SETTINGS PARA ACCESO VIA
#### TERMINAL SERVER
device = rawtcp <<<<<<<<< THIS SETUP WILL ALLOW YOU TO
host = 10.10.5.3 <<<<<<<<< CONECT DIRECTLY TO YOUR MODEM
port = 2100 <<<<<<<<<< ON THE MOXA DEVICE

Hope helps

Regards

Alvaro

On 6/1/12, Cezary Siwek wrote:
> Hi,
>
> Long time ago I’ve been playing with a regular serial modems + terminal
> server.
> The terminal server exposes each modem on a different tcp port. In the
> kannel you use either ‘rawtcp’ or ‘telnet’ smsc type.
> It worked fine for a several years.
>
>
>
> Regards,
> Cezary
>
>
> On 01/06/2012 10:57, Peter Valdemar Mørch wrote:
>> Hi,
>>
>> We’ve been using Falcom and Tango modems in the past, but they’ve been
>> difficult to buy lately. Instead we’re considering buying “Moxa
>> OnCell” or “Siemens MC35i” (which appears to be identical to
>> “Cinterion MC35i”).
>>
>> Now that we’re looking to test and buy new modems anyway, we’d love
>> some that work better in VMware ESX environments where access to
>> serial ports isn’t possible. All the above modems except the “Moxa
>> OnCell” are accessed via a serial port.
>>
>> E.g. something that holds a SIM card, has an IP address and provides
>> an SMPP interface would be perfect, but I realise I’m a novice in this
>> field.
>>
>> So far in VMware, we’ve been setting up Moxa Serial Device Servers (
>> http://www.moxa.com/product/Serial_Device_Servers.htm ) that via a
>> kernel module in the ESXi virtual host provide access to a
>> pseudo-serial port. That is flaky at best. The “Moxa OnCell” also
>> needs a kernel module, and we haven’t yet had success with it.
>>
>> I’ve read http://kannel.org/compatibility.shtml but I haven’t been
>> able to find a vendor for any of the “Phones that works as SMSC’s with
>> Kannel”. At least two of the three are no longer being produced, but I
>> think they all used serial port access, and so don’t work so well
>> under VMware.
>>
>> So in short, I’m looking equipment/solutions recommendations that
>> allow us to send SMSes from both real hardware and VMware ESX guests
>> using our own SIM card (not a remote hosted solution), using hardware
>> that is still current and in production and without kernel
>> modules/patches.
>>
>> Does such equipment exist? What do you recommend?
>>
>> Thank you for reading this far.
>>
>> Peter
>
>

SMS Servers

By , January 9, 2014 4:02 PM

SMS Tools

http://blog.biolizards.be/setting-up-a-smsgateway-part1/

http://smstools3.kekekasvi.com

PLAY SMS

http://playsms.org/

KANNEL

http://inuits.eu/blog/sms-server-using-centos-kannel-and-playsms

GOIP

http://blog.voptech.com/install-goip-sms-manager-server/#.Us45lvvhd8E

http://www.dbltek.com/pdf/GOIP_SMS_Server_English_Manual.pdf

http://www.ozekisms.com/index.php?owpn=697

GOIP

http://www.ultrative.com/down/UTT-GoIP_Manual.pdf

https://github.com/tangaza/Tangaza/wiki/Connecting-a-GoIP-GSM-VoIP-gateway-to-an-Asterisk-AGI

By , December 30, 2013 12:39 PM

thread_cache_size: Thread creation/destructions can be expensive, which happen at each connect/disconnect. I normally set this value to at least 16. If application has large jumps in amount of concurrent connections and I see fast growth of Threads_Created variable I boost it higher. The goal is not to have threads created in normal operation. See http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-server-after-installation/

The number of threads that are kept in the cache for reuse. This variable can be increased to improve performance if you have a lot of new connections. Increasing this value increases the number of file descriptors that mysqld requires. See http://www.interworx.com/support/docs/nodeworx/mysql/howto-mysql-options

thread_cache_size: How many threads the server should cache for reuse. When a client disconnects, the client’s threads are put in the cache if there are fewer than thread_cache_size threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. Normally, this does not provide a notable performance improvement if you have a good thread implementation. However, if your server sees hundreds of connections per second you should normally set thread_cache_size high enough so that most new connections use cached threads. By examining the difference between the Connections and Threads_created status variables, you can see how efficient the thread cache is.

**Threads_created (status variable): The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. The cache miss rate can be calculated as Threads_created/Connections. **

Connections (status variable): The number of connection attempts (successful or not) to the MySQL server.

Threads_connected: The number of clients currently connected to the server. If its value is often close to the value of max_connections, it might be good to increase the value of max_connections to allow more connections. If clients that should be able to connect frequently cannot, that too is an indication that max_connections is too small. Each active connection handler / thread requires some memory, so you don’t necessarily want to set max_connections to the number of threads allowed by the operating system.

Each thread that is used to manage client connections uses some thread-specific space. The following list indicates these and which variables control their size:

A stack (default 192KB, variable thread_stack)
A connection buffer (variable net_buffer_length)
A result buffer (variable net_buffer_length)

The connection buffer and result buffer both begin with a size given by net_buffer_length but are dynamically enlarged up to max_allowed_packet bytes as needed. The result buffer shrinks to net_buffer_length after each SQL statement. While a statement is running, a copy of the current statement string is also allocated. See http://www.learn-mysql-tutorial.com/TuneMySQL.cfm

MYSQL Tuning

By , December 30, 2013 12:39 PM

MyISAM Key Buffer Usage

 key_buffer_size

For MyISAM one of the most important variables is the Key Buffer.  The Key Buffer is sometimes called the Key Cache. It’s used as a buffer for the indices of MyISAM tables. There is some overhead in the buffer depending on the configured key block size.

Set up to 30-40% of available memory if you use MyISAM tables exclusively. 2-4 MB minimum; dedicating GBs can be a waste.

 

 

 

 

thread_cache_size:
Thread creation/destructions can be expensive, which happen at each connect/disconnect. I normally set this value to at least 16. If application has large jumps in amount of concurrent connections and I see fast growth of Threads_Created variable I boost it higher. The goal is not to have threads created in normal operation. See http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-server-after-installation/

The number of threads that are kept in the cache for reuse. This variable can be increased to improve performance if you have a lot of new connections. Increasing this value increases the number of file descriptors that mysqld requires. See http://www.interworx.com/support/docs/nodeworx/mysql/howto-mysql-options

thread_cache_size: How many threads the server should cache for reuse. When a client disconnects, the client’s threads are put in the cache if there are fewer than thread_cache_size threads there. Requests for threads are satisfied by reusing threads taken from the cache if possible, and only when the cache is empty is a new thread created. This variable can be increased to improve performance if you have a lot of new connections. Normally, this does not provide a notable performance improvement if you have a good thread implementation. However, if your server sees hundreds of connections per second you should normally set thread_cache_size high enough so that most new connections use cached threads. By examining the difference between the Connections and Threads_created status variables, you can see how efficient the thread cache is.

**Threads_created (status variable): The number of threads created to handle connections. If Threads_created is big, you may want to increase the thread_cache_size value. The cache miss rate can be calculated as Threads_created/Connections. **

Connections (status variable): The number of connection attempts (successful or not) to the MySQL server.

Threads_connected: The number of clients currently connected to the server. If its value is often close to the value of max_connections, it might be good to increase the value of max_connections to allow more connections. If clients that should be able to connect frequently cannot, that too is an indication that max_connections is too small. Each active connection handler / thread requires some memory, so you don’t necessarily want to set max_connections to the number of threads allowed by the operating system.

Each thread that is used to manage client connections uses some thread-specific space. The following list indicates these and which variables control their size:

  • A stack (default 192KB, variable thread_stack)
  • A connection buffer (variable net_buffer_length)
  • A result buffer (variable net_buffer_length)

The connection buffer and result buffer both begin with a size given by net_buffer_length but are dynamically enlarged up to max_allowed_packet bytes as needed. The result buffer shrinks to net_buffer_length after each SQL statement. While a statement is running, a copy of the current statement string is also allocated. See http://www.learn-mysql-tutorial.com/TuneMySQL.cfm

After Hours Doctors After Hours Doctors