Pc Lap Counter searching tru all com ports for dongle

Hi

I is any way that you can force Pc Lap Counter to only use one com port?

The reason for my question is, because I have this problem, that I can see, that the Pc Lap Counter are searching through all the com ports on my pc for the dongle.

And there is no issue with the dongle, because I can use it without any problem with Chrono and RCS02.

Thanks in advance!

Here can you see the error.

Hello,

You can force the com port to use : click on the stop button , change the com port and then click on the start button.
Also, at least one controller must be powered ON, otherwise Pc Lap Counter will not be able to connect to the dongle.

Regards.

Guy

Hi Guy

I tried this yesterday at our racing club. Using the procedure that you advised. But it did not solve the problem.

Actually we also discovered that under the search for com port pc lap counter did not count laps, and when the seaching was on the com port where the dongle was placed the race stopped for around 5 seconds, and then pc lap counter added the laps, but the laps time was really wrong.

And we are not the only club here in Denmark, that have this issue.

So is there any way that you can hardcode the com port for the dongle and avoid this searching for a dongle?

Thanks in advance!

Hi,

Something i don't understand : if the connection with the dongle failed then Pc Lap Counter start searching , therefore i don't see how hardcode the com port can solve the connection problem, even i hardcode the com port i assume the connection problem will still occurr.
I think sometime the dongle not answer to the "init" command and i need to check why , maybe PCLC not send the init command correctly...
By the way , at the end Pc Lap Counter 5.48 found your dongle V4 (and the led in PCLC become green) or not ?

Regards.

Guy

Hi

I have made this video, so you can see the problem. But to answer your question.

at the end Pc Lap Counter 5.48 found your dongle V4 (and the led in PCLC become green) or not ?
No, it is still yellow as you can see from the video.


https://youtu.be/rR3ZSA2yzHo

Ok now I see the problem, when pclc try the com3 he receive a signal from the dongle but it 's like pclc didn't recognize the data coming from the dongle and then try another com.
Can you click on the "debug" button and check what pclc display in the debug window.

Hi Guy

I have used the same procedure generating this debug output as in the video.

Here i the screenshot of the debug collection.
https://servimg.com/view/20546056/4

Here do you have the debug information from the text files.
DebugO2_20240205T174735_IN.TXT
17:46:58:599643
17:47:08:006508
17:47:08:188399
17:47:08:487925
17:47:08:788742
17:47:21:415444
17:47:21:684956
17:47:22:000023
17:47:31:652967
17:47:31:895158
17:47:32:192456

DebugO2_20240205T174735_OUT.TXT
17:47:06:915369 06 06 06 06 00 00 00 00 3B B7
17:47:07:975336 61 00 00 00 00 00 00 00 3C 21
17:47:08:538948 43 FF 14 00 00 82 FF 00 3C 59
17:47:08:592809 43 FF 14 00 00 85 FF 00 3C 5E
17:47:20:309480 06 06 06 06 00 00 00 00 40 F5
17:47:21:372618 61 00 00 00 00 00 00 00 41 5C
17:47:22:028308 43 FF 14 00 00 82 FF 00 41 A0
17:47:22:055676 43 FF 14 00 00 85 FF 00 41 A3
17:47:30:526246 06 06 06 06 00 00 00 00 44 F0
17:47:31:607067 61 00 00 00 00 00 00 00 45 5B
17:47:32:238813 43 FF 14 00 00 82 FF 00 45 9C
17:47:32:266726 43 FF 14 00 00 85 FF 00 45 A0

DebugO2_20240205T174602_IN.TXT
17:45:28:289145
17:45:28:579072
17:45:37:922922
17:45:38:170813
17:45:38:480072
17:45:48:102726
17:45:48:393720
17:45:48:703790
17:45:58:328336
17:45:58:602224
17:45:58:908869

DebugO2_20240205T174602_OUT.TXT
17:45:36:865158 06 06 06 06 00 00 00 00 18 8D
17:45:37:901354 61 00 00 00 00 00 00 00 18 F5
17:45:38:490999 43 FF 14 00 00 82 FF 00 19 31
17:45:38:503474 43 FF 14 00 00 85 FF 00 19 31
17:45:47:024572 06 06 06 06 00 00 00 00 1C 84
17:45:48:079344 61 00 00 00 00 00 00 00 1C EC
17:45:48:743889 43 FF 14 00 00 82 FF 00 1D 2F
17:45:48:768592 43 FF 14 00 00 85 FF 00 1D 33
17:45:57:217601 06 06 06 06 00 00 00 00 20 7C
17:45:58:304789 61 00 00 00 00 00 00 00 20 E9
17:45:58:941932 43 FF 14 00 00 82 FF 00 21 2B
17:45:58:975546 43 FF 14 00 00 85 FF 00 21 2E

