Author Topic: Loss of prime trigger on FW 1.2.43  (Read 653 times)

Offline 299vr6-t

  • Jr. Member
  • **
  • Posts: 5
  • BHP: 0
Loss of prime trigger on FW 1.2.43
« on: June 13, 2021, 01:19:50 pm »
Hey guys
i have 2 VEMS fired cars , a VR6-T and a (S4 AAN)
Both are running Firmware 1.2.38 without trigger problems (sometimes noise on cam sensor on vr6-t)
Now i wont try Firmware 1.2.43 to use something like multispark but the is no chance to get the car running because of trigger error.
It happens on both cars.
What is wrong with triggering on 1.2.43 ?
I tried different settings , also without cam sync but both cars wont run with this firmware.

Is there any solution ?

Offline 299vr6-t

  • Jr. Member
  • **
  • Posts: 5
  • BHP: 0
Re: Loss of prime trigger on FW 1.2.43
« Reply #1 on: April 25, 2022, 12:38:55 pm »
Today tried FW 1.2.44
Same issue, "to many prim. trigger".

It´s not good that there is any support for those special things.

 :(

Offline jrussell

  • VEMS USA
  • Administrator
  • Full Member
  • *****
  • Posts: 212
  • BHP: 15
    • VEMS USA
Re: Loss of prime trigger on FW 1.2.43
« Reply #2 on: April 28, 2022, 02:22:29 pm »
So don't use those firmwares? They are not released anyway. 1.2.38 is recommended.

Read the notes on the versions since 1.2.38 here: http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges

They all say experimental, do not use yet.

1.2.43 had some specific trigger related changes for a Subaru EJ255 and hasn't been thoroughly tested or released yet. Not really a surprise it didn't run a VR6 or AAN.
VEMS USA - Located in beautiful Burlington, Vermont
1988 RX7 Turbo