F.A.Q.
Frequently asked questions

Before buying any of our products in the store, you must register using a valid email address and username (not already in use). After registering, you will receive an email with the password initially assigned to your Logykal web account (you could modify your password later if you wish).

So, your access data is: the account email, the password, and the username (also known as nickname).

To modify your user data you must log in the Logykal website, using your access data.

Once logged in, look for the My account option in the upper menu bar into the Logykal store. Clicking on it, you will access your account desktop, and there you can access all account related options.

To modify your user data, click on the button Account details, and you will enter a page to update or change your personal data, your email address, the password and your avatar.

You can also enter by that page without accessing the user desktop, just clicking directly in the My account / Edit account option in the upper menu bar.

Our products are designed to be used in Personal Computers (x86 32/64bit) with Windows (7 / 8 / 8.1 / 10) operating system.

Currently we don’t have Unix-Linux or MAC compatible products.

Being owner of one of our products you have the right to resell it to any other person or company, by terms of a private contract, as long as the terms of the transaction do not contravene the terms and conditions accepted during your buy at Logykal store. Obviously you will be responsible to comply with tax obligations derived from the resell.

The only case you are not allowed to resell your Logykal product is with a software application. In our software products, the terms and conditions establish that the license acquired is for personal use and it is non-transferable.

Anyway, the product resell does not imply the transmission of the provided guarantee against faults. In that case you will be solely responsible of giving the proper guarantee to your customer for the resold product.

Each of the Motion Box Pro version is suitable to control a given number of linear actuators. Depending on the number of actuators: two (2DOF), three (3DOF), four (4DOF) or six (Hexapod), we can model more or less movements in our system. From basic movements (longitudinal accelerations and rolls), to more complex ones (vertical accelerations and twists).

Each of the Motion Box Pro version is suitable to control a given number of linear actuators. Depending on the number of actuators: two (2DOF), three (3DOF), four (4DOF) or six (Hexapod), we can model more or less movements in our system. From basic movements (longitudinal accelerations and rolls), to more complex ones (vertical accelerations and twists).

A later upgrade is not available for Motion Box Pro, because the enclosed power supply is designed to provide enough current for the calculated number of actuators it will feed.

If you are planning to upgrade your motion system in the near future, we suggest you to select the Motion Box Pro version suitable to the maximum number of actuators you are thinking ahead. Thus, your system will never turn out to have been too small. Price difference isn’t too big, and you will be grateful for having had enough foresight.

Yes; our Motion Box Pro can be supplied on demand adapted to work with a 110-125V AC 50/60Hz supply. To buy this special kind of Motion Box Pro, it’s necessary to select the “custom” option in the product page.

The working voltage and frequency is preset on factory. Once built, this value could not be changed anymore. This is a very important detail, because systems bought in EU to work with 220-230V AC can’t be used in countries where mains are 110-125V AC and vice versa.

After Lince detects your movement system, run the utility “Logykal.MotionTest.exe” which is placed in the Lince v2.0 installation folder, in order to start a motion system demo.

If you only have one serial (COM) port, you should select the system belonging to the type: [Legacy]. But if you have two or more serial ports, just select the corresponding type.

If you only have one serial (COM) port, each actuator ID should be different (typical values are 0 and 1). If you have more than one serial (COM) port, the typical actuator ID is 0.

The serial number usually is included in a label attached to the actuator itself.

Another way to guess the number is by opening the file “LinceInfo.log”, after Lince v2.0 has detected your motion system, with the help of a text editor. The file is placed in the Lince installation folder, and contains multiple information within which, you can find the serial number and IDs of your actuators.

When you buy a Lince copy, you will receive an email with a download link to the software installer.

Please, click on the link provided to download the software. Your email client could show you a security warning telling that you are about to download an executable from Internet; this is ok, and it is just to prevent you from downloading unwanted files without your knowledge, which it is not the case.

