martinpankratov
Hi

I used the Pi Software for the first time this weekend and managed to figure out how everything works except the qualyfing mode. I followed the steps provided in the QM Mode pdf file (http://www.cosworth.com/media/457717/toolset_-_qualifying_mode_setup.pdf). I filled all the information in as it shows on the guide and wanted to use the Auto Learn feature. I then used the write to device button once the car had started and was ready to go out. The display is Omega Intelligent Colour Display (ICD). 

The problem was that the QM Mode reference lap(fastest lap) did not show up at all on the display after multiple laps and therefore the (Qualifying mode cumulative segment time diff) did not work etiher.

Is it true that you need to be in QM Mode to have the fastest lap of the session displayed on the ICD? I only managed to get the current and the previous lap displayed. All the QM Mode laps failed to work.

The circuit beacon worked absolutely fine.

Any help would be greatly appreciated.

Thanks

Quote 0 0
Rob_Jarvis
Hi Martin,

A couple of things to check. Your Toolset setup was set as QM Mode enabled in the Qualifying node? Providing this is enabled the ICD normally has Auto Learn selected by default.

What settings did you use when you at ironed the write to device and where you logging the QM channels in your data to analyse and understand why you didn't get what you expected?

Many thanks,

Rob

Cosworth Support
Cosworth Electronics 

Quote 0 0
martinpankratov
Hi Rob,

We believe that the problem is in the firmware of the display or the data logger. The same settings worked on another display that I tested. 
Trying to find firmware for the display to download now.

Any links would be appreciated.

Many thanks,
Martin 
Quote 0 0
Rob_Jarvis
Hi Martin,

Interesting...I am not aware of any firmware issues that means the QM mode doesn't work but then again I work mainly with our ECU products so my colleagues might know more. 

In terms of firmware versions we need to know what ones are in your displays to begin with as we have several different versions.

In Toolset this should be shown on the bottom right corner of the devices tab, if you can send us a screenshot of these from the working and non working ICDs then we can send you over the firmware version.

Many thanks,

Rob.

Cosworth Support
Cosworth Electronics 

Quote 0 0
martinpankratov
Hi Rob,

Sorry for the late response. Both ICD Plus displays are running  display.png  and toolsetversion.png   is the Pi Toolset software version I have used. The Pi Toolbox itself is version 7.3



After enabling Enabling the QM in the set up using the Pi Toolset software. I sent the setup to the display. I then reset the lap counter in the actions tab. And clicked on the 'Write to device'. After that a box appeared that the 'The device has been successfully updated or smth'. The qualifying mode is set to the Auto Learn - Distance based mode. The inputs are following: *Both of the channels are fully working (checked using Pi Toolbox.&nbsp[wink]toolset QM.png 

After that the display was shut off and the car was fired up a few minutes later to go out qualifying. The quali session lasted for 20 minutes and in total the driver did 13 flying laps. (e.g. crossed the beacon, I set using Google Earth, 13 times).

None of the QM Channels worked that I inserted to the display. The QM Reference lap stayed at 0.00.000 and same with the QM Cumulative Segment Difference. 

After inserting all the QM channels into the Pi Toolbox software graph, only the QM Status shows something. All the other QM Channels are just zeros.

Graph showing QM Status during the qualifying session. *Neither did the reference lap overlay work, which should show the fastest lap or the last lap and the bar in green and red, depending on the last laps difference to the reference lap. The overlay only shows the last lap.
QMStatus.png 

I haven't figured out what the numbers mean, but I can see that the QM Status changes during the session and the gets stuck in the fourth phase. Which according to this image should be the lap the QM Mode starts working and showing the referene lap and the Delta time etc. But it is not working for us for some reason. 

Does the QM have anything to do with the Beacon sensor or do the QM Channels get their information from GPS? Remember, both inputs work fine.

Please let me know, if someone knows if I have missed out on something or if there really is a serious problem somewhere in the Display unit.

Quote 0 0
Duramotor
When using GPS as beacon then the following is working for me.

Under "NMEA 0183 Decode" Select GGA and RMC.
NMEA.png

NMEA.png
Quote 0 0
Gummi
QM uses Distance as an input, so if no distance channel is available it will not work. What channel is creating the Distance in the setup (should be in Wheelspeeds)
Also, if you use a Bitfield control in Toolbox for the QM Status channel then the name/reference of the status is displayed directly. 
Quote 0 0
martinpankratov
Untitled.png 
These are the settings I have inserted under the wheelspeeds tab. I managed to get the qualifying mode working using "Distance Based - PDS File Reference". The QM using "Distance Based - Auto Learn" feature is not working at all. All the QM channels remain 0 then. 

But even with the PDS File Reference segments feature does not work. It does not update itself on track and only shows delta time every time the driver crosses the line I inserted manually using Google Earth. 

Any help would be appreciated.

I'd really like to get the Auto Learn feature working one day and find out where the fault was. 

Thank you


Quote 0 0
tran.k88
Hi Martin,

I had this issue previously and was able to resolve it.

A few things to check:

Log the generated channels (Distance and Speed). If these aren't logging, then you can at least trace back the issue to this channel. I had to re-define my channel. I believe I used ICD_Distance in the end.

Secondly,

When importing a pds reference lap, check that Pi actually is segmenting the lap properly into 128 segments. If you distance/speed channels are incorrectly defined, the PDS generation method won't work either.

If the imported lap works, each segment should have a time increment. This is on the option page just before you click 'Write to Device'. 



Log all the QM channels - I use the QM Cumulative Segmented Time Difference for our team's live dashboard.
Quote 0 0