Finally back to a real 60-2 Trigger Setup
#31
Rennlist Member
Thread Starter
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
Brian, the question I have about that setup is how you mounted the sensor? I have that wheel sitting on a shelf somewhere, I've been planning on machining my flywheel and putting in several more cap set screws to use the factory location, but that won't be either cheap or easy.
#32
Addict
Rennlist Member
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
Brian, the question I have about that setup is how you mounted the sensor? I have that wheel sitting on a shelf somewhere, I've been planning on machining my flywheel and putting in several more cap set screws to use the factory location, but that won't be either cheap or easy.
#33
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
We used the Clewitt one for a while before going to the new fly, but Richard definitely did get his from Patrick Motorsports as it's in a thread on Reutterwerks.
#34
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
#35
Rennlist Member
Thread Starter
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
This.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
#36
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
This.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
#37
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
This.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
I run the stock sensor for speed and a cam sync sensor with my fully sequential Vi-PEC (same software as Link G4) set up from Pauertuning and never had a trigger issue. With the cal file that Vic supplied the engine started right away after installation although it was a non-stock 3l engine.
I find curious there aren't more folks around who seem to be able to use the stock sensors.
#38
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
I can't say if the cam sensor helps with any possible trigger error but just that the engine always sparks crystal-clear up beyond 7k rpm, with no trigger errors on both sensors reported in the real time value window. I always see the green light.
#39
Three Wheelin'
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
I have used stock speed+ref sensors as crank sensors and cam sync as 3rd sensor, worked well with VEMS. With 132 teeth there would be issues trying to run just speed sensor and just cam sensor because cam is a bit sloppy and ECU has to calculate timing from cam sensor -> not recommended at all.
Cam sync should be used just as it is, cam sync. It means that it just shows ECU when to reset firing order ( can occur between any cylinder TDC, has 180 degree window on 4cyl engine).
Cam sync should be used just as it is, cam sync. It means that it just shows ECU when to reset firing order ( can occur between any cylinder TDC, has 180 degree window on 4cyl engine).
#41
Addict
Rennlist Member
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
The issue with using the 132 tooth ring gear in a sequential setup is that the teeth are very close together and the cam sync signal must occur in the "valley" between the teeth. If the sync falls on either the fallin or rising edge of the crank signal, there will be errrors.
60-2 wheels are a standard option and they are easy to set up. There is nothing wrong with using the factory reluctor sensor and 132 tooth ring gear for a crank signal. The only issue for aftermarket ECU users is that adjustment to the arming threshold needs to be set properly to ensure stable signal.
60-2 wheels are a standard option and they are easy to set up. There is nothing wrong with using the factory reluctor sensor and 132 tooth ring gear for a crank signal. The only issue for aftermarket ECU users is that adjustment to the arming threshold needs to be set properly to ensure stable signal.
#42
Three Wheelin'
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
As I explained earlier, factory trigger works perfectly if it is used as intended, meaning to interpret two crank sensors as missing tooth wheel by ECU and use separate 3rd sensor on the cam for cam sync. BTDT, never had a problem.
But I would never take timing from cam unless it is some normally aspirated car and budget is really tight or something..
But I would never take timing from cam unless it is some normally aspirated car and budget is really tight or something..
#43
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
As I explained earlier, factory trigger works perfectly if it is used as intended, meaning to interpret two crank sensors as missing tooth wheel by ECU and use separate 3rd sensor on the cam for cam sync. BTDT, never had a problem.
But I would never take timing from cam unless it is some normally aspirated car and budget is really tight or something..
But I would never take timing from cam unless it is some normally aspirated car and budget is really tight or something..
#44
Three Wheelin'
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
I have tested many options during the development of the VEMS pnp system for 951 and while they work, I just chose to take advantage of the VEMS capability to accept three trigger inputs. Least amount of potential issues and always rock solid signals.
#45
Rennlist Member
![Default](https://rennlist.com/forums/images/icons/icon1.gif)
Given the shape of the teeth, the 132-tooth crank signal is always either rising or falling, so not sure what you mean? Do you mean errors occur if the trigger point for the cam signal coincides with the trigger point on the crank signal? If so, seems like that should be manageable with the right hardware/software (i.e., process the crank trigger first, and put the cam in a queue to be processed immediately after)?