# Troubles with V3 software

**URL:** <https://community.ecumaster.com/t/troubles-with-v3-software/4052>\
**Category:** V3 SOFTWARE\
**Created:** [July 11, 2025, 7:27pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052 "2025-07-11T19:27:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![JeanD](https://avatars.discourse-cdn.com/v4/letter/j/9e8a1a/32.png) [@JeanD](https://community.ecumaster.com/u/JeanD)\
**Post date:** [July 11, 2025, 7:27pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/1 "2025-07-11T19:27:09Z")

</div>

I have two problems with the V3:  
1- Very often, when I connect the PC to the ECU, it connects, the “live” values ​​work, as does the logging, BUT the maps are all “empty,” meaning all the values ​​remain empty, or at zero!  
The only way I’ve found to be able to work is to re-open a saved file…

2- The second problem encountered is with the “prime pulse”, I completed the table, but when I look closely at the PW injector in the logging, I do not see this first injection appear… I have the impression that it is not happening!

---

<div class="post-metadata">

**Author:** ![enkorn](https://avatars.discourse-cdn.com/v4/letter/e/e95f7d/32.png) [@enkorn](https://community.ecumaster.com/u/enkorn)\
**Post date:** [July 12, 2025, 6:13pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/2 "2025-07-12T18:13:01Z")

</div>

I confirm with the transition to v3 47+ version I also have the same bug on the started one I connect to the ecu and all my cards and parameters do not load, zeros everywhere, reconnection does not help, only recording the working firmware, I think this is because of the virtual Windows 7 that I use from the MacBook

---

<div class="post-metadata">

**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\
**Post date:** [July 13, 2025, 10:15am UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/3 "2025-07-13T10:15:43Z")

</div>

1. What software version do you use ? Is your laptop based on x86 or ARM architecture ?
2. You cannot see the prime pulse on PW log channel. It is independent. You can see it on the scope. Enable scope and start to crank the engine, when the first pulses from the trigger wheel appears the injectors execute prime pulse and it will be visilbe on the scope.

---

<div class="post-metadata">

**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\
**Post date:** [July 13, 2025, 10:18am UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/4 "2025-07-13T10:18:35Z")

</div>

I’ve checked the change log and the communication stuff wasnt modified in 3.047.  
In the old versions of the software there was such issue with the communication but it was solved. I will take a look what was the fix and try to improve it.

---

<div class="post-metadata">

**Author:** ![JeanD](https://avatars.discourse-cdn.com/v4/letter/j/9e8a1a/32.png) [@JeanD](https://community.ecumaster.com/u/JeanD)\
**Post date:** [July 13, 2025, 1:20pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/5 "2025-07-13T13:20:19Z")

</div>

I use the 3.051  
My computer is running Widows 11  
Thank you for your help

---

<div class="post-metadata">

**Author:** ![Jadzwin\_ECUMASTER](https://dub1.discourse-cdn.com/flex013/user_avatar/community.ecumaster.com/jadzwin_ecumaster/32/28_2.png) [@Jadzwin\_ECUMASTER](https://community.ecumaster.com/u/Jadzwin_ECUMASTER)\
**Post date:** [July 13, 2025, 3:39pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/6 "2025-07-13T15:39:15Z")

</div>

You can try this build. I’ve doubled the timeouts:

[https://www.ecumaster.com/files/EMU\_BLACK\_V3/EMUBlackV3Setup\_3\_053b.exe](https://www.ecumaster.com/files/EMU_BLACK_V3/EMUBlackV3Setup_3_053b.exe)

You can also try to download the latest drivers from FTDI (2.12.36.20)

> **[D2XX Drivers - FTDI](https://ftdichip.com/drivers/d2xx-drivers/)**
>
> Est. reading time: 5 minutes

---

<div class="post-metadata">

**Author:** ![enkorn](https://avatars.discourse-cdn.com/v4/letter/e/e95f7d/32.png) [@enkorn](https://community.ecumaster.com/u/enkorn)\
**Post date:** [July 26, 2025, 3:29pm UTC](https://community.ecumaster.com/t/troubles-with-v3-software/4052/7 "2025-07-26T15:29:50Z")

</div>

Hello, Yes, with this build I didn’t have any more errors with hot plugging, thanks!
