TachoSync Company Card Authenticator: Difference between revisions
No edit summary |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 26: | Line 26: | ||
==How to Install CCA== | ==How to Install CCA== | ||
===Download | ===Download it from TachoSync UI=== | ||
[[File:CCA.png|right]] | [[File:CCA.png|right]] | ||
# Go to '''[https://tacho.teltonika.lt TachoSync]'''. | # Go to '''[https://tacho.teltonika.lt TachoSync]'''. | ||
| Line 33: | Line 33: | ||
# Open the downloaded file and install CCA. | # Open the downloaded file and install CCA. | ||
# Run CCA. | # Run CCA. | ||
Now you can connect card reader with a company card that will be used for remote authentication. | |||
For more information on how to add company cards, please refer to [[TachoSync_Interface#Adding_a_Company_Card|Adding a company card]]. | For more information on how to add company cards, please refer to [[TachoSync_Interface#Adding_a_Company_Card|Adding a company card]]. | ||
=== | ===Version update via CCA=== | ||
# | # Another option is to update it directly from CCA's monitor view. Once a new version is available, a banner appears at the top of the CCA window. The banner contains the version number, release date and "Update" button. If the banner is dismissed, it does not re-appear until a new version is released. | ||
# Click "Update" - the download starts, progress is shown. | # Click "Update" - the download starts, progress is shown. | ||
# When download is completed, click "Install and restart". | # When download is completed, click "Install and restart". | ||
| Line 45: | Line 45: | ||
==Latest CCA version== | ==Latest CCA version== | ||
{| class="wikitable" | {| class="wikitable" | ||
!Version!!Release Date! | !Version!!Release Date!!Release Notes | ||
!Release Notes | |||
|- | |- | ||
|'''2. | |'''2.1.0''' [[File:Download_zip.png|100px|link=Special:Redirect/file/Company_Card_Authenticator_v2.1.0.zip]]||'''2026-01-14''' | ||
|<ul style="margin:1;"> | |||
* Fixed an issue where company cards were not identified reliably when using Lisle Hyper Card racks. | |||
* Fixed a rare display issue where the same company card could appear duplicated in the monitor view when using standard smart card readers (PC/SC). | |||
</ul> | |||
|- | |||
|} | |||
{| class="mw-collapsible mw-collapsed wikitable" | |||
|+ style="white-space: nowrap" | Older versions | |||
|- | |||
!Version!!Release Date!!Release Notes | |||
|- | |||
|2.0.0||2025-12-18 | |||
|<ul style="margin:1;"> | |<ul style="margin:1;"> | ||
* Added version information to the CCA monitor, showing the installed version, release date, package size, and whether an update is available. | * Added version information to the CCA monitor, showing the installed version, release date, package size, and whether an update is available. | ||
| Line 59: | Line 71: | ||
</ul> | </ul> | ||
|- | |- | ||
|1.2.1||2025-09-15 | |1.2.1||2025-09-15 | ||
|<ul style="margin:1;"> | |<ul style="margin:1;"> | ||
* Fixed a rare issue where some smart card readers (PC/SC) did not retrieve ATR command correctly. | * Fixed a rare issue where some smart card readers (PC/SC) did not retrieve ATR command correctly. | ||
| Line 65: | Line 77: | ||
</ul> | </ul> | ||
|- | |- | ||
|1.2.0||2025-09-11 | |1.2.0||2025-09-11 | ||
|<ul style="margin:1;"> | |<ul style="margin:1;"> | ||
* Improved authentication speed when using Lisle Hyper Card racks – authentication is now 3–4 times faster compared to the previous version. | * Improved authentication speed when using Lisle Hyper Card racks – authentication is now 3–4 times faster compared to the previous version. | ||
| Line 72: | Line 84: | ||
</ul> | </ul> | ||
|- | |- | ||
|1.1.0||2025-07-04 | |1.1.0||2025-07-04 | ||
|<ul style="margin:1;"> | |<ul style="margin:1;"> | ||
* Disabled internal logging to internal.log, keeping only the main application logs. This prevents uncontrolled file growth and simplifies troubleshooting. | * Disabled internal logging to internal.log, keeping only the main application logs. This prevents uncontrolled file growth and simplifies troubleshooting. | ||
| Line 80: | Line 92: | ||
</ul> | </ul> | ||
|- | |- | ||
|1.0.0||2025-04-25 | |1.0.0||2025-04-25 | ||
|<ul style="margin:1;"> | |<ul style="margin:1;"> | ||
* Reduced memory usage to improve performance and stability. | * Reduced memory usage to improve performance and stability. | ||
| Line 92: | Line 104: | ||
[[File:Company Card Authenticator interface window.png|link=Special:Redirect/file/Company Card Authenticator interface window.png|frame|200px|alt=Company Card Authenticator interface|Company Card Authenticator interface]] | [[File:Company Card Authenticator interface window.png|link=Special:Redirect/file/Company Card Authenticator interface window.png|frame|200px|alt=Company Card Authenticator interface|Company Card Authenticator interface]] | ||
The CCA provides the name of the connected | The CCA provides the name of the connected reader(s) and the following information in a table: | ||
* Card slot - identifier of card slot in the reader. | * Card slot - identifier of card slot in the reader. | ||
* Card ID - a unique identifier assigned by the smart card chip - '''copy this ID to TachoSync when adding a new company card - see [[TachoSync Interface#Companies|“Companies”]] for more information'''. | * Card ID - a unique identifier assigned by the smart card chip - '''copy this ID to TachoSync when adding a new company card - see [[TachoSync Interface#Companies|“Companies”]] for more information'''. | ||
| Line 106: | Line 118: | ||
==CCA Hosting Models== | ==CCA Hosting Models== | ||
''' | '''A. Centralized Card Management (Provider-hosted CCA) | ||
*The service provider | *The service provider hosts the company cards of the end-clients. | ||
*These cards are stored in card hotels / hyper-racks (hardware racks that can host many cards at once). | *These cards are stored in card hotels / hyper-racks (hardware racks that can host many cards at once). | ||
*The CCA software runs on the provider’s infrastructure, making all stored cards available to | *The CCA software runs on the service provider’s infrastructure, making all stored cards available to TachoSync. | ||
'''Key highlights: | '''Key highlights: | ||
| Line 116: | Line 128: | ||
*Works best for providers serving many small transport companies that do not want local IT hassle. | *Works best for providers serving many small transport companies that do not want local IT hassle. | ||
''' | '''B. Local Deployment (End-client hosts CCA) | ||
*The end-client (transport company) keeps the company card on-site, usually in a single-slot USB smart card reader connected to a PC. | *The end-client (transport company) keeps the company card on-site, usually in a single-slot USB smart card reader connected to a PC. | ||
*The CCA application is installed on that PC. | *The CCA application is installed on that PC. | ||
| Line 194: | Line 206: | ||
|[[File:Hyper-card-rack-120-img5.png|thumb|left|x300px|DIP switches, lower right (© Lisle, 2025)]] | |[[File:Hyper-card-rack-120-img5.png|thumb|left|x300px|DIP switches, lower right (© Lisle, 2025)]] | ||
|[[File:Hyper-card-rack-120-img4.png|thumb|left|x300px|Multiple racks connected (© Lisle, 2025)]] | |[[File:Hyper-card-rack-120-img4.png|thumb|left|x300px|Multiple racks connected (© Lisle, 2025)]] | ||
|} | |||
===<u>Troubleshooting</u>=== | |||
{| class="mw-collapsible mw-collapsed" | |||
!Cards become unresponsive after inactivity | |||
|- | |||
| | |||
'''<u>Symptoms</u>''' | |||
* CCA shows as ''connected''. | |||
* Company cards become unresponsive or show communication errors after a period of inactivity. | |||
* Restarting the '''CCA Windows service''' restores functionality temporarily. | |||
'''<u>Cause</u>''' | |||
* Windows '''USB selective suspend''' may put idle USB ports into a low power state. | |||
* USB smart card readers do not always recover correctly when the port resumes. | |||
* As a result, CCA loses communication with the reader. | |||
'''<u>Workarounds</u>''' <br> | |||
'''<big>Option A</big> — Disable USB selective suspend (recommended)''' | |||
* Control Panel → Hardware and Sound → Power Options | |||
* Change plan settings → Change advanced power settings | |||
* USB settings → USB selective suspend setting → '''Disabled'''. | |||
* Apply for Plugged in (and On battery, if applicable). | |||
'''<big>Option B</big> — Disable USB power management per device''' | |||
* Open '''Device Manager'''. | |||
* Expand '''Universal Serial Bus controllers'''. | |||
* For each '''USB Root Hub''': | |||
** Right click → Properties → Power Management. | |||
** Uncheck '''Allow''' the computer to turn off this device to save power. | |||
'''Notes:'''<br> | |||
* This is a '''Windows power management behavior''', not a CCA defect. | |||
* The issue is more likely to occur on non‑dedicated PCs with active power‑saving settings. | |||
* For dedicated CCA hosts, '''Option A''' is usually the simplest solution. | |||
''For more information'':<br> | |||
[https://learn.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-selective-suspend Microsoft documentation]|[https://www.pugetsystems.com/support/guides/how-to-disable-usb-selective-suspend-1190/ Puget Systems guide]|[https://www.ninjaone.com/blog/configure-usb-selective-suspend/ NinjaOne guide] | |||
|} | |} | ||