Jump to content

Early Firmware and EScribe Suite Discussion Thread


Recommended Posts

3 hours ago, James said:

AMDtrucking, you are still running SP35? Does it occur with SP38 for you?

Still SP35. I will load SP38 and report back.

I spoke too soon. There was a link to SP38 in this thread, but the owner removed the file. Where do I get SP38?

Never mind, it's in SetupEScribe2_SP19_INT_ServicePack 

SP38.PNG

Edited by AMDtrucking
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...

@James First: Thank You for Your Efforts

I confirm the "Error press up"-bug ("Epu") still exists in firmware SP38

I first encountered the Epu after updating to Escribe SP17 and firmware SP35. Until that day my device ran perfect in Replay-mode.

After about 7 days messing with about everything in Escribe (not changing the Theme however) I downgraded back to firmware SP33.2. After that the "Epu" never appeared again for 10 days in a row.

Today I installed Escribe SP19 and firmware SP38. After letting the mod sleep for 15+ minutes (not before, I tested), the "Epu" appeared again. It could be repeated again and again by pressing "Upload settings to device" in Escribe. Same with "Restore Defaults": After the upload "Epu" appeared on the screen. I could only end this behavior by taking the batteries from the mod. Afterwards I tried again, letting it sleep for 15+ minutes, "Epu" showed, same behavior with Escribe.

2,5 hours ago I downgraded again to SP33.2, and couldn't get the "Epu" to appear on screen again, letting it sleep several times between 15 and 35 minutes.

Hopefully this helps you and Evolv a little. My device is a LV Paranormal DNA 250C with a board programmed May 25th, 2018. Please excuse my English!

Link to comment
Share on other sites

i can also confirm the Error press up happening with SP38

mod is the lost vape 250c 

for me i have seen it happen more with inactivity and a few when sending profile updates my device was from september going back to Core it has yet to happen. the device was first updated then used until the error was frequent between uses . after reverting it has yet to happen with the same use pattern and all. 

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

DO NOT UPLOAD SP38 to Orion 40W it will not complete.

I tried manually updating to SP38 on my orion and now it just blinks red. any one have any advice to reset to factory settings or previous versions? I tried restoring my settings to factory settings and my mac says cannot find serial number or there is an error with uploading the SP38 operating software. ive already redownload-ed escribe and with high hopes even the international version but no luck. my orion has no bricked with a blinking red light.  if anyone knows a solution please let me know.IMG_8430.thumb.JPG.9b0c7d1c7916537320965caed5d4b1d3.JPG

IMG_8429.JPG

Link to comment
Share on other sites

  • 4 months later...
  • 3 weeks later...

Problem with new Windows 10 1903.

The monitoring windows display the value and graph, but after a small time, graph does not progress even if the value on the left part seems updated, and another small time after, the value on the left part also also no more updated (they stay fix).

Before, with previous version of Windows 10 (1803), i don't have this problem.

Does anyone also have experienced this ?

Link to comment
Share on other sites

Not experiencing this with my Win10 with the latest Windows updates installed..  I ran Device Monitor just now and let it run for many, many minutes.  If you look at the lower left corner of the graph you will see a left pointing arrow. A right pointing arrow is in the lower right corner of the graph.  The slider between these arrows moves from left to right as the monitor is running and the graph is always updating along the way.  At some point the slider will reach the right arrow (takes a long, long time to get there). I let it run for over 15 minutes and the slider has not reached the right arrow yet so I don't know if it stops updating the graph when it reaches the right arrow or not.  The longer it runs the slower the slider moves.

You might connect a device that needs charging and let it run and take a vape every 5 minutes or so to see if it still is updating the graph...  

UPDATE: over 25 minutes and still running....

Link to comment
Share on other sites

Thanks Retird ;-)

The situation is now more bad. As you, i think now that it is not a Windows problem, but a DNA250C Chipset problem.

Now, my Paranormal does not want to unlock, i have try to verify all the parameter and when i send the data, i get an eerom error.

I have try to flash the firmware, with success… but no change.

And now, after a lot of attempt to unlock, i see something very strange with the button… fire act as fire but also as up, select act as up or does not respond…… seems a big problem now.

Well…. this box has 1 year and 2 months…. and is mostly dead.

 

Link to comment
Share on other sites

  • 5 months later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...