Introduction
AMMC - Amb MyLaps Multidecoder Converter is a command utility to converts multiple decoders binary protocol data into JSON open format. It connects to decoder and waits for data to come. Once received binary packet, this is converted to JSON. Based on command line parameters the JSON is logged, stored to a database or sent to WebSocket. Your timing can read this in real-time from WebSocket or do a query in database.
binary name | AMB/TranX3/ RC4/DR5 | MyLaps X2 | ProChip Smart | RaceResult | Vostok |
---|---|---|---|---|---|
ammc-amb.exe | 👍 | ||||
ammc-x2.exe | 👍 | ||||
ammc-prochip.exe | 👍 | ||||
ammc-rr.exe | 👍 | ||||
ammc-vostok.exe | 👍 |
For more detail usage see Supported decoder
JSON produced by AMMC is the simplest possible JSON with Passings data. Common fields between decoders are names the same and only filled in with specific decoder's data. Example:
{"msg":"PASSING","passing_number":1,"transponder":232323,
"rtc_time":"2022-10-11T22:57:36.099241435+02:00",
"strength":0.0,"resend":false,"tran_code":"ID:232323","loop_id":"55"}
- each passing has a passign number unique to the decoders session
- there is
transponder
ortrans_code
based decoder type - there is always RTC time or UTC time depending on decoders architecture
- additional features like strength, resend or loop id appears based on decoder's setup and abilities
AMMC conversion's utility can be also embedded into your app using a native API for JavaScript, Java, C++, Python or any other programming language with FFI interface. For more details with examples see the API description
Supported platforms
AMMC is fully supported on Windows and Linux 64 bit only. Some decoders are supported on Apple OSX as well.
Platform/OS | AMB | MyLaps X2 | ProChip Smart | RaceResult | Vostok | Simulator |
---|---|---|---|---|---|---|
Windows 64bit | yes | Intel/Amd only | yes | yes | yes | yes |
Linux 64bit | yes | Intel/Amd only | yes | yes | yes | yes |
OSX M1 | yes | no | yes | yes | yes | yes |
Raspberry Pi 4+ | yes | no | yes | yes | yes | yes |
OSX/Intel, Raspberry Pi, Windows 32, Linux 32 are platform supported on request only. If you need other platform, please contact us by email.
For Android support see our AMMC Demo timing app (source code Github) using AMMC lib for timing compatible with AMB and Vostok decoders. Contact us for your timing app support on Android or other platform support
Setting up as Windows Service (start on boot)
AMMC can be setup to start with Windows boot. It can be setup as Windows service using nssm
utility.
The nssm
utility can be downloaded from https://nssm.cc/download Extract downloaded nssm-xxx.zip file
and run following based on your Windows version (32 or 64bit):
nssm.exe install ammc
A gui of nssm
utility opens. Setup following values (see screenshots in "screens" directory):
Application
->Path
- link to ammc-xx executable fileApplication
->Startup directory
- link to directory where is AMMC extractedApplication
->Arguments
- fill in parameters required like decoder IP address, license, DB url etcDetails
->Display name
- name the new service - something likeAMMC
etc
Other fields might be configured as necessary
Press edit service
to save and create new Windows service. The new service can be started by
`nssm.exe start ammc` (running as superuser might be necessary)
Once started windows will restart the service if failed and start it with Windows boot.
Use nssm.exe start ammc
o nssm.exe stop ammc
to restart ammc service; or Windows service manager UI to do the same.