Remote control over LAN is one of the most practical ways to integrate an IWATSU CS-3000 Series Semiconductor Curve Tracer into a modern lab workflow. Once the instrument and the PC are on the same network, the CS-810 remote control software can communicate with the curve tracer quickly and reliably, allowing convenient control from the desk rather than the bench.

This guide explains the basic setup logic, the difference between static IP and DHCP, and a simple troubleshooting method that works well in practice.

What you need

Before starting, make sure you have:

• an IWATSU CS-3000 Series curve tracer
• a PC with CS-810 installed
• an Ethernet cable
• a live LAN connection, either through a network switch or through a direct PC-to-instrument Ethernet connection
• access rights on the PC to view or change network adapter settings if needed

It is also helpful to have someone available with IT admin rights, especially in company environments where network adapters, firewall settings, or VLAN policies may be restricted.

Basic communication principle

For the CS-810 software to communicate with the curve tracer over LAN, both devices must be on the same IP subnet and the curve tracer must have a reachable IP address.

In practical terms, this means:

• the curve tracer must have a valid IP address
• the PC must have a compatible IP address
• both devices must be physically connected to the same network path
• the PC must be able to ping the instrument

If these conditions are met, the CS-810 software usually has a good chance of connecting successfully.

Check the curve tracer LAN settings

On the curve tracer, navigate to the LAN setup screen and note the following values:

• DHCP: ON or OFF
• IP address
• Subnet mask
• Default gateway
• MAC address

A typical manually configured example could look like this:

• DHCP: OFF
• IP address: 192.168.31.91
• Subnet mask: 255.255.254.0
• Default gateway: 10.131.16.1

The most important fields for local communication are the IP address and subnet mask.

Static IP vs. DHCP

Static IP (DHCP OFF)

With DHCP turned off, the instrument uses the manually entered IP settings.

Example:

• curve tracer IP: 192.168.31.91
• subnet mask: 255.255.254.0

This is often the preferred lab setup because the instrument keeps the same address every time. That makes it easy to store the address in CS-810 and reconnect later without rediscovering the instrument.

DHCP (DHCP ON)

With DHCP turned on, the curve tracer requests its IP settings automatically from a DHCP server on the network.

This can be convenient on managed office networks, but it has one disadvantage: the assigned IP address may change unless IT creates a DHCP reservation for the instrument’s MAC address. For many test setups, a fixed static IP is the cleaner solution.

Check the PC network configuration

On the Windows PC, open Command Prompt and run:

ipconfig

Look for the Ethernet adapter that is physically connected to the network used by the curve tracer.

For example, if the curve tracer is set to:

• IP: 192.168.31.91
• mask: 255.255.254.0

then the PC should be on a compatible address range, for example:

• IP: 192.168.30.171
• mask: 255.255.254.0

These two addresses are compatible because the subnet mask places both devices in the same subnet. If the PC instead has something unrelated such as 10.x.x.x or 192.168.1.x, the CS-810 software will usually not be able to reach the instrument.

Test the connection before opening CS-810

Before debugging the software, first confirm that the PC can reach the curve tracer at the network level.

In Command Prompt, run:

ping 192.168.31.91

If the connection is healthy, you should see replies such as:

Reply from 192.168.31.91: bytes=32 time<1ms TTL=32

This is a very important checkpoint. A successful ping confirms that:

• the cable or switch path is working
• the curve tracer is powered and active on the network
• the PC and instrument are on compatible IP settings
• the problem, if any remains, is likely no longer a basic LAN issue

If ping succeeds, the next step is simply to use that IP address in CS-810.

Connect with CS-810

Open the CS-810 remote control software and configure the target instrument connection using the curve tracer’s IP address.

Using the example above, the target IP would be:

192.168.31.91

If the software supports auto-discovery but fails to find the instrument, try entering the IP address manually. Manual IP entry is often the most reliable method.

Recommended simple setup for direct connection

If you are working in a lab and want the cleanest possible setup, use a direct or isolated LAN connection with fixed addresses.

A simple example:

Curve tracer
IP: 192.168.31.91
Subnet mask: 255.255.255.0
Gateway: blank

PC
IP: 192.168.31.92
Subnet mask: 255.255.255.0
Gateway: blank

This avoids unnecessary complexity from corporate gateways, DHCP leases, domain policies, or VLAN rules.

What if ping fails?

If ping does not work, the issue is almost always one of the following:

• Wrong subnet — the PC is not in the same subnet as the curve tracer
• Wrong adapter — the active IP address is assigned to Wi-Fi, VPN, or a virtual adapter instead of the correct Ethernet port
• Physical connection issue — bad cable, disconnected cable, disabled switch port, or no link on the Ethernet interface
• Instrument settings not applied — values may have been entered on the curve tracer but not confirmed or activated yet
• Firewall or network restrictions — managed company networks may introduce additional obstacles

If ping fails, start with:

ipconfig

Then confirm the PC adapter settings, cable path, and the instrument IP settings.

Why ping matters so much

A successful ping is the dividing line between two very different kinds of problems.

If ping fails: You have a basic network problem involving addressing, subnet, cable, adapter, switch, or unapplied settings.

If ping works: The basic network path is good. Remaining issues are more likely related to CS-810 connection settings, firewall permissions, or the wrong target IP entered in the software.

In other words, ping first, software second.

Notes about default gateway

For local PC-to-instrument communication, the default gateway is usually not critical as long as both devices are on the same subnet.

So if your curve tracer can be pinged successfully, but its gateway looks unusual, that alone may not be the cause of a communication problem. For direct lab connections, many users simply leave the gateway blank.

Practical troubleshooting checklist

1. Confirm the curve tracer IP address and subnet mask.
2. Run ipconfig on the PC.
3. Verify the correct Ethernet adapter is active.
4. Confirm the PC is on the same subnet.
5. Run ping <curve tracer IP>.
6. If ping succeeds, enter the same IP manually into CS-810.
7. If needed, allow CS-810 through Windows Firewall.
8. Temporarily disconnect VPN or disable unused network adapters during testing.
9. If the company LAN is complex, simplify the setup by using a direct connection or isolated switch.

Conclusion

Establishing a LAN connection between an IWATSU CS-3000 Series Semiconductor Curve Tracer and the CS-810 remote control software is usually straightforward once the network basics are understood.

The key points are simple:

• make sure the instrument has a valid IP address
• make sure the PC is on the same subnet
• verify the connection with ping
• then connect to that IP from CS-810

For many labs, a static IP setup is the most convenient and predictable solution. It avoids address changes, makes support easier, and simplifies day-to-day use of the remote control software.

Need help choosing or setting up an IWATSU curve tracer system? Contact PMK America for application support, installation guidance, and remote-control workflow assistance: sales@pmkamerica.com