Really strange, here is what you should see when all is ok:



In your case when Pc Lap Counter send the init command your dongle response with NULL value and that's not normal.

What is the version of your O2 components ? (dongle, controller and car)
Also, did you use blue dongle or yellow dongle updated to v4 ?

Guy

Hi Guy

Thanks for your feedback, it has big value for me and also for the members in our club here in Denmark.

Here do you have the answers to your good questions.

What is the version of your O2 components ? (dongle, controller and car)

Also, did you use blue dongle or yellow dongle updated to v4 ?

• It is the blue dongle
  

Dongle have version

• 4.10
  

SCP3 controller

• 4.10a for the handle
  

• 4.10a for the PA (Power modul)
  

Car

• C chip (newest version) with firmware version 4.10
  

Windows version where the Pc Lap Counter is running on

• Windows 11 home edtion
  

As an extra information I can tell you that I have been testing with Chrono for Oxigen ver. 4. (I am fully aware of, that I do not know, if you can compare with this RMS to yours RMC). I was using the same dongle, laptop, SCP3 controller and car, and I was able to run 3 test races (2 x 10 minutes) and one with 20 laps without any problems with the communications from the Dongle to the Chrono software.

Thanks for your help and support.

ok thank you for the information, the only difference i see is the version of the controller : i have SCP3 4.10 and not 4.10a and i don't have the power modul but i hope it does not make a big difference.
I made a little modification in Pc Lap Counter to use the init command 0Fh FFh (in place of 61h), who knows...maybe it will solve your problem.
You can download the new version with the little modification here Pc Lap Counter version 5.48b.
After the installation you should see "version 4.0.1b" in the O2 interface of PCLC like here:



Guy

Hi Guy

Many thanks. I will test this new version in this weekend.

How will you recommend the new version shall be installed? Shall I remove the old version, and do a clean install, or shall just do an upgrade of the current version of Pc Lap Counter.

Anders Trier

Simply install the new version over the existing, data and setting will not be overwrited.

Hi Guy

Will do.

Anders Trier

Hi Guy

Many thanks for your updated version. But you fix did not fix the issue. Pc Lap Counter are still not detecting the dongle. It is same issue as before the update version.



I was using the same procedure as last time that I was testing and with same controller, same firmware etc.

Hi Anders,

I running out of idea , we should plan a teamviewer session so i will be able to check what happen on the com port (via the tools "com port toolkit 3.9").
When did you have sometime for a teamviewer session ?

Guy

Hi

What about tomorrow at around 10:00 am og early evening tomorrow?

Thanks for the offer.

Tomorrow after 21h will be fine, ok ?

Hi Guy

Perfect for me. Tomorrow after 21th. Ok.

Thanks for your help and support.

Anders

Hi Anders,

I have made version 5.48c,  this version  fix a potential bug in the debug feature of the O2 interface.
It will not solve the problem but at least i hope it will display more information in the debug window.
Can you install version 5.48c and send me a screenshot of the debug window.
You can download the new version with the little modification here Pc Lap Counter version 5.48c.
After the installation you should see "version 4.0.1c" in the O2 interface of PCLC

Guy

Hi Guy

I will try to download and test this evening.

Hi Guy

Here do you have the request screenshots. I have been following the same procedure with this test as I did, when we had our session.

I have also sent you the debug output text file to you over e-mail.

Thank you, so unfortunately nothing more in the debug window.
I know Chrono2 and rcso2 is working good on your computer but they don't use the same component to read the com port,
so maybe something on your computer disturb Pc Lap counter...
Can you try on another computer ? just install version 5.
48c on it, you don't need to activate that Pc Lap Counter because we just want to know if it will recognize the dongle and if it will display more data in the debug window.

Hi Guy

I will try to install Pc Lap Counter on my work laptop later today, and update you with the result.

Hi Guy

I have now tried the same operation with the Pc Lap Counter version with the extra debug feature installed on my work laptop. And the good thing is that there was no issue with the communication to the dongle as you can see from below screenshoots.

The only differrence on my working laptop and the current windows laptop is, that my working laptop are using windows 10, and my private laptop is on windows 11.

Otherwise there is no difference. In my racing club where we have the same issue with pc lap counter the computer, that are been used are also windows 11.

Can you see from the log that there is any difference, or when you are testing on your computer with laptop are you also only using windows 10 or windows 11?

I have sent you the logs through e-mail.