Once the file has been downloaded, the installer will be in the selected location during download process, or in your computer download folder (the default download folder configured in the mail client) if you weren’t asked for location for the file download.

If you don’t want to wait for the download email, or once it has been received you have difficulties to download the file through the link included (maybe your mail client doesn’t allow the download of executable files, or any other reason), you can alternatively download the installer from your client account in the Logykal website; just follow this procedure:

1. Login in the Logykal store using your account data (the same used during software buy).
2. In the upper menu bar, click on the My account / Downloads item.
3. If this account has one or more software licenses, you will see in this page the corresponding download links, showing also the remaining number of downloads allowed and the expiration date (limit date to download the files). Just click over the links and the file will be downloaded to your computer.

Once the installer has been downloaded, just execute the file and follow the steps shown.

Notice: If account control is activated under Windows, you could receive a security warning when Lince is being installed. That is ok. Software in our servers has been verified and is malware free. Logykal does not take responsibility for any illegal copy of our software not downloaded legally from our servers using the described procedure.

When you buy a Lince copy, you will receive an email with all the necessary data to start up Lince: your personal license key and the account email address associated to the license (which is the same that figures in the account access data). Also in this email you will receive a download link.In the F.A.Q. you will find instructions to download and install Lince software.

In the above image you can see an example of the email you will receive, highlighting the relevant information to start up and activate Lince. The activation should be done for a single computer, because the computer hardware become associated to the license during activation procedure.

The steps to be followed, once Lince has been installed, are:

• Double click over software icon; a splash window will open and the license activation is verified. The first run license won’t be activated and the activation screen will be shown (see below).

  

• The next step will be entering our license email address (1), indicated in the email received.
• Next, we must enter our account password (2) in the corresponding input box. We should use the password associated to our client account email (the same used to access our account data in the Logykal store website).
• After that, we must enter the license key (3), regarding uppercase, lowercase and slashes as they appeared in the email received. Maybe it should be easier for you to select all the license key text end copy to the clipboard from the email client, and then paste it into the corresponding field of Lince activation screen (copy and paste option will vary depending on the email client used, but the shortcuts “Ctrl+C” to copy and “Ctrl+V” to paste usually works in Windows).
• Finally we will click over the button ACCESS. After a few seconds, during which software access to our servers to validate the license, a window will show to tell us that the software has been activated using one of the activations and inform us the number of activations remaining.
  Note: An Internet connection is necessary for Lince to become activated.

Once completed the described procedure, we could see on Lince main screen our username (nickname), the active license type, and a button labeled CLOSE SESSION. Additionally, the Display tab, the Motion System tab or both tabs become visible, according to the type of license acquired. We can have access to those tabs to configure our peripherals.

If we close the software clicking over the X shape icon in the upper right corner of the window, our session will remain open. This means that the next time we run the program, our user will be directly active. We recommend this way of closing the software for personal computers only in a secure environment (nobody can have access to our computer without our knowledge or authorization).

In unsecure settings or shared computers, we recommend that, before exiting Lince software, click the button CLOSE SESSION. This way the next time Lince is executed, we will be asked again to enter our access data: email, password and license key. Doing it again in the same machine (the one the license is active for), does not consume one of the activations remaining.

3Motion System example

• Navigate to Cockpit / Connection Configuration window.
  

• Here you can find:

1. Set system type. In this example we are going to setup a 3Motion type. Select 3Motion and set actuators models to Dyadic Hyperaxis [100mm].
2. Lince will detect automatically your serial actuators numbers and show them in the box Actuators Information (Number 2).
3. Just click over a serial number in Actuators information and then click over the Actuator box (Number 3). It’s a easy way to copy and paste the serial number. Id = 0 (if your actuators has another Id, set here) and Port = None.
4. You can do a quick test selecting the actuator by the grey button near the actuator info box and changing the number of the slider in the Test section (number 4).

If everything is detected and configured, the system will start up the actuators and set a central position. Please, press accept button.

• Now your system is ready to configure a profile for any game.

