Evolv DNA Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 5 of 70     «   Prev   2   3   4   5   6   7   8   Next   »
Tpat591

Junior Member
Registered:
Posts: 29
Reply with quote  #61 
Quote:
Originally Posted by Tpat591
Quote:
Originally Posted by laadam

Just tried the new update, 2015-08-05 EScribe, 2015-07-29 R1 firmware.
It forced a new USB driver install that put EScribe into a "not responding" state.
Bricked my V200.  Closed everything through task manager and re-opened.
Using the tools menu, I forced the firmware upgrade and everything is up and running.
However, I lost all data and settings... like a factory reset!
BTW, running Win7 32bit


Just did same thing with the 8/7 update.

Accidentally left my Hana V200 connected via usb while I ran the https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe

Everything went fine on install but when it prompted to update the firmware to the 2015-08-07.sw-update
it started to download, the little box flashed, screen went dark on V200 & got error message that no device was connected on repeated tries.

Pressing fire button on device reboots device and escribe can see it if I connect through device monitor & appears to work.  Pulled cable & reloaded https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe completely same thing happens when I try to update firmware, even when I try to roll it back to 2015-07-16.sw-update.

Rebooted Win8.1 64bit computer & uninstalled escribe completely reinstalling program...no change.

Tried installing same update on win7 64bit machine.  Same thing.  Cannot update firmware at all on HanaV200 due to unit shutting down during firmware update.  I can only access unit in device manager after hitting fire button to reboot.

Just pulled escribe from win7 machine & rebooted w/ intention to go back to stable release escibe & load it but that is release I had on win7machine when I first rebooted the win 8.1 machine & had communication issues there too.

Cable is one that came with hana & have been using without issue since I got it.  Just tried to roll back to 2015-07-16.sw-update on the clean install of stable release & same issue exists.

Think I screwed up the Hana?  What process did you kill in Device Manager to Fix yours?



James, John, or Branden do you have any advice on how to proceed considering conditions described above?  is there a command line command to diagnose integrity of board programming & operation of device itself to determine why it will not accept firmware updates?













jolley

Junior Member
Registered:
Posts: 9
Reply with quote  #62 
Quote:
Originally Posted by David Campbell
Crickets is probably a good sign [smile] I've been running this for a couple days and haven't had any issues.

In unrelated news, the FreeMax Starre Pro (unexpectedly) sets a new high bar for TC tanks with pre-made coils.


How about Freemax Starre pro tank? It is said that is great. Has someone tried?
blueridgedog

Avatar / Picture

Moderator
Registered:
Posts: 573
Reply with quote  #63 
Quote:
Originally Posted by Tpat591

James, John, or Branden do you have any advice on how to proceed considering conditions described above?  is there a command line command to diagnose integrity of board programming & operation of device itself to determine why it will not accept firmware updates?


Have you tried a hard reboot in escribe?  Have you tried a battery removal for a hard reboot?

If you pull the battery, then reinstall the battery, reboot your computer, plug in the DNA200, launch escribe and then attempt a manual firmware update that fails, the next step I recommend is a help desk ticket for a replacement.


laadam

Member
Registered:
Posts: 69
Reply with quote  #64 
Quote:
Originally Posted by Tpat591
Quote:
Originally Posted by laadam

Just tried the new update, 2015-08-05 EScribe, 2015-07-29 R1 firmware.
It forced a new USB driver install that put EScribe into a "not responding" state.
Bricked my V200.  Closed everything through task manager and re-opened.
Using the tools menu, I forced the firmware upgrade and everything is up and running.
However, I lost all data and settings... like a factory reset!
BTW, running Win7 32bit


Just did same thing with the 8/7 update.

Accidentally left my Hana V200 connected via usb while I ran the https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe

Everything went fine on install but when it prompted to update the firmware to the 2015-08-07.sw-update
it started to download, the little box flashed, screen went dark on V200 & got error message that no device was connected on repeated tries.

Pressing fire button on device reboots device and escribe can see it if I connect through device monitor & appears to work.  Pulled cable & reloaded https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe completely same thing happens when I try to update firmware, even when I try to roll it back to 2015-07-16.sw-update.

