Android Devices with N-Scan 6.0

Hi Rathi,

We’re in the midst of testing the MC40 Android-based ticket scanners with N-Scan 6.0. So far, it has been going well; we have successfully scanned multiple tickets for entry and exit. It seems to be paying attention to key error conditions, like a ticket for the wrong performance, wrong date/time, etc.  

I have had a couple of times when N-Scan on the Android stopped retrieving data when getting seat information after I made network configuration changes to them. A reboot of the device resolved that issue. We’ll be hitting them harder the next two weeks, so I’ll know more soon as to whether that is an actual N-Scan 6.0 issue or was just some quirk due to changing Android settings on the device.

Assuming no major issues come up in our continued testing, we’re hoping to go live with the new MC40 scanners and N-Scan 6.0 late this month.

Thanks,

David

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Rathi Kumar
Sent: Wednesday, September 10, 2014 6:36 AM
To: David Frederick
Subject: [Tessitura Technical Forum] Android Devices with N-Scan 6.0

Hi,

I was wondering if anyone out there has started the process of testing or is currently using in a live environment Android devices with N-Scan 6.0 and if so how it's going?

We're still having a heck of a time making our MC55s work consistently and so our next thought is to try out an Android device concurrently with our MC55s to see if the same issues arise.

If anyone has advice on how Android devices seem to fare and suggestions on models, I'd appreciate it.

Thanks,
Rathi 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Hi David,

Thanks for the reply.  It would be great if you could keep me in the loop as to how you guys get on.

We’ve been having a lot of issues with our MC55s where they drop their connection to the server in the middle of an ingress even though they are all rebooted and working at the start of the evening, so I’d be curious to know if you guys experience the same sort of thing with the MC40s.

Hi Rathi,

We’re in the midst of testing the MC40 Android-based ticket scanners with N-Scan 6.0. So far, it has been going well; we have successfully scanned multiple tickets for entry and exit. It seems to be paying attention to key error conditions, like a ticket for the wrong performance, wrong date/time, etc.  

I have had a couple of times when N-Scan on the Android stopped retrieving data when getting seat information after I made network configuration changes to them. A reboot of the device resolved that issue. We’ll be hitting them harder the next two weeks, so I’ll know more soon as to whether that is an actual N-Scan 6.0 issue or was just some quirk due to changing Android settings on the device.

Assuming no major issues come up in our continued testing, we’re hoping to go live with the new MC40 scanners and N-Scan 6.0 late this month.

Thanks,

David

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Rathi Kumar
Sent: Wednesday, September 10, 2014 6:36 AM
To: David Frederick
Subject: [Tessitura Technical Forum] Android Devices with N-Scan 6.0

Hi,

I was wondering if anyone out there has started the process of testing or is currently using in a live environment Android devices with N-Scan 6.0 and if so how it's going?

We're still having a heck of a time making our MC55s work consistently and so our next thought is to try out an Android device concurrently with our MC55s to see if the same issues arise.

If anyone has advice on how Android devices seem to fare and suggestions on models, I'd appreciate it.

Thanks,
Rathi 

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Rathi:

We had a lot of trouble with our MC55s dropping connectivity too, until we separated our wireless traffic on our access points.  We installed additional wireless access points specifically for the NScan units only, and we limit connectivity to those access points to the MAC addresses of our MC55 units.  That has helped a great deal.  We still have an occasional disconnect, so we try to have a booted spare scanner on stand-by to switch to quickly while we reboot the dropped device, but not near as much trouble as we had before separating the traffic on the access points.  If you don’t already have your network setup that way, it might be something to try.

Penny Tabor

Director of IT

Midland Center for the Arts

Midland, MI 48640