1. Information about your system (serial number, type, etc)
2. You can configure your actuator setting and the game effects.
3. Once you modify any profile, push diskette button to save the profile.

Recommendations

Actuators configuration:

• Start with low values (just to ensure the system is working properly). The parameter means the % of the maximum value applied to the actuator.
• G’s maximum is the value of G generated by the car that you are driving (Renault generate 1G, F1 generates 4G, so select a approximated value, 2 or 2.5 is a good starting value)

Effects configuration:

• The software represents the acceleration in any axes. So your simulation experience depends of these values. If any effect is inverted, please, set a opposite signal (for example, 80 -> -80)
• Smooth is a good value to change… Experiment with this! ?
• Vertical G’s represents all the vertical motion.

If you have any questions or query please open a ticket and we will help you.

Enjoy your races ?

Depending on the simulator used, the steps to follow will be different. If you have one of the following simulators, it’s not necessary to do anything, as the system will be automatically detected:

iRacing
Asseto Corsa
Falcon 4 BMS
IL2 Cliffs of Dover

However, some simulators need the installation of a plugin or a file with a special setup to be able to work with external software; in that case, depending on the simulator, follow these steps:

• Automobilista
  Copy file “LogykalAutomobilista.dll” from Lince plugins folder ({Lince_dir}\Plugins\Automobilista\) to the Automobilista plugins folder ({Automobilista_dir\Plugins\).
• Automobilista 2
  Use this settings in the game.
  Shared memory – Project Cars 1
  UDP Frec. – 9
  UDP protocol – Project Cars 2
• Codemaster F1 Series
  F1 2018
  Find file “hardware_settings_config.xml, which is in the folder “C:\Users\{User_Name}\Documents\My Games\{Game_Name}\, and modify it so that it has the following content:

  <udp enabled="true" broadcast="false" ip="127.0.0.1" port="21001" sendRate="60" format="legacy" />

  Inside the simulator keep the telemetry settings in this configuration:

  

  F1 2019
  Find file “hardware_settings_config.xml, which is in the folder “C:\Users\{User_Name}\Documents\My Games\{Game_Name}\, and modify it so that it has the following content:

  <udp enabled="true" broadcast="false" ip="127.0.0.1" port="21001" sendRate="60" format="legacy" yourTelemetry="restricted" &lt;span style="color: #ff0000;"&gt;extradata="2">

  Inside the simulator keep the telemetry settings in this configuration:

  
  
  F1 2023
  Within the game, access “Options > Settings > Telemetry Settings” and configure the following values:

  

  EA SPORTS WRC 2023
  1. Run the game and close it
  2. Copy the Cosmos.json file from the Cosmos plugins folder (C:/Logykal/Plugins\WRC\) to Documents\My Games\WRC\telemetry\udp
  3. Copy the Config.json file from the Cosmos plugins folder (C:/Logykal/Plugins\WRC\) to Documents\My Games\WRC\telemetry\
  If you need a more specific configuration replace step 3 with edit the file Documents\My Games\WRC\telemetry\config.json and add the following inside packets:

• {
  "structure": "cosmos",
  "packet": "session_update",
  "ip": "127.0.0.1",
  "port": 20779,
  "frequencyHz": -1,
  "bEnabled": true
  },
  {
  "structure": "cosmos",
  "packet": "session_pause",
  "ip": "127.0.0.1",
  "port": 20779,
  "frequencyHz": 0,
  "bEnabled": true
  },
  {
  "structure": "cosmos",
  "packet": "session_end",
  "ip": "127.0.0.1",
  "port": 20779,
  "frequencyHz": 0,
  "bEnabled": true
  }
  

• LeMans Ultimate
  Le Mans Ultimate (32bits)
  1. Copy file “LogykalRFactor2.dll” from Lince/Cosmos plugins folder ({Lince/Cosmos_dir}\Plugins\Rfactor2\32bits\) to the Le Mans Ultimate plugins folder ({LeMansUltimate_dir}\Plugins\).
  2. Modify the file CustomPluginVariables.JSON ({LeMansUltimate_dir}\UserData\player) to enable the plugin.
  Add this to the body:

  "LogykalRFactor2.dll":{
  " Enabled":1
  }

  The content of the file should look like this:

  {
  "LogykalRFactor2.dll":{
  "Enabled":1
  },
  "TrackIR_LMU_Plugin.dll":{
  "Enabled":1
  }}

  Le Mans Ultimate (64bits)
  1. Copy file “LogykalRFactor2.dll” from Lince/Cosmos plugins folder ({Lince/Cosmos_dir}\Plugins\Rfactor2\64bits\) to the Le Mans Ultimate plugins folder ({LeMansUltimate_dir\Plugins\).
  2. Modify the file CustomPluginVariables.JSON ({LeMansUltimate_dir}\UserData\player) to enable the plugin.
  Add this to the body:

  "LogykalRFactor2.dll":
  { "Enabled":1 }

  The content of the file should look like this:

  {
  "LogykalRFactor2.dll":{
  "Enabled":1
  },
  "TrackIR_LMU_Plugin.dll":{
  "Enabled":1
  }}

• Codemaster Grid Series
  Find file “hardware_settings_config.xml, which is in the folder “C:\Users\{User_Name}\Documents\My Games\{Game_Name}\, and modify it so that it has the following content:

  <motion enabled="true" ip="127.0.0.1" port="21002" delay="1" extradata="2"/>

• Codemaster Dirt
  Find file “hardware_settings_config.xml, which is in the folder “C:\Users\{User_Name}\Documents\My Games\{Game_Name}\, and modify it so that it has the following content:

  <motion enabled="true" ip="127.0.0.1" port="21000" delay="1" extradata="2"/>

• Codemaster Dirt Rally 1 & 2
  Find file “hardware_settings_config.xml (or “hardware_settings_config_VR.xml if you use VR), which is in the folder “C:\Users\{User_Name}\Documents\My Games\{Game_Name}\, and modify it so that it has the following content:

  <udp enabled="true" extradata="2" ip="127.0.0.1" port="21000" delay="1"/>

• DCS WORLD
  Copy the file export.lua from the folder \plugins\ of Lince 2.0 to the folder $HOME\Users\$YourUserName\Saved Games\DCS\Scripts of DCS WORLD.
• Euro Truck Simulator 2/American Truck Simulador (32bits)
  Copy file “Lince2ETSAS.dll” from Lince plugins folder ({Lince_dir}\Plugins\ETS2_AMS\32bits\) to the ETS2 or AMS plugins folder ({Steam_dir}\steamapps\common\American Truck Simulator\bin\win_x86\plugins\).
• Euro Truck Simulator 2/American Truck Simulador (64bits)
  Copy file “Lince2ETSAS.dll” from Lince plugins folder ({Lince_dir}\Plugins\ETS2_AMS\64bits\) to the ETS2 or AMS plugins folder ({Steam_dir}\steamapps\common\American Truck Simulator\bin\win_x64\plugins\).
• FSX & Prepar 3D
  Unzip archive “FSUIPC4.zip” contained in the Lince plugins folder ({Lince_dir}\Plugins\Prepar3D\) and install the software.
• Game Stock Cars
  Copy file “LogykalGSC.dll” from Lince plugins folder ({Lince_dir}\Plugins\GSC\) to the Game Stock Cars plugins folder ({GSC_dir\Plugins\).
• Live for Speed
  Find file “cfg.txt”, which is in the folder where we have installed the software, and modify it so that the lines inside it look like the following:
  OutSim Mode 1
  OutSim Delay 1
  OutSim IP 127.0.0.1
  OutSim Port 23000
  OutGauge Mode 1
  OutGauge Delay 1
  OutGauge IP 127.0.0.1
  OutGauge Port 23001
• pCars
  Enter the simulator and go to the configuration section: “Options > Visuals > Hardware”, changing the parameter “Use shared memory” to “Yes”.
• pCars 2
  Enter the simulator and go to the configuration section: Menu/Options/system and changing the parameter:
  Shared memory = Yes
  Udp Frequency = Off
  UDP Protocol Version = Project CARS 1
• pCars3
  Enter the simulator and go to the configuration section, Menu/Config/System: , changing the parameter:
  Shared memory = Project Cars 2
  UDP Mode = 9
  UDP Protocol version = Project Cars 2
• rFactor 1
  Copy file “LogykalRFactor1.dll” from Lince plugins folder ({Lince_dir}\Plugins\Rfactor\) to the rFactor 1 plugins folder ({rFactor_dir\Plugins\).
• rFactor 2 (32bits)
  Copy file “LogykalRFactor2.dll” from Lince plugins folder ({Lince_dir}\Plugins\Rfactor2\32bits\) to the rFactor 2 plugins folder ({rFactor2_dir\Plugins\).
• rFactor 2 (64bits)
  Copy file “LogykalRFactor2.dll” from Lince plugins folder ({Lince_dir}\Plugins\Rfactor2\64bits\) to the rFactor 2 plugins folder ({rFactor2_dir\Plugins\).
• Richard Burns Rally
  Copy file “LogykalRBR.dll” from Lince plugins folder ({Lince_dir}\Plugins\RBR\) to the Richard Burns Rally plugins folder ({RBR_dir\Plugins\).
• The Crew
  Create file “hardware_settings_config.xml” inside the directory “C:\Users\{User Name}\Documents\My Games\{Game Name}\” with the following content:

  <ExtraConfig phys_out_sim="127.0.0.1:22000" phys_out_sim_rate="3" phys_out_nitro_lean="0.5"/>

• Xplane (32bits)
  Copy file “win.xpl” from Lince plugins folder ({Lince_dir}\Plugins\Xplane\32bits\) to the Xplane plugins folder ({Xplane_dir\Plugins\).
• Xplane (64bits)
  Copy file “win.xpl” from Lince plugins folder ({Lince_dir}\Plugins\Xplane\64bits\) to the Xplane plugins folder ({Xplane_dir\Plugins\).

Lince supports a wide range of simulation software:

DRIVING

• [iRacing] iRacing
• [Kunos simulazione] Assetto Corsa | Assetto Corsa Competizione
• [WMD] pCars | pCars2
• [ISI] RFactor 1 | RFactor 2
• [Reiza Studios] Game Stock Car | Automobilista
• [SimBin] GTR | GTR2 | GT Legends | Race | Race07 + Expansion Pack | RaceRoom
• [Codemasters] F1 Series | Dirt Series | GRID Series 
• [Ubisoft] The Crew 
• [Piboso] Kart Racing Pro 
• [LFS] Life for Speed 
• [SCSI] Richards Burns Rally 
• [SCS Software] EuroTruck Simulator 2 | American Truck Simulator

FLIGHT

• [Laminar Research] XPlane series
• [Microsoft] Flight Simulator 2020 & FSX
• [Lockhedd Martin] Prepar 3D
• [Disgital Combat Simulator] DCS World
• [Benchmark Sims | Billion Soft | Microprose] Falcon 4 BMS
• [1C Company] IL2 Cliff of Dover

* Our software is under continuous development; if your simulation software is not in the above list, keep visiting our support forums to check if it will be supported in the next Lince release.

No.

Although Lince has been created to make the most out of Logykal peripherals, it is also compatible with a wide range of peripherals available in the market. You can check the list of supported peripherals in the product page.

When you buy a Lince copy, you will receive a non-transferable license for personal use. The first time you install the software, you must activate it before use (an Internet connection is required).

After that, if you want to change your computer, you can install Lince again, but likewise before you must activate the software in the new equipment before using it, thus using another one of the activations available. You can repeat that as long as you have activations remaining, but note that Lince can only be activated in one machine at the same time. Activating the software in a computer imply the deactivation in the previous equipment.

Lince access data, as well as your avatar (the small picture associated to your user), are the same used in Logykal website. Any changes should be done in the website itself.

Access the website with your favorite browser, and you could modify the access data and the avatar easily; there are detailed instructions on how to do that above this question in the FAQ.

If you have a Lince compatible display, our software will detect it automatically; you don’t have to do anything. In the upper right area of Lince display configuration page you will see the detected display type and its hardware settings: vendor ID (VID) and product ID (PID).

If your display is in the list of compatible displays, but Lince doesn’t show it as detected, it would be due to several causes. Before contacting our technical support service (soporte@logykal.com), please do the following tests:

• Ensure your display is detected by Windows operating system (go to Start, Configuration, Devices).
• Check that you are not executing any other alternative software to control your display.
• If you are the owner of a XtremeRacers display, check that the VID/PID values are the right ones.
• Visit our support discussions to check if someone else has had the same problem with his/her display. You may find a workaround for that particular problem.

If your display is still not being detected in Lince after having checked the above, we will be pleased to help you to solve your problem through the support forums (preferred method) or sending us a message to the email address shown above.

n the Lince display configuration page you can see, for each of the visualization presets (from 1 to 12), a list with all the possible values to be shown in that area of your display.

Nevertheless, the selected value will show in the display only when the used simulation software exports this value to the attached devices. You can see the simulator selected looking at the upper left area of the display configuration page, in section number 1: Select a Simulator.

To obtain further information about the exported (available) variables of your simulation software, you must turn to its support page.

Origins display is supplied in an enclosure ready to be attached to a steering wheel by means of two holes in the upper side ends. To fix it you should use two M3 screws of the required length.

On the back side of the enclosure is the mini-USB connector to supply current and communicate with the display and control circuit, and for that reason you should foresee the path of the cable through your steering wheel to the display.

In the product page you can see a diagram with the enclosure dimensions, so you can take measurements for the cable crossing and the mounting holes.

The analog axis controller board allows the installation of a small motor to simulate ABS system. The vibration motor should be a DC current type motor.

Vibration motors are usually small in size and power, and thus, it could be connected directly to the axis controller board without a separate power source. In this case, the motor will be fed by the USB bus power itself, through the USB connector of the controller board. In order to do that, the connected DC motor must fulfill the following specifications:

• Rated voltage: 5V DC
• Current, continuous use: 0.25 A max.
• Current, non-repetitive use (t < 100 us): 0.4 A max.
• USB bus power output: 0.5 A (don’t use non-powered USB hubs)

Warning: the connection of a motor that doesn’t fit the above specifications might cause irreversible damage to the axis controller board and the computer connected to it.

In case you want to use a motor with higher specifications than the above, a separate power source would be necessary to feed the motor. The axis controller board have a power supply connector for that particular use. The motor used must comply with the following specifications:

• Rated voltage: 4.5 – 24V DC max.
• Current, continuous use: 1 A max.
• Current, non-repetitive use (t < 100 us): 2 A max.

In no way whatsoever a motor with rated voltage or rated currents higher than the above can be used. It will be responsibility of the final user to ensure that the DC motor used is suitable.

Warning: DC motors current increases when the shaft find rotation resistance (during starting, for instance). So, the motor current might reach unacceptable levels if the shaft get stalled. Please, verify in the motor datasheet that the starting current and the stall current are lower than the continuous current that the axis controller board can supply.

Redirection of telemetry data to another UDP port

1. Locate the C:\Logykal\config folder
2. Edit the EquipmentData.cnf file
3. Locate the paragraph “PassThroughUdpPort”:29993
4. Assign the UDP port to which the telemetry data should be redirected (for example, port 20001) and modify it with that number, it should look like this: “PassThroughUdpPort”:20001

When Cosmos starts up, it will read the telemetry assigned to its UDP port in the corresponding simulator configuration and forward it to port 20001.