Rebooted Win8.1 64bit computer & uninstalled escribe completely reinstalling program...no change.

Tried installing same update on win7 64bit machine.  Same thing.  Cannot update firmware at all on HanaV200 due to unit shutting down during firmware update.  I can only access unit in device manager after hitting fire button to reboot.

Just pulled escribe from win7 machine & rebooted w/ intention to go back to stable release escibe & load it but that is release I had on win7machine when I first rebooted the win 8.1 machine & had communication issues there too.

Cable is one that came with hana & have been using without issue since I got it.  Just tried to roll back to 2015-07-16.sw-update on the clean install of stable release & same issue exists.

Think I screwed up the Hana?  What process did you kill in Task Manager to Fix yours?



EScribe hung for me and was not responding.  I had to use Task Manager to close EScribe then restart the program.  Using the drop down menu across the top, used the update option and forced it into the chip.  Everything worked for me after that
James

Avatar / Picture

Administrator
Registered:
Posts: 304
Reply with quote  #65 
Quote:
Originally Posted by Tpat591

Pressing fire button on device reboots device and escribe can see it if I connect through device monitor & appears to work.  Pulled cable & reloaded https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe completely same thing happens when I try to update firmware, even when I try to roll it back to 2015-07-16.sw-update.


How do you know pressing the fire button reboots the device specifically? What behavior are you seeing? Does something display on the device screen? If you see anything on screen, that rules out it being a firmware issue. If Device Monitor works then your firmware is working. What are you seeing for battery voltage? I wonder if something is wrong with your battery connector. When you use Device Monitor, are you able to fire? Or does it say CHECK ATOMIZER? (What are the battery voltages reading? Keep in mind, battery voltage is read over the balancer taps, whereas power actually comes from the main connector (JST in the Hana's case).)
Tpat591

Junior Member
Registered:
Posts: 29
Reply with quote  #66 
Quote:
Originally Posted by James
Quote:
Originally Posted by Tpat591

Pressing fire button on device reboots device and escribe can see it if I connect through device monitor & appears to work.  Pulled cable & reloaded https://www.dimensionengineering.com/software/SetupES_2015-08-07.exe completely same thing happens when I try to update firmware, even when I try to roll it back to 2015-07-16.sw-update.



How do you know pressing the fire button reboots the device specifically? What behavior are you seeing? Does something display on the device screen? If you see anything on screen, that rules out it being a firmware issue. If Device Monitor works then your firmware is working. What are you seeing for battery voltage? I wonder if something is wrong with your battery connector. When you use Device Monitor, are you able to fire? Or does it say CHECK ATOMIZER? (What are the battery voltages reading? Keep in mind, battery voltage is read over the balancer taps, whereas power actually comes from the main connector (JST in the Hana's case).)


My issue unfolded in this thread:http://evolvapor.forumchitchat.com/post/escibe-and-device-monitor-always-seem-to-want-to-always-open-in-full-screen-mode-7540247?pid=1288251932#post1288251932

On firmware upload the "Please Wait" progress box will flash for a minute, device goes dark & will not respond to any communication.  Pressing fire button on device powers it up again and will restore serial communication but not in firmware update.  I have tried pressing fire button to repower device through the firmware update but it will return error on computer screen command failed.

Unit appeared to be operating correctly independent of this vaping a Lemo 2 with twisted 28ga ni200 .07ohm build @ 360deg until on one vape I had 2 separate 1sec full 200w spikes on the preheat graphed on the device monitor that blew apart my build in the lemo and gave me a lungful of fire the taste of which I cannot describe.  I was so busy choking on the lungful that I did not think to do a screenshot before it timed out on the device monitor.  Apparently it slipped into kanthal mode and blasted 200w even though unit was set for 24w.  Perhaps under vaping conditions my build loosened at a screw contact but that never should have happened.  Since then the Hana serial cable has developed communication issues and I am using another serial cable I happened to have around.  All this happened yesterday afternoon.
Hanav200 error message.png  Hanav200 subtank trace.png 
These were done with a subtank equipped with a ni200 occ as I have not rebuilt the Lemo2.  This hana is equipped w/ jst rcy connector that does not appear melted down but i am having trouble separating it.  Prior to the Lemo2 coil burnout my preheat spikes were approaching the height of the power checkbox on the left.  The double spike when the coil burned out went above the battery indicator line as high as the charge box.

Tpat591

Junior Member
Registered:
Posts: 29
Reply with quote  #67 
Forgot to post 1st error message screen experienced after Hana screen goes dark on firmware update.

Hanav200 error message1.png this happens on any firmware update (no matter the firmware version date) attempt on 2 separate computers with 2 separate versions, 2 separate operating systems, clean installs, stable version vs 8/7 version.  I'm at a loss.  I had previously sent service tickets to hana about how the plan to swap out the substandard jst rcy connectors on 2 occasions and they have not seen fit to reply.  Their customer service is horrible & I think Evolv should threaten to stop selling to them if they don't get their act together.

retird

Avatar / Picture

Administrator
Registered:
Posts: 1,187
Reply with quote  #68 
RE: Not Connected error message.  I saw that message 4 times while trying 4 different USB cables.  Bought a new quality USB data cable and no more error message.  No saying that is your issue but it was mine. 
__________________
I am not an employee of and do not represent Evolv Inc.  My opinions are just that and are not meant to be fact or even correct.

Tpat591

Junior Member
Registered:
Posts: 29
Reply with quote  #69 
Quote:
Originally Posted by dc601
RE: Not Connected error message.  I saw that message 4 times while trying 4 different USB cables.  Bought a new quality USB data cable and no more error message.  No saying that is your issue but it was mine. 

Well I'm up to 10 cables I have here in house w/ same issue.  It would be really cool diagnostic tool if the Dna200 had a loopback feature so a USB cable's integrity could be tested from within escribe to rule out a bad cable.

That error box goes away when the fire button on the mod is pressed and screen display lights up again.
James

Avatar / Picture

Administrator
Registered:
Posts: 304
Reply with quote  #70 
Once you hit the Fire button, does it stay on? That'd narrow it down between a USB Voltage reading issue and a sleep pin related issue.
James

Avatar / Picture

Administrator
Registered:
Posts: 304
Reply with quote  #71 
Posted the 2015-08-17 EScribe. Same firmware as 2015-08-07, adds the option of installing ECigStats.
basilray

Member
Registered:
Posts: 36
Reply with quote  #72 
Still no Windows 10 love.  I think James doesn't want me messing w/ my profiles. [tongue]

HolmanGT

Avatar / Picture

Member
Registered:
Posts: 41
Reply with quote  #73 
Quote:
Originally Posted by basilray
Still no Windows 10 love.  I think James doesn't want me messing w/ my profiles. [tongue]



Are you saying Escribe is not working for you on Windows 10?
branflan

Junior Member
Registered:
Posts: 1
Reply with quote  #74 
Quote:
Originally Posted by HolmanGT
Quote:
Originally Posted by basilray
Still no Windows 10 love.  I think James doesn't want me messing w/ my profiles. [tongue]



Are you saying Escribe is not working for you on Windows 10?


I've been using EScribe on Windows 10 since the OS was released on 7/29 with no issues whatsoever. 
basilray

Member
Registered:
Posts: 36
Reply with quote  #75 
Quote:
Originally Posted by branflan
Quote:
Originally Posted by HolmanGT
Quote:
Originally Posted by basilray
Still no Windows 10 love.  I think James doesn't want me messing w/ my profiles. [tongue]



Are you saying Escribe is not working for you on Windows 10?


I've been using EScribe on Windows 10 since the OS was released on 7/29 with no issues whatsoever. 


I haven't been able to use EScribe since upgrading from Win Pro 8.1 x64 to Win 10 Pro x64.  I was in the beta, and had zero issues w/ the software in Win 8.1, so it's weird.

The app opens, but is 100% unresponsive after it opens.  I have tried everything short of a new install of Windows...
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.