East Tester ET3502 LCR-Bridge

[egonotto]

Hello,

can you enter an IP address manually. If so, is it recognized by your router?
In my case, all IP addresses start with 192.168.178 and the subnet mask is 255.255.255.0 and the Gateway is 192.168.178.1

Best regards
egonotto

[Martin72]

Hi,
I've already been through all that with the ET3502, and the ET3503 will be no different.
I entered the network data manually “back then” and the router recognized it briefly.
But then the ET35 seems to “close”.
You can also see this on the Ethernet socket, on the status LEDs.
After switching on, “traffic” can be seen for a short time and then it is quiet.
I asked East Tester to test this before sending the ET3503 and they promised to do so.
It also took longer for the status message to change to “shipped”.
But either they were just pretending, or it “works” for them and they'll think I'm an idiot by now - or they and I have completely different ideas about what an Ethernet port is and how to control it.

[w.v.s.]

There is one more IP mentioned in the firmware:

Code: [Select]

192.168.0.70
Did you listen with a packet-sniffer what it says before the ethernet connection hangs up?

[Martin72]

Not to date, no.
Is there a recommendation as to which tool is good for this?

[KungFuJosh]

Why are there even IPs in the fw?? Trying manually setting one the listed IPs from the fw and see if it makes a difference.

[w.v.s.]

Why are there even IPs in the fw?? Trying manually setting one the listed IPs from the fw and see if it makes a difference.

It think the first set contained just the default settings. But the last one I've found was completely separate. That is the one, which can make one curious.

[w.v.s.]

Not to date, no.
Is there a recommendation as to which tool is good for this?

I would try tcpdump, but I'm living in a linux world. Don't know what windows users would prefer. Maybe you have a raspi with linux installed that could try to talk to the meter?

[w.v.s.]

Wireshark was mentioned before with the ET4xxx serial communication. It seems to do ethernet, too. Maybe worth a try.

[Martin72]

I would try tcpdump, but I'm living in a linux world. Don't know what windows users would prefer. Maybe you have a raspi with linux installed that could try to talk to the meter?

I still have “Ubuntu on Windows” on my notebook.

[Martin72]

I asked East Tester to test this before sending the ET3503 and they promised to do so.
It also took longer for the status message to change to “shipped”.
But either they were just pretending, or it “works” for them and they'll think I'm an idiot by now - or they and I have completely different ideas about what an Ethernet port is and how to control it.

You have to hand it to the people at East Tester, they are really keen to help.
Today they sent me 2 videos to show that it works, they even downloaded the program I used last to show that it works.
And they emphasized again that they had explicitly tested the ET3503 before sending it out.
I believe them too, but somehow information must be lost between them and me as to why it works for them but not for me.
The language barrier is high, they can't speak English, I can't speak Chinese, it all goes through the alibaba translator.....
What you have to say goodbye to is the DHCP thing, they will probably have deactivated it at some point, probably because of what Dwaine had written about it (if it is active but there is no LAN connection when switching on, the device hangs).
They didn't write that, but that will be the reason why they keep coming back to manual entry.
Lastly, they wanted to know my network settings.
They have a break over the weekend anyway, but I'm wondering what I'm missing in all this.
As I said, in the meantime I don't think the Ethernet interface isn't working, it will probably work on the ET3502 too.
But something is still missing in terms of information.

[mawyatt]

Martin,

Next time you communicate with them, ask why they reversed the BNC connections from what everyone else has and been doing for decades?? Every LCR Meter we've seen or used all have the L on the left and H on the right looking at the front panel.

Reminds of the SPD3303X terminals spacing 

Best,

[Martin72]

Hi,
I can do that, but I don't think it will change anything.
It doesn't really matter.
"Fun fact: The test leads are reversed.
The red ones go to "L", the black ones to "H"...

Something else, take a look at the video:
https://drive.google.com/file/d/1fIFq-a9pUUXXN_lfatnbyEut-dqt6XQt/view?usp=sharing

They point there several times to the subnet mask.
Is it possible that this may not be 255.255.255.0 as usual?

[w.v.s.]

I would expect that 255.255.255.0 should work in an usual LAN-setup. Did they tell you what information you should get from that video?

[Martin72]

"Of course" not...

As I said, they really try very hard, but somehow something is "missing" in the communication.

[egonotto]

Hello,

the netmask is wrong in my opinion.
Can you try a wrong netmask as seen in the movie?
So:
IP address: 192.168.178.22
Netmask: 192.168.178.0
Gateway: 192.168.178.1

You can also choose another more suitable address for 22 if there are other conflicts.

Best regards
egonotto

[KungFuJosh]

Some of y'all need to do some reading: https://www.lenovo.com/us/en/glossary/netmask/

Or for a quick cheat sheet of what the specific subnets allow: https://dnsmadeeasy.com/support/subnet

[tautech]

"Of course" not...

As I said, they really try very hard, but somehow something is "missing" in the communication.

Have you tried a IPCONFIG command on your PC to double check Gateway and Subnet values ?

[egonotto]

Some of y'all need to do some reading: https://www.lenovo.com/us/en/glossary/netmask/

