Overview

This is a debugging assistance tool for developing systems which use the TCP/IP. It supports the e² studio integrated development environment.

It is intended to reduce development effort of embedded systems incorporating the M3S-T4-Tiny software library for these communications protocols on RX family products which are suitable for TCP/IP.

  • The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view
  • The states of API errors occurring within the TCP/IP middleware can be checked: [TCP Communication Path Info. (QE)] view
  • Learn More

QE for TCP/IP

Latest Ver.: V1.0.1

Released: Jul 20, 2017

Operating Environment

Download the technical preview

Installing This Product >>

Downloads
Type Title Date
Software & Tools - Other
[technical preview version] QE for TCP/IP V1.0.1
Log in to Download ZIP 589 KB 日本語
1 item

Documentation
Type Title Date
Application Note
RX Family Embedded TCP/IP M3S-T4-Tiny Socket API Module Firmware Integration Technology Rev.1.32
PDF 836 KB 日本語
Related Files:
Manual - Development Tools
QE for TCP/IP V1.0.1 [technical preview version] Rev.1.00
PDF 93 KB 日本語
Tool News - Release
[Released on the Web] Solution Tool Kit QE: Dedicated Tools for Particular Applications QE TCP/IP: A Dedicated Tool for TCP/IP Development Technical Preview V1.0.0
PDF 100 KB 日本語
3 items

Additional Details

Functions

The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view

Since the state of a TCP connection between your system and another party in communications can be checked for each end-point, analyzing or breaking down problems in the form of communications not starting even when a connection has been made becomes easy.

The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view

The states of API errors occurring within the TCP/IP middleware can be checked: [TCP Communication Path Info. (QE)] view

When a problem in communications originates in TCP/IP, this product helps you to resolve it by quickly getting the answers to questions "Did the problem arise in the TCP/IP middleware?" and "When the problem arises, what kind of error is involved?"

Using QE for TCP/IP under the e² studio eases the debugging of TCP/IP systems, shortening development periods and lowering costs.

Supported Library

Device Middleware Version
RX Family Ultracompact TCP/IP protocol stack [high-speed version] : M3S-T4-Tiny V2.02, V2.03, V2.05