Hey guys,

I'm having an issue with network access. I have my DT80 physically connected to a wireless client (Dlink DAP-1665 in wireless client mode) via the ethernet port. I have manually configured the DT80 with a static IP (and all the other required settings).

I am able to open the dEX Logger software through my browser if I do so within the first minute or two of "power on". I am also able to successfully ping it within that same time frame.

But, if I wait too long to connect, I get "This webpage is not available" from the browser. My ping responses will be either "Destination host unreachable" (only one time) and three "Request timed out", or four "Request timed out" responses.

Also, after I'm connected to the DT80, I lose the connection if I don't continue to "interact" with the DT80 for a two minute span of time (with either the browser or by pinging). I am able to revive the lost connection simply by disconnecting and reconnecting the ethernet cable leading to the wireless client.

I've done other testing, but nothing that points directly to either device as the problem. Any thoughts?

Hi normaleyes,

Disconnection happens as something close the link between DLink and dataTaker.
Could you explain the topology of your connection? What do you have in your network?
Please check security and DHCP setting on DLink.

Best regards,
Rudy Gunawan

Hi Rudy,

We currently have three dataTakers but only one DLink, since we are still working on Proof of Concept with the wireless client.

We have WPA security on our in-house wireless network (TestNet). With the DLink in Client mode, the wireless signal is passed directly to whatever device is attached. Our Network Admin has provided me with a block of static IP addresses on TestNet and I have configured each dataTaker with its own IP address.

I decided to expand my testing scenario due to the lack of results. I obtained a wired ethernet switch and connected the DLink, two of our dataTakers, and a computer (TestPC) to it. This provides me with a wireless connection to three wired devices. I also have my laptop wirelessly connected to TestNet.

Using the TestPC I am able to connect to both dataTakers without any issues (they are all communicating via ethernet cables through the switch). I am also able to ping my laptop from the TestPC and vice versa (via the wireless network). There has never been a wireless disconnect between the TestPC and laptop.

From my laptop I am able to wirelessly connect to both dataTakers within the 1-2 minute "window of opportunity". If I continue to actively ping both dataTakers, they will remain connected. If I wait more than 1-2 minutes to ping one of the dataTakers (but continue to ping the other), I lose the connection to the one but maintain the connection to the other.

To reestablish a lost connection, I can remove and reinsert the ethernet cable to the dataTaker and my connection comes back to life.

From all of this testing I see two key, albeit conflicting, points:

1) The TestPC has never lost the (wireless) connection to the laptop, even after sitting idle for extended periods.
This tells me that the DLink is working as expected and the issue must be with the dataTakers.

2) The TestPC has never lost the (wired) connection to the dataTakers, even after sitting idle for extended periods.
This tells me that the dataTakers are working as expected and the issue must be with the DLink.

Arrgh!

normaleyes

Hi normaleyes,

Does it mean you have three logger behind DLink router?
Then using TestNet you try to access DLink wirelessly to each of the logger, is that correct?

How do you forward wireless access from DLink to each dataTaker?
It seems I missed some of the information.

That term of "window of opportunity" could be a time frame where the connection is there but is not fully established therefore it get disconnected automatically.
Perhaps it is an incorrect network setting.

Best regards,
Rudy Gunawan

Hi Rudy,

The DLink is not a router. It functions just like a wireless network card in a computer. It is physically connected to a non-wireless device by an Ethernet cable. The DLink is totally transparent on the network.

By using the switch, I am able to share the wireless connection with multiple devices. Windows 7 allows you to share an internet connection with other devices on a network in a similar way.

Here is a simplified diagram:

Wireless Router ))) ((( DLink --|Switch|-- dataTaker #1
|-- dataTaker #2
|-- Desktop Computer
Laptop )))

My "window of opportunity" is that period of time when I have the ability to establish a "conversation" between my laptop and the dataTaker. If I miss the window, I have to physically do something (recycle power, disconnect the Ethernet cable) to the dataTaker to get another chance for a "conversation".

Once a conversation has been established, my computer needs to "say something to" (ping) the dataTaker every minute or the conversation is dropped. It's like the window of opportunity is restarted at the end of each interaction and the conversation must be continually active.

