dbnetsoft
IDCamPro
Knowledge BaseIDCamProRemoteRedirectRaceResultExchangeScreensProPhotofinish.NET
IDCamPro
Knowledge BaseIDCamProRemoteRedirectRaceResultExchangeScreensProPhotofinish.NET
  • General
    • Installation
    • User Interface Overview
      • Live View
      • Details View
      • Navigation View
    • Pre-Event Checklist
    • Settings & Configs
  • Configuration
    • Timing
      • ALGE-Timing Devices
      • RACE RESULT Devices
    • Cameras
      • Camera Recommendations
      • Reolink
    • Transponder Mappings
    • RACE RESULT 12
      • Exporter
  • Competitions
    • Markers & Recordings
    • Matching between images and markers
    • Synchronisation
    • Navigation
      • Search box
      • Keyboard
  • Release Notes
Powered by GitBook
On this page
  1. Configuration
  2. Timing

RACE RESULT Devices

PreviousALGE-Timing DevicesNextCameras

Last updated 4 months ago

The following devices are supported:

  • System 5000 directly via local network (port 3601)

  • Ubidium directly via local network

  • Exporter setup on local webserver in RR12

Configuration

Active

As there can be many remote devices and/or loops connected to a decoder or RR12 event file, differentiation is based on channel and loop IDs.

Key
Values
Example

Start/Impulse Channels

M<channelId>-<loopId>

M3-1 for loop 1 on channel 3

Recording Channels

<channelId>-<loopId>

2-1 for loop 1 on channel 2

Bib Channels

<channelId>-<loopId>

5-1 for loop 1 on channel 5

Ubidium does not transmit channel and loop information, so here a trigger is only M without channel and loop id.

Passive

Key
Values
Default

Start Channels

M

M

Recording Channels

M, F

M F for recording on both a trigger and a passing

Bib Channels

F

F

Mstands for manual input on the active extension by either a lightbeam or a push button.

Rising/falling edge cannot be used.