So,
I finally connected all my Ethernet TEA Devices to a network and I am having trouble with my Tektronix AFG3252.
First I don't fully understand why there is a Ethernet port there, in all the manuals I read, they tell you how to set it up but no clue what you can do for it.
After more reading I assume it can be used by the software ArbExpress, so I downloaded the last compatible version for my old mister:
https://www.tek.com/signal-generator/afg3000-function-generator/afg3011-software/arbexpress-waveform-creation-and-editinbut no joy I am getting an error message and I can't connect.
A few info more:
1) DHCP works
On my AFG3252 if I turn DHCP on, I get a "good" IP automatically.
2) I can see the AFG3252 by pinging it
3) Here the error message I get:
Here the AFG3252 settings:
Any idea?
Thanks in advance.
Do you have DHCP set for On on the AFG? (although it shows 10.14 it also seems to be showing Off). Keep trying with DHCP On. The error message indicates it doesn’t know its mode: GPIB or Ethernet - is there a menu setting that let’s you specify one or the other or both as enabled? Likely when you get it connected to app software you will be able to make Arbs and maybe/probably be able to remotely control other settings (waveform type such as sine, square, etc plus frequency and amplitude etc).
Hi, your Windows PC should have static IP address 192.168.10.1 see attachments
See page ~18
https://download.tek.com/manual/071163105web.pdf#page79Push the front-panel Utility button. Push the I/O Interface > Ethernet bezel buttons.
The Ethernet Network Settings menu is displayed.
By selecting the DHCP On, the instrument can set its network address automatically through DHCP.
You might need to assign a static IP address but first be sure to enable remote control through the front panel Utility menu; if that doesn’t work with DHCP then try setting up a static IP address (on both the AFG and the PC as ivi_yak shows) - but first make sure the Utility setting is enabled for ethernet. DHCP will probably work fine after Utility is set for ethernet I/O enabled.
Page 18, Step 3
The fact that you can successfully ping the machine doesn't answer all the questions.
Did you scan the open ports?
If not, that should be your next step to see which services are available on the machine.
The fact that you can successfully ping the machine doesn't answer all the questions.
Did you scan the open ports?
If not, that should be your next step to see which services are available on the machine.
Hi Sir! It was on my todo list:
with DHCP off
nmap 192.168.10.14
Starting Nmap 7.80 ( https://nmap.org ) at 2020-05-15 13:42 W. Europe Daylight Time
Nmap scan report for localhost (192.168.10.14)
Host is up (0.000098s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
MAC Address: 08:00:11:1F:23:2E (Tektronix)
with DHCP on
nmap 192.168.10.78
Starting Nmap 7.80 ( https://nmap.org ) at 2020-05-15 13:47 W. Europe Daylight Time
Nmap scan report for localhost (192.168.10.78)
Host is up (0.0034s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
MAC Address: 08:00:11:1F:23:2E (Tektronix)
nmap -p- 192.168.10.78
Starting Nmap 7.80 ( https://nmap.org ) at 2020-05-15 13:48 W. Europe Daylight Time
Nmap scan report for localhost (192.168.10.78)
Host is up (0.00029s latency).
Not shown: 65532 closed ports
PORT STATE SERVICE
111/tcp open rpcbind
1005/tcp open unknown
1008/tcp open ufsd
MAC Address: 08:00:11:1F:23:2E (Tektronix)
Nmap done: 1 IP address (1 host up) scanned in 14.98 seconds
Interesting.
EDIT: Same results with DHCP off.
Hi, your Windows PC should have static IP address 192.168.10.1 see attachments
Why my PC IP should match the GATEWAY of the AFG3252?
Anyway I tried it, it does not work.
By selecting the DHCP On, the instrument can set its network address automatically through DHCP.
DHCP works but regardless I can not talk with the device.
You might need to assign a static IP address but first be sure to enable remote control through the front panel Utility menu
I press Ethernet Menu and I get the ETH menu configuration, does it means the ETH remote control is enabled?
Anyway ArbExpress does not want to.
Downgraded ArbExpress to v2.9, same results.
This time 2.9 ArbExpress complains to not find a TEKVISA SW installed.
Do I need TEKVISA? According to the tek support page TEKVISA is not supported by any AFG...
Hi, your Windows PC should have static IP address 192.168.10.1 see attachments
Why my PC IP should match the GATEWAY of the AFG3252?
Anyway I tried it, it does not work.
Of course it shouldn't.
You PC has one IP. Your GW has another one and your AFG has another one.
From IP standpoint all is good.
With/out DHCP all is working as it should.
Now, you need to enable something on the AFG to allow remote access or some process is not running in the AFG to let you access its features.
I don't know what is the use of those 1005, 1008 ports. Maybe one of them is SCPI.
I guess tv84 suggested that you should scan for open ports on the tek:
nmap -p- 192.168.10.14
Thanks tv84, we are on the same page.
What worries me, during the ArbExpress 3.1 install, I got a message at the end like: "please install .NET framework 1.1 or above, if you have it already you can ignore this message."
I had very bad experiences in the past with SW that are using .NET framework.
Now if I try to install .NET framework 4.7 it tells me it's already installed and I do not need to
...
I send an email to Tek support... will see.
BTW: Is Tek not in this forum yet? I know about Keithley, Keysight, R&S and many others....
Are you sure per Page 18, step 3 that you turned on Ethernet? If so, try turning on GPIB and see if that shows as enabled in the menu you posted earlier. If GPIB displays as On, toggle back to ethernet and see if it shows as On.
Post a photo showing the I/O interface menu item showing ethernet is selected.
Are you sure per Page 18, step 3 that you turned on Ethernet? If so, try turning on GPIB and see if that shows as enabled in the menu you posted earlier. If GPIB displays as On, toggle back to ethernet and see if it shows as On.
Post a photo showing the I/O interface menu item showing ethernet is selected.
I can't be sure because I can't find a menu where you can select GPIB or/and Ethernet.
Here a Video for you (you can also see the DHCP working):
https://www.dropbox.com/s/f2z6fxce70zchsc/2020-05-15%2015.13.15.mp4?dl=0Anyway back to the manual, the step 3 on page 18 is to set up the Ethernet, does it mean also activate it?
nmap -p- 192.168.10.78
1005/tcp open unknown
1008/tcp open ufsd
Can you now say:
telnet 192.168.10.78 1005or
telnet 192.168.10.78 1008If it connects, say
*IDN? (page 2-24 of the
Programmer Manual)
For example, here is me talking to my scope:
~> telnet 10.40.23.22 4000
Trying 10.40.23.22...
Connected to 10.40.23.22.
Escape character is '^]'.
*IDN?
TEKTRONIX,MDO4054C,C012223,CF:91.1CT FV:v1.08
You get the idea.
Are you sure per Page 18, step 3 that you turned on Ethernet? If so, try turning on GPIB and see if that shows as enabled in the menu you posted earlier. If GPIB displays as On, toggle back to ethernet and see if it shows as On.
Post a photo showing the I/O interface menu item showing ethernet is selected.
I can't be sure because I can't find a menu where you can select GPIB or/and Ethernet.
Here a Video for you (you can also see the DHCP working):
https://www.dropbox.com/s/f2z6fxce70zchsc/2020-05-15%2015.13.15.mp4?dl=0
Anyway back to the manual, the step 3 on page 18 is to set up the Ethernet, does it mean also activate it?
Ok, thanks for posting the video. That's helpful. Hang in there. This thing is going to connect.
Yes, I think selecting Ethernet does seem to be activating Ethernet (but it would be interesting to also see what happens when you select GPIB. Does that disable Ethernet?) Assuming you have Ethernet enabled.... next thought....
I noticed that when you turned DHCP on it showed an address of 192.168.10.78 and when you turned DHCP off it set the address to 192.168.10.14. That is interesting because you had DHCP off, so it had to get 10.14 from somewhere - probably your router. You might look in your router to confirm everything is set appropriately.
Next place to look again is where ivi_yak suggested, which is on your PC port card. Maybe check those settings. Probably preaching to the choir, but your PC port, router, and the AFG all need to work together in the network. One of the three is doing something off kilter that we haven't found yet.
Do you have any other devices on your network beside the PC that you can confirm are accepting addressing handouts via DHCP as normally expected?
Another thought.... Any chance you have MAC filtering on somewhere?
Hi, your Windows PC should have static IP address 192.168.10.1 see attachments
Why my PC IP should match the GATEWAY of the AFG3252?
Anyway I tried it, it does not work.
Of course it shouldn't.
You PC has one IP. Your GW has another one and your AFG has another one.
From IP standpoint all is good.
With/out DHCP all is working as it should.
Now, you need to enable something on the AFG to allow remote access or some process is not running in the AFG to let you access its features.
I don't know what is the use of those 1005, 1008 ports. Maybe one of them is SCPI.
I think OP might have meant should the PC and the AFG both match (use) the same Gateway address (192.168.10.1), and the answer is yes. Having said that of course each device should have it's own IP address.
What kind of router is being used? Any chance the router supports Wifi in addition to ethernet cables? If so, any chance MAC filtering is on? It's strange because it looks like the ping tests show connectivity but the device isn't fully connecting. Also, as mentioned DHCP is showing 10.74 and the ping tests and one of the (DHCP OFF) screens showed 10.14. I think it would be good to make sure via either DHCP or a static address we're consistently square on the device address, and then look at why ping works but the data isn't getting through. It's going to be a big Duh for all of us when it starts working.
Are you sure per Page 18, step 3 that you turned on Ethernet? If so, try turning on GPIB and see if that shows as enabled in the menu you posted earlier. If GPIB displays as On, toggle back to ethernet and see if it shows as On.
Post a photo showing the I/O interface menu item showing ethernet is selected.
I can't be sure because I can't find a menu where you can select GPIB or/and Ethernet.
Here a Video for you (you can also see the DHCP working):
https://www.dropbox.com/s/f2z6fxce70zchsc/2020-05-15%2015.13.15.mp4?dl=0
Anyway back to the manual, the step 3 on page 18 is to set up the Ethernet, does it mean also activate it?
Right after you hit Utility and then I/O interface the next two soft buttons you should see should be GPIB and Ethernet. It was hard to see in your video but it looked like you hit I/O interface and then quickly hit Ethernet - but I think just before you hit Ethernet the GPIB soft button was there.
Can you now say:
telnet 192.168.10.78 1005
or
telnet 192.168.10.78 1008
If it connects, say *IDN? (page 2-24 of the Programmer Manual)
Thanks but it does not work. Tomorrow I will continue to analyze the problem, now I go bed.
I'm sure you tried and I don't know why it would make any difference but try another ethernet cable?
Better ideas would be to 1) move the AFG to another network (different router and PC) and see if it behaves any different, and/or 2) add another new node (some other device) to your current network to make sure it connects.
Electro Fan, he has demonstrated that he has IP connectivity to the AFG, pings and DHCP working, etc.
Stop taking this to the physical realm. This is a logical thing.
- Have you tried to disable the FW in your Windows machine to be sure that you are not stopping any traffic from reaching the AFG?
- Does your router do any port limitation/FW?
- Have you seen (from other guys or manual) which ports should be open? In other words, have you investigated which ports the AFG app is supposed to use?
These are the fundamental questions that you need answers for now.
EDIT: Nico's right, assuming the PC and AFG is in the same subnet no worry about the router.
1) Just take the router out of the equation. If the devices are on the same network then the only function of the router is to provide IP addresses by DHCP.
2) Make sure every device has a unique IP address but matches the netmask. If the netmask says 255.255.255.0 it means the first 3 numbers of the IP address must be identical otherwise devices can not exchange IP traffic.
3) It could be a Windows firewall problem; disable the firewall just to rule it out.
4) Make sure the AFG3252 has the latest firmware