Or for a quick cheat sheet of what the specific subnets allow: https://dnsmadeeasy.com/support/subnet

Hello,

In the video, an incorrect number is entered in the Netmask field, which is not a netmask. But presumably the desired result is still achieved with the incorrect entry. I would therefore also try the procedure shown.

Best regards
egonotto

[KungFuJosh]

Since you mention it, maybe EastTester should read more about netmasks. 😉

[egonotto]

Hello,

yes, but it's not that easy. In https://www.lenovo.com/us/en/glossary/netmask/ it is claimed that "A netmask consists of consecutive 1s followed by consecutive 0s" which is not correct, because the original standard did not restrict subnet masks to select contiguous bits of the address.
But I don't think this is used anywhere.

Best regards
egonotto

[KungFuJosh]

They were making a binary comparison for some reason. 🤷

[tatel]

How do you get this data out of the hex file?

@Josh:

See pic...
Normally I know that when you activate DHCP, it takes a while and then the network data is “pulled”.
Here the menu remains as it is, regardless of whether it is on or off(DHCP).

Can you change IP, netmask and gateway? If so I would try to put a network configuration compatible with your network and deactivate DHCP (edit: on the new device, not in your network).

On a windows PC, ipconfig command, executed on a terminal, shows IP address of the PC, netmask and gateway. Then you could manually set the new device to use any free IP address in the range 192.168.X.1 to 192.168.X.254. Netmask and gateway would be the same you have in your PC.

But, since you use DHCP in your network, you need to make sure there's no chance DHCP server could try and assign to other device the IP address you want for the new device, nor that you assign to the new device an IP already in use.

You should get into your router, which is the gateway. Probably it would be enough to point your web browser to the IP of your gateway, i.e: http(s)://192.168.1.1 or something like that. There you should look at DHCP server configuration carefully.

Usually DHCP servers are configured to never assign IP addresses in some arbitrary address pool of your LAN, i.e. it assigns addresses, say, between 192.168.1.2 and 192.168.1.200. In that case you would manually assign to the new device any (free) address between 192.168.1.201 and 192.168.1.254. That way the new device will not need the DHCP service, it will work, and the remaining devices in the network will continue to do their DHCP business as usual.

On a home LAN, unless you modified something, probability of netmask not being 255.255.255.0 must be about 1 ppb. That netmask is what defines the number of devices your LAN can have. 255.255.255.0 means the three first groups of 8 bits in the IP address are fixed, and that only the last 8 bits are unlocked. So devices in that network can get addresses between X.X.X.0 and X.X.X.255 => 256 devices, each with its own IP address.

But, by definition X.X.X.255 is the broadcast address, used to send messages to all devices in the network, and X.X.X.0 is the network address (of your entire LAN), used for routing between networks. So you can't assign any of these two addresses to a device in your LAN. This leaves you with 254 possible addresses. The router/gateway usually gets the first address, but it could be any of these 254 addresses.

If I'm getting it right, some guy from East Tester told you to use an 192.168.1.0 as *netmask*? It has to be a communication error. Otherwise you'd have to guess he's high on something

(multiple edits for clarity)

[tatel]

Netmask in the video is 255.255.178.0 and gateway 192.168.178.1?

Using CIDR notation 255.255.255.0 is /24, meaning 24 bits are locked. You can do your subnetting any way fits you. If you need more than 254 addresses in your LAN, you could use a /16 bit netmask, and have 65534 addresses available. But the mask would be 255.255.0.0

You could use a /17 bit netmask and that would leave half the addresses available on a /16 subnet, but netmask would be 255.255.128.0

A /18 bit netmask would be 255.255.192.0

I'm not aware that netmask could use fractions of a bit. So that netmask is wrong. Perhaps they have a typo and it would be 255.255.128.0 which corresponds to a 17 bit netmask. If you need 32766 IP addresses available in your LAN, that's the way to do it.

Let's see what ipcalc says. We are going to use gateway' address and netmask of 17 bits to see what the resultant networks are:

tatel@gis:~$ ipcalc 192.168.178.1/17
Address:   192.168.178.1        11000000.10101000.1 0110010.00000001
Netmask:   255.255.128.0 = 17   11111111.11111111.1 0000000.00000000
Wildcard:  0.0.127.255          00000000.00000000.0 1111111.11111111
=>
Network:   192.168.128.0/17     11000000.10101000.1 0000000.00000000
HostMin:   192.168.128.1        11000000.10101000.1 0000000.00000001
HostMax:   192.168.255.254      11000000.10101000.1 1111111.11111110
Broadcast: 192.168.255.255      11000000.10101000.1 1111111.11111111
Hosts/Net: 32766                 Class C, Private Internet


So, even if that netmask would be the right one 255.255.128.0, which it isn't, this device will be able to speak only to other devices with IP address between 192.168.128.1 and 192.168.191.254. Quite probably you LAN is out of that range?

I think, you need to change that device network configuration and adapt it to your LAN configuration, as explained in the previous post. It should work with the usual 255.255.255.0 netmask as long as device's IP is in the address range of the LAN configured in your router. If not, get into your router via web browser, take some screenshots of your LAN configuration, and send it to these guys.