[Elthox]

PM sent

 

[temerecs]

[ЦИТАТА="Шоншеридан, сообщение: 13496401 am , участник: 142175"]
Устройство, вероятно, заблокировано кодом VO. Вам нужно исправить VO Code Lock. ПМ отправил.
[/ЦИТИРОВАТЬ]

Unit is likely VO Code Locked. You need VO Code Lock fix. PM sent.
[/ЦИТИРОВАТЬ]

Good afternoon, could you help with a patch for VO unlock.
Thank you very much!

 

[temerecs]

[ЦИТАТА="masa52, сообщение: 13496421, участник: 270705"]
применил патч и все работает отлично спасибо
[/ЦИТИРОВАТЬ]

maybe you can help me.

 

[veresbmw]

I need VO Lock fix for my nbt evo.Can you send me for PM.
Thanks a lot

 

[code_breaker]

I too need to VO lock fix by nbt evo, if someone could pm me I would sincerely appreciate it.

 

[dengjie021160]

I replied to your same PM.

 

[shawnsheridan]

I too need to VO lock fix by nbt evo, if someone could pm me I would sincerely appreciate it.

PM sent.

 

[BVB1976]

hello, I need help with unlocking VO NBT EVO. Thank you very much!

 

[shawnsheridan]

hello, I need help with unlocking VO NBT EVO. Thank you very much!

View attachment 1062868

PM sent.

 

[shmalik]

Unit is likely VO Code Locked. You need VO Code Lock fix. PM sent.

I have same problem, can you please pm me the solution? Thanks

 

[shawnsheridan]

I have same problem, can you please pm me the solution? Thanks

PM sent.

 

[SWFLf10]

I may have the same issue... NBT EVO retrofit and when I go edit FDL it says runtime error...

 

[shawnsheridan]

I may have the same issue... NBT EVO retrofit and when I go edit FDL it says runtime error...

What happens when you VO Code NBT2?

 

[SWFLf10]

I might not be following correctly... I screwed up and hit "code" on the HU_NBT2 module while coding another module. I have a NBT EVO retrofitted, and the original coding was done before it was shipped to me. I realized immediately that I screwed up and tried to follow instructions online to get it working again. But it just shows "No Signal" now on my screen.

When attempting to edit the FDL and see the parameters, it shows a runtime error and then the module shows blue/red.

 

[shawnsheridan]

I might not be following correctly... I screwed up and hit "code" on the HU_NBT2 module while coding another module. I have a NBT EVO retrofitted, and the original coding was done before it was shipped to me. I realized immediately that I screwed up and tried to follow instructions online to get it working again. But it just shows "No Signal" now on my screen.

When attempting to edit the FDL and see the parameters, it shows a runtime error and then the module shows blue/red.

Error is a soon as you hit edit FDL or after when you FDL Code the ECU? What Launcher Application are you using with E-Sys?

 

[SWFLf10]

As soon as I hit edit FDL. PRO V2.8.1.155

 

[SWFLf10]

 

[shawnsheridan]

As soon as I hit edit FDL. PRO V2.8.1.155

Clearly an issue with your Launcher. And LauncherPRO 2.8.1 was released in Aug 2017 and declared End of Life by developer in Dec 2017, and likely does not have NBT2 properly mapped anyway.

 

[SWFLf10]

That's probably just a affecting that module? Everything else has been working without issue. Where can I find an updated version?

 

[shawnsheridan]

That's probably just a affecting that module? Everything else has been working without issue. Where can I find an updated version?

Can be, PM sent.