Yuku free message boards

Thanks for your reply.

The buttons on the 8600M Wheel were replaced by Stack with the newer style 1 year ago. Each of the 4 buttons works if pressed separately, so the buttons themselves are OK. The unit just doesn't respond to the continuous hold of the UP ARROW the way the manual claims for peak values, and it simply ignores the UP ARROW + DISPLAY LIGHT button combination instead of zeroing the lap counter. It is as if the manual is incorrect, and these functions are delegated to other key combinations in late build 8600 wheels with predictive lap. These functions have never worked with this new D module- it is not as if they worked at one time and stopped working later. I was hoping that the manual was in error - if not, then this new D module is not functioning properly and will have to be returned to Stack.

With regard to the E1 data issue, I dug out the Stack to ASCII conversion program and determined - to my dismay - that all the data from all 8 E1 module channels are non-varying junk values in all of the downloaded sessions. However, the data inputs connected into the D module (such as WSPD, LAT_G and all engine parameters, recorded fine with the correct sample rates. For the 8 E1 Module channels, the Recorder knew to create the proper channel name file for each, and also to set the proper sample rate for the channel, (so the Configuration File worked to that extent) but there was apparently no valid data supplied by the E1 module to the recorder.

It appears that DataPro felt I did not have the proper authorization/tag codes to use the E1 module and "Locked Out" the module. This seems likely to be associated with the "Channel Exceeded" error I got on the first download. The fact that I got, and continued to get, "all Green" indicators from the configuration upload (which specified 8 E1 channels) is a mystery. The system has always been configured with the same R and E1 modules, and the Tag and Authorization numbers were provided by Stack - they have always worked before.

The lithium battery in the Display Module - the one that is read out by the REAL TIME DISPLAY function - was replaced last year. If you can tell me the SYSTEM DIAGNOSTIC function to use to read out the batteries in the R and E1 modules I can get those values for you. In theory - and I need to test this - if I can see the 8 E1 channel values on the REAL TIME DISPLAY, the system should be able to record them - right?

Before I waste any of your time reviewing my files I am going to try some experiments with static tests now that the car is back in the garage. I will see if I can replicate the E1 channel exceeded error.

In the meanwhile, if you can confirm that indeed, the 8600M unit is supposed to work with the buttons as described in the -002 manual, and that therefore the fact that our unit does not work that way means that the problem is simply a broken D Module, that would be helpful. My understanding previously from Stack was that the wheel display is nothing but a simple repeater - all the program actions and display info is sent from the D module - so this problem would have to lie in the D module.

Regards,
-