Can't access the Pulsenics Network Setup page? (Hotspot unavailable or setup page not loading but static IP is set on ethernet)

The Pulsenics Networking Setup page may fail to load when trying to configure or recover Probe network access. This can happen when:

• The Probe Wi-Fi hotspot (Pulsenics Wifi Setup_PUXXX) is not appearing or not connecting
• Entering the Probe IP address in the browser does not bring up the setup page
• You are trying to change network settings (e.g. switch between DHCP and static IP) but cannot reach the configuration page
• The hotspot path worked before but is no longer available after a network change

If the Probe has a known static IP, the setup page can often be accessed directly through that IP without the hotspot.

Note: This recovery path requires knowing the Probe's static IP. If the static IP is not known, skip to the escalation section below.

Agent triage — ask these first

Ask these before troubleshooting:

1. "Do you know the static IP address currently set on the Probe?"

   • If unsure: Ask — "Was a specific IP address written down or documented when the Probe was first set up on your network?"
   • If not known: Skip this recovery path and escalate to Pulsenics — see escalation section below.

2. "Is your computer connected to the same network as the Probe, or are you trying to reach it over a different network?"

   • If unsure: Ask — "Is your laptop plugged into the same router or switch that the Probe is connected to, or are you on Wi-Fi on a different network?"
   • If still unsure: Proceed with the direct connection method below — it works regardless of network configuration.

3. "How are you trying to access the setup page — through the Probe hotspot, by entering an IP address in the browser, or another way?"

   • If unsure: Ask — "Are you connecting your laptop to a Wi-Fi network called Pulsenics Wifi Setup_PUXXX, or are you typing an address directly into your browser?"

Use the answers to route:

Recovery path — accessing the setup page via static IP

If the static IP is known and the computer is not on the same subnet as the Probe:

1. Connect your computer directly to the Probe's LAN port using an Ethernet cable
2. Assign your computer a manual IP address in the same subnet as the Probe, but with a different last number
   • Example: if the Probe is set to 10.145.61.57, assign your computer something like 10.145.61.50
   • Use the same subnet mask (e.g. 255.255.255.0)
   • Leave the gateway field blank
3. Ping the Probe IP to confirm the Probe is reachable before opening the browser
4. Enter the Probe static IP directly in the browser address bar
   • The Pulsenics Networking Setup page should load

Confirm after: If the page loads, proceed with the required network configuration before closing the session.

After accessing the setup page — Ethernet recovery

Once the Networking Setup page is accessible, the standard recovery path is:

1. Go to Ethernet Setup and enable dynamic IP (DHCP)
   • Note: enabling DHCP will disconnect the current session from the static IP used to reach the page — this is expected
2. Connect the Probe to the InHand IR302 router (black and green square router with antennas) LAN port via Ethernet
3. Confirm that the Probe network LED becomes solid blue — this indicates a successful network connection

Confirm after: Once the network LED is solid blue, check the Dashboard at dashboard.pulsenics.com to confirm the Probe comes back online with a green indicator.

Before escalating — collect this information

If the recovery path does not work, gather the following before contacting Pulsenics:

• Whether the Probe static IP is known and what it is
• Whether the Probe responds to ping on that IP
• Whether the computer was successfully placed on the same subnet
• Whether the Networking Setup page loaded at any point
• Whether the Probe network LED became solid blue after reconfiguration
• What has already been tried and what effect it had
• Whether a Windows computer with internet access is available for a remote session

Remote diagnostic path

If the Ethernet recovery path does not restore access, Pulsenics can assist remotely. Requirements for a remote session:

• A Windows computer with internet access
• Google Remote Desktop ready for the session
• Python 3.8 or newer installed
• Ability to install the paramiko package

Contact Pulsenics to arrange a remote diagnostic session.

Prevention

• Keep a record of the Probe static IP whenever static addressing is used
• Document whether the Probe is currently on DHCP or static IP at all times
• Use the direct static-IP access path when hotspot access is unavailable
• Keep the Ethernet recovery path available for setup and connectivity recovery

Escalate if

Flag for Pulsenics review if:

• The Probe static IP is not known
• The page still does not load after placing the computer on the same subnet
• The Probe does not respond to ping on the expected IP
• The network LED does not become solid blue after reconfiguration and Ethernet connection to the router
• The page access or network recovery path remains unsuccessful after following the documented method

What recovery looks like

• The Networking Setup page loads in the browser
• The required network configuration can be completed
• Where applicable, the Probe is switched from static IP back to dynamic IP (DHCP)
• The Probe network LED becomes solid blue
• The Probe appears online in the Dashboard with a green indicator

Article status

This is a living troubleshooting note for the symptom Pulsenics Networking Setup page not loading. Additional causes, checks, and confirmed resolutions may be added as more cases are identified.

Tags: Probe networking, Networking Setup page, static IP, DHCP, Ethernet recovery, hotspot unavailable, hotspot not showing, setup page not loading, can't access setup page, IP address, network configuration, InHand router, IR302