Why we use DecoderScript

You are currently sitting in front of a Snifflog and you have to figure out what each byte means? An application layer protocol can be quite cumbersome to decode. But if you are using Frontline equipment like

  • Frontline SoderaTMLE Wideband Bluetooth®Protocol Analyzer
  • ComProbe® SoderaTM Wideband Bluetooth®Protocol Analyzer
  • ComProbe® NFC Protocol Analyzer
  • ComProbe® 802.11 a/b/g/n Protocol Analyzer
  • ComProbe® SD Protocol Analyzer : SD/SDIO/SPI/MMC
  • ComProbe High Speed UART (HSU) Protocol Analyzer
  • ComProbe BPA® 600 Dual Mode Bluetooth®Protocol Analyzer
  • NetDecoder™: Industrial Network Analyzer
  • NetDecoder™: Industrial Network Analyzer Protocol Analyzer for Serial, Fieldbus, SCADA and Ethernet Networks
  • NetDecoder™: Industrial Network Analyzer Protocol Analyzer for Serial, Fieldbus, SCADA and Ethernet Networks
  • Ethernet ComProbe®: Frontline’s portable, non-intrusive, aggregator Ethernet Tap
  • Serialtest® ComProbe: Serial Data Analyzer & Protocol Sniffer
  • Serialtest®: Asynchronous RS-232/422/485 Serial Protocol Analyzer

there is help. It’s called DecoderScript. With DecoderScript, you enable the ComProbe® Protocol Analysis System to decode your proprietary application layer protocol. With that you can go from:

Read by Type Response Read by Type Response *Database: e68be278(S) Length: 8 Attribute data Handle-Value pair Attribute Handle: 79 *Stored Attribute: Unknown UUID [0xb98f] Unknown Attribute Data: 0x 00 01 09 02 01 02

to

Read by Type Response
*Database: e68be278(S)
Length: 8
Attribute data
Handle-Value pair
Attribute Handle: 79
*Stored Attribute: Custom HID Information
CHID Information
Version: 0x0100
Country Code: 0x09
Flags: 0x02
Sub Class: 0x01
Protocol: 0x02

Call us at +4920194671387 to get your decoder and save an immense amount of time, by not having to analyse your snifflog by hand.

undecoded snifflog

undecoded snifflog

Decoded Snifflog

Decoded Snifflog

 

By | 2017-11-23T17:31:34+00:00 November 23rd, 2017|Uncategorized|