Which brings us to your last statement - "Perhaps it is an incorrect network setting." Yes indeed. There aren't many settings or parameters related to Ethernet or network, and I've tried changing just about all of them.

Any thoughts on what I may have overlooked?

Thanks for your time.
normaleyes

Hi normaleyes,

In my previous statement, I believe on the outer layer we talk about two devices: wireless router from server side and DLink from the client side.
And then the inner layer: between wireless router and laptop; between DLink and three devices (DT1, DT2, desktop).

This outer layer should have separate IP addresses than the inner layer.
Maybe the designated addresses are not correct between those layers.

Then because the differences of addresses between those layers, port forwarding might be required.
How do you forward an incoming wireless connection into one of those devices behind DLink?

Example:

192.168.5.2 Laptop 192.168.5.1 Wireless router - 10.75.60.120 ))) ((( 10.75.60.154 - DLink 192.168.2.1 --|Switch|-- 192.168.2.2 DT1 192.168.2.3 DT2 192.168.2.4 desktop

Best regards,
Rudy Gunawan

Hi Rudy,

Sorry for the long delay in my reply. I decided to try a different wireless client device to rule that out as the problem. I replaced the DLink with a Netgear WN2500RP Range Extender. I set it up so that it works in the same fashion as the DLink. I am having "close to" the same problem with the Netgear. The difference being my Window of Opportunity is of a longer duration. I now have more than 5 minutes but less than 15 minutes to connect and the same time frame to re-ping.

Here is a little more clarification regarding my network situation. All of the devices I am working with are on the same side of the Wireless Router, so they are all on the same subnet (or layer). The new Netgear has 4 ethernet ports, so I no longer need the Switch.
Wireless Router 192.168.99.1 ))) ((( Netgear 192.168.99.102 - dataTaker #1

Wireless Router 192.168.99.1 ))) ((( Netgear 192.168.99.102|-- dataTaker #1 192.168.99.15
|-- dataTaker #2 192.168.99.16
|-- Desktop 192.168.99.19
((( Laptop 192.168.99.20

I have no problem interacting with the devices that are physically connected to the Netgear. With the new Netgear, I now have about a 10 minute Window of Opportunity to interact with the dataTakers before they "drop off-line". The Desktop has never dropped off-line.

Since other devices don't drop off-line like this, I'm hoping to find a setting/switch/parameter in the dataTaker that needs to be changed. I just don't know what that might be.

Thanks for your time.

normaleyes

Hi normaleyes,

When you lose the connection, do you still see the same IP address in dataTaker display?
Could you send me dataTaker service log? There could be some clue in your existing DT setting.

Best regards,
Rudy

Hi Rudy,

I've attached profile setting. I hope it helps you help me.

Profile

[USER]
SITE = IP:192.168.99.15
[HOST_PORT]
BPS = 57600
DATA_BITS = 8
STOP_BITS = 1
PARITY = NONE
FLOW = HARDWARE
FUNCTION = COMMAND
[SERSEN_PORT]
BPS = 1200
DATA_BITS = 8
STOP_BITS = 1
PARITY = NONE
FLOW = NONE
MODE = RS232
FUNCTION = SERIAL
[USB_PORT]
FUNCTION = COMMAND
[HOST_MODEM]
EXT_POWER_SWITCH = NONE
DETECTION = DSR
INIT = AT
MAX_CD_IDLE = 43200
[ETHERNET_SESSION]
SMTP_SERVER =
SMTP_ACCOUNT =
SMTP_PASSWORD =
SMTP_PORT = 25
RETURN_ADDRESS = Your.Logger@datataker.com
SENDER_NAME =
RETRY_DELAY_S = 30
[ETHERNET]
ENABLE = YES
IP_ADDRESS = 192.168.99.15
SUBNET_MASK = 255.255.255.0
GATEWAY = 192.168.99.1
[PPP]
USER = DATATAKER
PASSWORD = DATATAKER
[FTP_SERVER]
PORT = 21
USER = DATATAKER
PASSWORD = DATATAKER
ALLOW_ANONYMOUS = YES
[NETWORK]
DNS_SERVER_1 = 205.175.225.1
DNS_SERVER_2 = 205.175.225.45
[COMMAND_SERVER]
PORT = 7700
SESSION_TIMEOUT = 0
[MODBUS_SERVER]
TCPIP_PORT = 502
SERSEN_ADDRESS = 0
HOST_ADDRESS = 0
USB_ADDRESS = 0
[NTP]
BACKGROUND_ENABLE = NO
SERVER = 0.datataker.pool.ntp.org
BACKGROUND_PERIOD = 3599S
MAX_SLEW_CORRECTION = 3S
MAX_JUMP_CORRECTION = 24H
MIN_CORRECTION = 50T
SLEW_RATE = 10
TIMEOUT = 2S
BACKGROUND_WAKEUP_DELAY = 3S
[LOCALE]
TIME_ZONE = -21600
[STARTUP]
RUN = CURRENT_JOB
MAINTAIN_OUTPUTS = NO
MAINTAIN_VARS = NO
[UNLOAD]
FTP_RETRIES = INFINITE
[DISPLAY]
AUTOSCROLL_INTERVAL = 0S
AUTOSCROLL_DELAY = 30S
AUTOACK_DELAY = 0S
[STORAGE]
FORMAT = NORMAL
UNLOAD_BUFFER_SIZE = 16384
[FUNCTION]
F1_LABEL =
F1_COMMAND =
F2_LABEL =
F2_COMMAND =
F3_LABEL =
F3_COMMAND =
F4_LABEL =
F4_COMMAND =
F5_LABEL =
F5_COMMAND =
F6_LABEL =
F6_COMMAND =
F7_LABEL =
F7_COMMAND =
F8_LABEL = Remove USB
F8_COMMAND = REMOVEMEDIA
F9_LABEL = Copy logged data
F9_COMMAND = COPYD dest=a: format=dbd archive=y src=BD
F10_LABEL = Auto Ethernet IP
F10_COMMAND = PROFILE ETHERNET ENABLE=YES; PROFILE ETHERNET IP_ADDRESS=0.0.0.0; PROFILE ETHERNET IP_ADDRESS=AUTO
[SWITCHES]
C = ON
D = OFF
E = ON
F = OFF
H = OFF
I = OFF
K = ON
L = OFF
M = ON
N = ON
R = ON
S = ON
T = OFF
U = ON
W = OFF
X = OFF
Z = ON
[PARAMETERS]
P0 = 0
P3 = 30000
P4 = 1
P8 = 0
P9 = 1
P11 = 60
P14 = 30000
P15 = 2
P16 = 0
P17 = 30000
P20 = 2
P21 = 0
P22 = 32
P24 = 13
P26 = 60
P27 = 0
P28 = 0
P31 = 2
P32 = 8
P33 = 0
P36 = 1
P38 = 46
P39 = 0
P40 = 58
P41 = 3
P50 = 0
P51 = 6
P53 = 10
P55 = 16383
P56 = 0
P62 = 0

In the mean time, I have found a way to establish a persistent connection. If I launch and connect with DeTransfer and leave it running, the dataTaker stays "awake" for any other interaction with me or other users. The down side is that I need to have a computer logged in all the time to be able to keep DeTransfer running. But it works.

I'd still like to find out why I have the limited "window of opportunity" to make the connection.

normaleyes

Hi normaleyes,

Could you try to use 192.168.99.102 as dataTaker gateway?
Because dataTaker is actually member of Netgear (not member of Wireless Router).

Then if possible disable DHCP assignment on Netgear since you have set a manual IP address in dataTaker.
Remove DNS setting from dataTaker as well as these setting have been handled by Netgear and Wireless Router.

Best regards,
Rudy Gunawan

Hi,
Any solution for this? I am facing similar problem and I am using TP-Link.

TQ [Chandran]

Hi Chandran,

There might be connectivity issue on bridge client connection like previously discussed, perhaps WiFi modem with masquerading option is a better choice.
Unfortunately I am not an expert in WiFi connection.

Best regards,
Rudy Gunawan