We deployed an XP6/T2x combo today and encountered a problem. The initial USB download to each device went well (XP6 was configured for static IP, the T2x for dhcp), and subsequent programming updates via network to both from ID were fast & smooth. After perhaps 25+ updates over the course of several hours, suddenly the XP6 updates via network stopped working, with an ID error (to my chagrin, I didn’t write it down) along the lines of “error during update, click here for troubleshooting.”

For what it’s worth, when I looked at the XP6 I found the status light was lit solid green, which – according to the manual – indicates that the processor has not been programmed. Running a network scan from within ID, though, both XP6 and T2x were found and “live” on the network, and the XP6 was responding to pings to the static IP address at which it’d been programmed.

I attempted multiple reboots of the XP6 and restarting ID, but network update attempts continued to fail. I was able to connect via USB and successfully apply ID programming, but subsequent attempts to do so via network still did not work. Any ideas on what may cause network update to suddenly fail, and how to address this?

EDIT: worth mentioning that both XP/T2x had been updated to most recent firmware as of 6/17.

Are you doing this via a real windows PC or a MAC running parallels or VMware?

Did you also try instead of downloading by MAC address to download to the specific IP of the devices?

PC - didn't realize IP was an option, I'll try that out when next onsite, thx!