yaxin.zhang@rl-test.net - can you attach the device logs from the chromebox.

"Our developer has reviewed the codes and confirmed the function call chrome.usb.bulkTransfer() got error message – Transfer timed out."

jennyz@ / hychao@ - looks like chrome api timing out. Please take a look.. thanks

I am not familiar with usb extension. Add reillyg@.

I believe we have one of these devices in MTV. If someone on the CfM team can find it I can take a look at why the behavior has changed.

Please provide the instruction to retrive the device log from the chromebox.

Attached is the log from chromebox. Please let me know if it includes the information you look for.

Deleted: net-internals-log.json 2.6 MB

net-internals-log.json 2.6 MB View Download

Re. #6,
1. In chrome go to chrome://net-internals
2. Select "ChromeOS" 
3. Click on "Store Debug Logs", this will save the logs in the downloads folder that you can attach to this bug.

Re. #5, are you referring to Revolabs UC 500 USB? We have this here in bld 40 that you are welcome to grab for debugging.

chrome://net-internals are not relevant for this bug. I'll pick up the device and look at it this afternoon.

After unpacking the attached extension Chrome reports a number of errors in manifest.json and uc500background.js. Once the application launches it reports that the device is disconnected even though calling chrome.usb.getDevices() and chrome.hid.getDevices() from the console shows that the device is accessible to the app. Please correct these errors so I can continue to diagnose the Chrome regression.

I've forwarded the message to our developer, he'll take a look.

Our developer has corrected the errors. Attached is the new version of the Chrome extension. I also include the information of the lab I'm testing.

Chromebox Manufacturer		Asus
Chrome OS Release Channel		Dev
Chrome OS Update Date		July 26, 2016
Chrome OS Version		53.0.2785.29 dev (64-bit)
Chromebox Platform Version		8530.30.0 (Official Build) dev-channel panther
Chromebox Firmware Version		Google_Panther.4920.24.26
UC 500 Chrome Management App Version		1.0.21 (will be released in August)
UC 500 Bundle Version		2.6.0.91
UC 500 Model		10-FLXUC500-NA
UC 500 Date Code and Rev		626-VT Rev 24

Deleted: ChromeMgmtApp-1-0-21 (2).zip 526 KB

ChromeMgmtApp-1-0-21 (2).zip 526 KB Download

Please let me know the information of Revolabs UC 500 unit you're testing, including:

Model (such as "10-FLXUC500-NA") 
Serial Number (such as "VT4010011199")
Date Code (such as "626-VT")
Rev (such as "24")

Model: 10-FLXUC500-NA
Date Code: 446-VT
Rev: 10

When I plug it in the following is displayed on the app's console but it doesn't recognize the device as connected. Does this mean my device is too old? Is there a firmware update to install?

Plug device 10943:1280
detected device ID:  7

Since the current Chrome App doesn't work, it can only be upgraded via ChromeOS version 51 or Windows. Please let me know if you have a ChromeOS version 51 or Windows.

I've upgraded my device to the latest firmware version using a Windows machine. I notice a large difference between the data packet sent to the device when the version is requested by Chrome 54 on Linux vs. the native Windows app.

Chrome:

02 00 00 00 00 11 56 65  72 73 69 6f 6e 20 52 65
74 72 69 65 76 61 6c 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 70

Windows:
 
02 00 00 00 00 39 56 65  72 73 69 6F 6E 20 52 65
74 72 69 65 76 61 6C 00  3C 01 20 5F 39 01 00 56
3C 01 14 38 3C 01 50 FB  FE 02 4E 98 FE 00 01 00
00 00 00 00 00 00 34 A9  39 01 28 4F 3A 01 00 1A

I tried downgrading Chrome on Linux to 51 and still could not retrieve version information with the app in comment 12. When it receives the request from Windows the device responds immediately with a version string. When it receives the request from Chrome on Linux no response is sent and the request eventually times out.

Can you let me know what you see from the "Software Version" window. My lab unit is:

Bundle version:  2.6.0.91
USB version:     5.7
DSP version:     2.7

I also forwarded the message to our developer, he assumed the timeout might be same as what we see on ChromeOS Dev 53. He asked to make sure the UC 500 has build 91 or 92

Device versions are:

Bundle version:  2.6.0.91
USB version:     5.7
DSP version:     2.7

I don't think this is a regression in Chrome 52. I found a Chromebook with Chrome 51 and I was initially able to read the software versions from the device but if I disconnected and reconnected the device it would sometimes fail in the same was as on Chrome 52. Looking at the application source the flush function looks suspicious because it seems to assume that there will be data ready to read from the device. The output from my USB analyzer box shows that the device is NAKing the request until it times out.

I've forwarded above message to our developer, he'll look into it.

Our developer made some change, I can retrieve device version with ChromeOS 53 now. I'll rerun the regression testing again.

Problem is fixed by our developer. Thank you for helping. Please close the ticket.