Export
The Export command tells the Frontline software application to invoke the Frame Display. It then automatically selects the Export menu option.
A file name must be specified using the File= parameter specification. If just a file name without a path is specified, the saved file will be written to the default directory which is: \\documents and settings\all users\documents\frontline test equipment\my log files.
Export;File=export1.csv
The file extension must be .csv or a failure notification response is sent:
Export;FAILED;Timestamp=8/23/2012 2:29:38 PM;Reason=Invalid file extension : export1.txt
An optional file path may be specified.
Export;File= C:\Users\JSmith\Documents\export1.csv
The path must be valid or a failure notification response is sent:
Export;FAILED;Timestamp=8/23/2012 2:40:37 PM;Reason=Failed to create file ( may be Read-only ): c:\users\jsmith\documents\export1.csv
By default the Export command will wait until all frames have been compiled before beginning to export the data. However in the scenario where the Export command is sent while frames are still being captured this behavior can be modified using the Mode= parameter specification. The format for using the Mode= parameter is as follows:
Mode=< 0,1>
Where
0 : indicates the default behavior which is to wait for the frame compiler to complete.
1 : indicates to export the frames that are currently in the Frame Display ( i.e. do not wait for the frame compiler to complete ).
Example of using the Mode parameter:
Export;File= C:\Users\JSmith\Documents\export1.csv;Mode=0
The Mode parameter must be valid or a failure notification response is sent:
Command:
Export;File= C:\Users\JSmith\Documents\export1.csv;Mode=2
Response:
Export;FAILED;Timestamp=8/23/2012 2:40:37 PM;Reason=Invalid Mode parameter: Mode=2
Note: Note that if the default behavior of waiting for the frame compiler to complete is desired, then it is not necessary to specify the “Mode=0” parameter. However it is important to understand that if the Mode parameter is not specified and the sniffer is still running and capturing new frames, then the Export command may wait indefinitely.
The tab currently selected on the Frame Display is what gets exported. A specified tab can be selected using the optional Tab= parameter specification. The format for using the Tab= parameter is as follows:
Tab= < Technology >:< Layer Name >
Where < Technology > is one of the following:
| Value | Technolgy |
|---|---|
| "General” | // Ethernet |
| "Classic" | // Classic Baseband |
| "LE" | // LE BaseBand |
| "80211" | // 802.11 Radio |
| "USB" | // USB |
| "SD" | // SDIO/SPI |
Where < Layer Name > is one of the following:
Note: Note: in general the Layer Name matches what you see on the Tab in the Frame Display.
| 802.2 | 802.11 AMP | 802.11 AMP |
| 802.11 MAC | 802.11 Radio | 802.15.4 MAC |
| 802.1D | 802.1X | A2DP |
| AB CSP | AB DF1 Full Duplex/Radio Modem (BCC) | AB DF1 Full Duplex/Radio Modem (CRC) |
| AB DF1 Half Duplex (BCC) | AB DF1 Half Duplex (CRC) | AB PCCC |
| AMP Manager"SDP | ARP | ATT |
| AVCTP | AVDTP | AVDTP Media |
| AVDTP Recover | AVDTP Report | AVDTP Signaling |
| AVRCP | BACnet APDU | BACnet MSTP Frame |
| BACnet Network Layer | BACnet NPDU | BACnet PTP Frame |
| BACnet/IP | Baseband | BCCMD |
| BlueCore Serial Protocol | Bluetooth FHS | Bluetooth PRP |
| Bluetooth USB | Bluetooth Virtual Transport | BNEP |
| BSAP Link Layer | BSAP Network Control | BSAP Transport |
| BT-HID | CAN 2.0A | CAN 2.0A/2.0B |
| CAPI | Chipcard Bulk Messages | CIP |
| CL-DceRpc | CMTP | CO-DceRpc |
| Context Missing | ControlNet MAC | DeviceNet |
| DeviceNet Explicit | DH+ (Async) | DH+ (U2DHP) |
| DH-485 | DLR | DNP3 Application |
| DNP3 Transport | DNP3-Eth Link Layer | DNP3-Eth Raw Link Layer |
| DNP3-Serial Link Layer | Encapsulated AsyncPPP | Ethernet |
| Extended Inquiry Response | FAX | Frame Info |
| FTP | H4DS | Hands-Free |
| HCI | HCI UART | HCRP Contro |
| HCRP Data | Headset | HID Keyboard |
| HID Mouse | ICMP | IEC-60870-101 Application |
| IEC-60870-101 Link | IEC-60870-102 Application | IEC-60870-102 Link |
| IEC-60870-103 Application | IEC-60870-103 Link | IEC-60870-104 Application |
| IEEE P11073 20601 | IGMP | IPv4 |
| IPv6 | ISO-DEP | L2CAP |
| LE ADV | LE BB | LE DATA |
| LE LL | LE PKT | LLC 802.2 |
| LLDP | LMP | LPacket |
| Mass Storage Bulk Only Transport | MCAP Control | Modbus |
| Modbus ASCII 2 Wire | Modbus ASCII Master | Modbus ASCII Slave |
| Modbus RTU 2 Wire | Modbus RTU Half Duplex | Modbus RTU Master |
| Modbus RTU Slave | Modbus/TCP | NFC |
| NFC-A | NFC-B | NFC-DEP |
| NFC-F | OBEX | Obsolete S-Bus Presentation |
| OPP | PN-CBA | PN-IO-ContextMgr |
| PN-IO-DCP | PN-IO-MRRT | PN-IO-PTCP |
| PN-IO-RTAcyclic | PNIO-RT-CBA | PN-IO-RTCyclic |
| PN-MRP | PPP | PreConnection |
| PROFINET | PTP/MTP | PTS |
| RA USBCIP | RFCOMM | ROC Master |
| ROC Plus Master | ROC Plus over Ethernet | ROC Plus Slave |
| ROC Slave | RTCP | RTP |
| S-Bus Data Mode | S-Bus Data Mode (Secure Mode base) | S-Bus Presentation |
| S-Bus RS-232 Parity Mode | S-Bus RS-485 Parity Mode | S-Bus Secure Data Mode |
| SCO/eSCO | SCSI Primary Commands | SDIO/SPI |
| SDIO/SPI/HCI | SIM ACCESS | SIM Application |
| SMP | SNAP | Tag Type 1 |
| Tag Type 2 | Tag Type 3 | Tag Type 4A |
| Tag Type 4B | TCP | TCS |
| Three-Wire UART | UDP | USB |
| USB Data and Handshake Messages | USB Pre Messages | USB Setup |
| USB Split Message | USB Token Message | UWB Radio |
| VCP | VDP | Virtual Sniffer |
| VJC | VJU | WiMedia |
| Wireless USB | WUSB | ZigBee APS |
| ZigBee Cluster Library | ZigBee Device Profile | ZigBee Network |
As an example, if you wanted to export the “802.11 MAC” layer from your capture file generated by the ComProbe 802.11 sniffer you would format your Export command as follows:
Export;File=export1.csv;Tab=80211:802.11 MAC
OR as another example, export the SCO/eSCO layer captured by the BPA500
Export;File=export1.csv;Tab=Classic:SCO/eSCO
Note: If your capture file does not contain the specified layer name OR you make an error in entering the layer name then the export command will export the currently selected layer. In other words there will not be an error notification for this case.
There are several important ideas to remember about Export.
- Be aware that this can cause the Frontline software to spend considerable time generating the file.
- The Frame Display window will close once the export is complete.