punksofada Posted October 16, 2015 Author Report Posted October 16, 2015 Windows 7 ultimate. Vt200. It sees the device, I can monitor the device . When I try to download or upload settings I get a communication failure message, usually EEPROM read failed . I have tried numerous usb cables, has not worked once.
VapingBad Posted October 16, 2015 Report Posted October 16, 2015 There were 2 people who's USB keyboard caused problems if you have one try unplugging it temporally.
punksofada Posted October 16, 2015 Author Report Posted October 16, 2015 Sorry, should have stated, this is on a laptop with nothing else connected.
VapingBad Posted October 16, 2015 Report Posted October 16, 2015 It was a long shot, not had the problem so don't have any advice other that different cables which you have already tried.
punksofada Posted October 16, 2015 Author Report Posted October 16, 2015 I've been messing with it for about 8 hours. Bad first impression, I'm so fed up I'm about to smash it.
VapingBad Posted October 16, 2015 Report Posted October 16, 2015 That sucks mate, but it is very usual, I know that is little comfort.
Nick Posted October 16, 2015 Report Posted October 16, 2015 No need to be frustrated! Shoot us a ticket and we will get you taken care of. http://helpdesk.evolvapor.com/index.php?a=add
James Posted October 17, 2015 Report Posted October 17, 2015 punksofada, what firmware is your device running? (What version in Device Monitor?)If it is 2015-06-02, you will definitely need to update your firmware before uploading/downloading. That was a beta firmware that manufacturers were supposed to update to release firmware before shipping. A few didn't, unfortunately. Manufacturers are supposed to run all their mods through Production Utility as well for final functional test, which would specifically prevent this, but, again, a few don't. Most do, thankfully... So, update your firmware, and it will work perfectly. If your firmware is fairly recent, try the 9/3 or 9/30 EScribe in the Early Firmware thread. Those have longer timeouts for slower PCs and for computers running Windows under virtualization (Macs for instance).
punksofada Posted October 17, 2015 Author Report Posted October 17, 2015 Device is on version 2015-08-21. I just tried the 9/3 firmware and it's doing the same thing. I guess I'll give another version a shot. Edit: I did a hard reboot and then tried downloading settings, and it got almost done before the error popped up this time. I'm thinking it may be my computer being slow. That was the most I'd seen it do
James Posted October 17, 2015 Report Posted October 17, 2015 Interesting. How far along in the status bar does it go before you get the error? And what other errors are you getting?
punksofada Posted October 17, 2015 Author Report Posted October 17, 2015 Usually it was right away before it showed any progress, but after rolling back the escribe version and a hard reboot, this time it got about 3/4
James Posted October 17, 2015 Report Posted October 17, 2015 Hmm. I was going to make a small EScribe update on Monday. "EEPROM read failed" is a very generic error -- nearly all underlying errors while uploading/downloading will give it. I'll add a debug feature to Monday's release to make it possible to get at the underlying error message. All other functions - Tools->Reboot Device, Tools->Show Serial Number, etc. all work perfectly? Does Device Monitor say 'error' in the fields at any consistent rate?
punksofada Posted October 17, 2015 Author Report Posted October 17, 2015 I finally got it to work once. Seemed really slow, but did work. I'm thinking it may be a pc issue. I set the priority higher in task manager. Lol. I don't know if that helped or just by chance it wanted to work right after that. I just want to clarify that the pc I'm using isn't exactly new, so that could be the problem. But I really appreciate the help. I'm gonna keep fiddling with it and see if I can get it working a little smoother.
punksofada Posted October 17, 2015 Author Report Posted October 17, 2015 Not getting errors anywhere else except when trying to upload and download. It seems the monitor is working flawlessly. The reboots work flawlessly as well. The only other error I got every once in a while said "can't figure out device version" or something very similar, I can't quite remember. The first thing I did when I connected the device for the first time was update the firmware on the device, so it has been up to date the whole time I believe.
punksofada Posted October 17, 2015 Author Report Posted October 17, 2015 It actually works every time now with the older version of escribe. It's almost like it was timing out instantly before. Like iI said, it's slow, but it's getting the job done so I'm happy. Lovin' it now.
James Posted October 19, 2015 Report Posted October 19, 2015 Hmm. What version of EScribe are you running that works? 9/3 and 9/30 both time out and do not work for you? (What firmware version right now?)
punksofada Posted October 19, 2015 Author Report Posted October 19, 2015 9/3 is working for me. I didn't try 9/30 yet. The first time I tried to connect on 9/3 it timed out but it's worked every other time after that.
blueridgedog Posted October 19, 2015 Report Posted October 19, 2015 Sounds a lot like the USB timeout associated with running an operating system in a virtual environment, so there is probably some lag going on at the PC level slowing things down. One way I have addressed that in the past is to make a new user account and log in as that user as that often bypasses a great deal of startup related items that people tend to collect over the years.
James Posted October 21, 2015 Report Posted October 21, 2015 punksofada, I've made a version (2015-10-20 1.0.35) that can show the underlying error message. It's in the Early Firmware thread in the Software and Firmware forum. To unlock the full error details, go to Help->About and left click on the Evolv logo seven times. After that, it will show the error details along with the error.
jcwest Posted December 2, 2017 Report Posted December 2, 2017 Same exact thing happend to me was abad USB cable, got a new one things work fine
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now