which ressource name is needed to connect iviscope initialise.vi and a scope on a netware (TCP/IP). tcpip::"IP adress"::INSTR doesn't work

[jean-phi]

Labview 6.1, run time engine 1.83, basic ivi class driver. I can ping the scope on the netware so my IP adress is goood but i can't see it under labview with or without MAX. I think the problem is the ressource name

[mvu]

Hi,

I currently have a Tek 3054B and use it through TCPIP. First off, I make sure that it is connected to the network and that my computer can see it. I do not know if your scope supports this feature, but this is how I check for connectivity: I open internet explorer and goto the address http://"instrument's ip address"/ with no quotes. This should (for me) pop up an interface that resembles the instrument. Then all I have left to do after I've confirmed that is to use VISA, or an IVI resource name control, and type in TCPIP::"Instrument ip address"::INSTR with no quotes to connect to it through labview. Look for an DHCP option somewhere in your instrument, please turn this on. This will get the instrument to find an available ip address to use on the network.
Also another problem could be that you are using the "gateway ip address" instead of the "instrument ip address" these are two separate things, you want to use the "instrument" option. If you are still having trouble, please mention what model instrument you are using and I will try to help further. Good luck!

[jean-phi]

Hi and thanks a lot for your answer.
I certainly have a problem on my netware. I can see my scope on the net by the command ping 10.35.0.100 every time i try. But if i try under windows by looking for a computer on the net with \\10.35.0.100 for the name, i never see it while i can see this way other connected PC.
My scopes are TEKTRONIX TDS3034B and LECROY WAVERUNNER LT344. I accept with pleasure every idea to test or every exemples VI
thanks again

[mvu]

Try http://10.35.0.100/, your other method will not work in trying to connect to your scope. I recommend using the tek 3034B because our two instruments are quite similar and would most likely work the same as in setting it up. Two, are you trying to connect both scopes at the same time? They cannot have the same ip address, as this will cause conflicts. Try to get the tek scope to auto configure a working ip combination. The instrument ip address, gateway ip address, subnet mask, and http port must all be set for things to work properly. If everything works properly up until now, try to see if it will work with the IVIscope initialize.vi. Under LabVIEW just type in TCPIP::10.35.0.100::INSTR or under CVI it is the same but must be inside quotes.

[jean-phi]

Unfortunately scopes are used most of the time and it's difficult to choose one but i'll try. Ip adress are different, the other one is 10.35.0.104. In fact i have to vi to try to connect and i use one of them in relation to the scope, not on the same time. Every thing is right to the seting excepted the http port that i can't find. Your method to connect doesn't work in my system and return me error 111, connection failed
iviscope Initialise doesn't work too. Perhaps a special setting of my netware doesn't work with this vi
I'll certainly try to do the connection with RS232 to be sure of my ivi driver.
Something else, i can see the Lecroy on the net with its own software only with the IP adress setting
Thank for your answer
i'll be
back on friday

[mvu]

Worth a shot, but I was having trouble connecting to my instrument via ethernet. I would keep getting these timeout errors. Well what fixed it was that I completely exited LabVIEW, turned the scope off, and then turned the scope back on with the ethernet cable already attached before hand. Now LabVIEW sees the instrument just fine. So basically, if you have LabVIEW running or the instrument on when you connect in the cable, things might not work properly. I hope this helps out.

[jean-phi]

I've tried another solution. I connect both the PC and the scope with a hub and the hub to the net. In that case i can see the scope. I don't know why exatly. The hub is a 10/100 Mbit/s, as well as the netware, but it's half duplex only. On the netware we have some connections full duplex and somes of them half duplex, controled by switches ... and perhaps my problem is here.
I've now others problems. If i send commands with default parameters (maybe bad parameters) when the scope isn't in a certain state, the connection failed and i have to turn off both the scope and LabView to recover. The driver isn't able to control that or maybe i do something wrong. Do you have some advices and is it the same thing with Lab Windo
ws ?
Thank you previously

[mvu]

Have you tried to connect the instrument through VISA Interactive Control? That should be the first step to do to find out what really is the problem. Just connect to TCPIP::::INSTR and if that connects then connecting it with an IVI control should be the same way.

[mvu]

To add on... Try upgrading your firmware revision of your scope. I have heard earlier versions were pretty buggy. You can download the upgrade from tekronix's website. I also noticed they had an upgrade / program for download in helping with connecting with TCP/IP connections. They should both be on the same page. Look up your scope then find the firmware updates page.