NI cDAQ-9191 Mobile Device Support Discussion

[JoeFriedchicken]

NITKR wrote:

The following image is how it looks like in the Settings page of the APP. When I clicked it, the error message popped up as "Device Error Invalid chassis firmware. Upgrade chassis firmware".

This happens when the DAQ web API doesn't return the correct response headers. Since you can use the system service from a browser, I'm surprised that you are receiving this error. Would you use your browser again and also share the response headers?

When I capture the headers, I see:

Server: Mbedthis-Appweb/2.5.0

Keep-Alive: timeout=60000, max=100

Date: Thu, 01 Jan 1970 00:04:31 GMT

Content-Type: application/json

Content-Length: 454

Connection: keep-alive

Cache-Control: no-cache

Firefox will let you capture the headers like this.

1. Show the web developer console from the Tools menu and selecting Web Developer » Web Console. In the image below, also check "Log Request and Response Bodies" in addition to "Log".
   
2. Force-refresh the system service page with Ctrl-Shift-R (or Command-Shift-R for Mac).
3. Click the GET request line.
4. Inspect the response headers.

NITKR wrote:

Then, I went to the system page and got the same API output as shown in my last post.

Ok, thanks for testing again.

NITKR wrote:

By the way, because I used the ad-hoc connection. I couldn't use my iPhone to check the API output. I used my laptop by connecting the cDAQ 9191 to the network with a Ethernet cable.

Would you clarify what you mean by 'ad-hoc'? How did you configure the 9191 chassis?

NITKR wrote:

Have you tried using iPhone for ad-hoc connection? I tried a different iPhone also running iOS 8. That iPhone couldn't even connect to the device.

Yes, that is what I wrote in my previous message. The 9191 doesn't broadcast its SSID well enough for iOS 8 to fully detect, so the Settings app doesn't show it. However, if you tap "Other..." in the Wi-Fi pane and enter the 9191's SSID, you can connect.

What other iOS versions do you have?

[NITKR]

Hello,

Here is the response header I got:

Server: Mbedthis-Appweb/2.5.0

Keep-Alive: timeout=60000, max=100

Date: Thu, 01 Jan 1970 00:10:27 GMT

Content-Type: application/json

Content-Length: 448

Connection: keep-alive

Cache-Control: no-cache  

"Ad-Hoc" means that I used the chasiss creating a network instead of adding it to a network via a router.

I tried an IPad with IOS 7.02, an IPhone with IOS 8, IOS 8.1 and 8.2. With all of them, I got the same error message. Do you think whether it is related to the NI 9215 I used or not? I used one with screw terminals. In your case, you used one with BNC.   Thank you very much for your help.

[JoeFriedchicken]

NITKR wrote:

Here is the response header I got

Ok, no problems there, which increases the mystery 😕

NITKR wrote:

"Ad-Hoc" means that I used the chasiss creating a network instead of adding it to a network via a router.

Ok, thanks. I can confirm that this configuration works for me.

NITKR wrote:

Do you think whether it is related to the NI 9215 I used or not? I used one with screw terminals. In your case, you used one with BNC.

No, both the screw terminal and BNC modules work.

At this point, I am beginning to run out of diagnostics to run. If you want to continue troubleshooting, then there are two ways:

1. I use your chassis and module to debug by either:

A. you sending both chassis and module to NI, or

B. you giving your 9191 a public IP address so I can connect to it from NI

2. You use your chassis and module to debug by using the web API and iOS sample code [1].

Alternatively, you can create your own custom user interface with Data Dashboard [2] by using LabVIEW Web Services [3] [4] [5]

[1] NI cDAQ-9191 Web API Documentation & Examples

https://decibel.ni.com/content/docs/DOC-21477

[2] Data Dashboard

http://www.ni.com/mobile/

[3] LabVIEW Web Services

http://www.ni.com/tutorial/13757/en/#toc5

[4] Integrating NI Data Dashboard for LabVIEW into your LabVIEW Applications

http://www.ni.com/white-paper/14689/en/

[5] Web Services - Best Practices and Examples

https://decibel.ni.com/content/docs/DOC-17328

[NITKR]

I will send you the devices. Please let me know your name and address. My email is victor.li@timken.com. Thank you very much.

[JoeFriedchicken]

Ok, I can begin preparations for receiving the devices.

Allow me to outline what I can do and what will happen. Since the firmware update and iOS app are part of the NI Labs community, neither are treated as fully supported products. Here is how I can help:

1. If there is a configuration problem, then I can report what I found and how I changed it to fix the problem in this forum.
2. If there is a bug in the app or firmware, then I can report it in this forum, and further
   • if there is a workaround, I can report that here, too.
   • if there is no workaround, I can create an internal bug ticket and report the bug ID in this forum.

Please be aware that NI makes no guarantees that bugs found in NI Labs projects will be fixed or released. In this situation, the best way to move forward is to use the web API in your own native app or use LabVIEW Web Services and Data Dashboard for configuring and retrieving data from your iOS devices.

In all cases, I will return the devices to you.

[NITKR]

Thanks. I appreciate all your effort. Please email me your address to which I can send the device.

[JoeFriedchicken]

To close the loop on the problem Victor encountered --

1. After updating the 9191's firmware,
2. Delete the app from the iOS device,
3. Re-download and install the app, and
4. Use the 9191's IP address for the device.

There appears to be a bug in the iOS app where the app incorrectly caches invalid device information that prevents a valid device from being used.