Thank you so much! I figured the serial part wouldn't be to hard.Tres said:The serial is the easy part.
I have them somehwere...(I will see if I can find them)
USB is a pain and AMB won't give them out....
A USB Sniffer could be used.
that's true, but atm i've no decoder, and i'm interested only to know the protocol and the datagram sent to made up a linux timing systemhankster said:Best bet would be just to open up terminal and connect it to the serial post and view what is coming across the serial port.
I too am trying to find info on the tcp protocol used by the AMB decoder. I can read port 5403 and I am receiving data but it is not ascii - does anyone know how to read this data?the transmissiom= 9600 8N1
the string = AMB20 Output @010204382050 (Car1;hours2;min4;Sec38;20Mil Sec;50Hits)
If you have some schematics about AMB20 decoder and transmitter or equivalent please sen me
Wireshark is a good "sniffer" but it will not be able to decode the data.Try some of the other options in Wireshark for decodes.
It issues a "status" every 5 seconds - noise level, gps setting, temperature and a few more not-so-important itemsHi myosin, I'm trying to emulate the an AMB decoder to connect my lap counter system directly with all software supporting the AMB protocol.
Do you have any other information about the proctocol :
1. initialization data send by the decoder on port opening
2. Any other data send, not related to the Lap data.
My amb decoder send for example this :Wireshark is a good "sniffer" but it will not be able to decode the data.
Not to worry though... I already figured it out.
8E 02 33 00 0F 08 00 00 01 00 01 04 3D 00 00 00 03 04 1D 73 87 00 04 08 E8 7E 98 69 24 50 04 00 05 02 22 00 06 02 03 00 08 02 00 00 81 04 B0 14 02 00 8F
This stream is a "passing" (identified by bytes 9 and 10),
It is passing number 61
Transponder ID is: 8876xxx
RTC TIME in hex is: E8 7E 98 69
RTC DATE in hex is: 24 50 04 00
Plus a few other types of info.