Telnet tutorial

Try this command:

help

It brings up a huge list of commands available to use in telnet.

Unless of course you're asking about how to program the processor to "talk" via telnet with something.

flcusat wrote:

Which is the same command I send in NS but it tells me that is an invalid command in Telnet. What am I missing?

Did you actually connect to the master and log in first?

I've never done this but if you you type "msg on" while in the master telnet you should get all the debug feedback you would normally see from a send_string 0. This of course requires your code to have these send_string 0 to begin with and if it requires a nDeBug variable of some name set to permit these messages then that needs to be set as well.

flcusat wrote:

when I type superuser I get invalid command.

I just tried it with a NI-700 that's sitting on my desk, seemed to work for me.

Attempt to summarise and add some hints and tricks

What an entertaining thread, I guess we don't know what we don't know, me included!

Here is my attempt at the Telnet tutorial that ficusat asked for:

Telnet is a commonly used method of using IP so that a person at a keyboard can talk to something on the other side of a network.

In the context of AMX programming, this usually means setting up a telnet session from a PC to a NetLinx master in order to do housekeeping on the master, to experiment, or to monitor debug messages generated by code on the master.

To establish a telnet session, connect both your PC and the master to the network and assign static IP addresses to both (optional but best).

Now run the cmd line. Click on Start / Run and type in

cmd<enter>

On older machines you may need

command<enter>

You should see a black window. This is the DOS command line of your PC. Yes, you still have DOS in there. Don't know what DOS is? Google can help!

If you want to avoid that palaver above, find cmd.exe in your Windows system folder and drag a shortcut to your desktop.

Enter the following command:

telnet <IP address of master><enter>

eg

telnet 192.168.0.100<enter>

and you should immediately connect.

Note that this works but is a bit crappy - window sizing is very annoying. A decent telnet client would be better - can anyone recommend one?

To make that easier next time, make a DOS batch file. First note the directory in which your DOS box opens. Now use a text editor to create a simple text file in that directory called "a.bat" with contents "telnet 192.168.0.100". Now to connect from the DOS box just type in

a<enter>

To send debug messages from code, the code should contain lines like

send_string 0,'This just happened'

To see those messages in your telnet session, type in

msg on<enter>

You almost always want to do this but I haven't worked out an automated way to do it yet. I guess it would be easy to script in a decent telnet client.

To see what else you can do in the telnet session, type in

help<enter>

If you want MORE POWERFUL STUFF type in

superuser<enter>
help<enter>

and gosh what dangerous stuff you can do!

Now try sending a string:

send_string 5001:1:1,'Hello'

and watch the 1st serial port led flash.

To send a command to a virtual device, try

send_command 33001:1:0,'Hi'

or

send command 33001:1:0,'Hi'

You can refer to a device by its code name

program_name='Fred'

define_device

dFred = 33001:1:0

send_command dFred,'Yo'

NMarkRoberts wrote:

send_string 5001:1:1,'Hello'
send string 5001:1:1,'Hello'

send_command 33001:1:0,'Hi'
send command 33001:1:0,'Hi'

This also works:
send c
send s

So any of the following:
send_string 5001:1:1,'Hello'
send string 5001:1:1,'Hello'
send s 5001:1:1,'Hello'

send_command 33001:1:0,'Hi'
send command 33001:1:0,'Hi'
send c 33001:1:0,'Hi'

Ok, that works from the cmd DOS page and I usually go from cmd to the telnet DOS page where you need the "o".

I've been going to Run>cmd (ok)

---

Then

---

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DVining>telnet (type telnet then enter)

---

Then

---

Welcome to Microsoft Telnet Client

Escape Character is 'CTRL+]'

Microsoft Telnet> o 192.168.1.60 (hit enter key)

---

as opposed just doing:

Run>cmd (ok)

---

Then

---

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DVining>telnet 192.168.1.60 (then enter)

---

Just another reason it seems everything I do just takes longer that it should!

I vastly prefer using Hyperterminal for Telnet; I have the Private edition, not the one packaged with Windows. It allows me far more customization, text capture, and as many stored setups as I care to make.

try "do_push()"

flcusat wrote:

Another question. How can I simulate a push button in a touch panel? I'm sending this:

pulse[10001:5:1,5]

but there is not action executed.

do_push(dvpanel,nbtn). Note that this is one of the very few (maybe three) occasions when a device.channel pair is not enclosed in square brackets.

When I took the programmer courses, someone told me that using do_push could be dangerous, but the reason was not explained and I don't remember who it was.

Personally, I find do_push rather useful from time to time.

BTW, the default do_push press time is .5 seconds. You can use do_push_timed or do_push_timed_infinite for other press times.

A friend, who is the most experienced and accomplished AMX programmer I know, suggested that do_push is dangerous because it wouldn't work if the panel device was not online. I didn't think that was my experience, so I tested the question and it seems to me that the panel referred to in the do_push statement does not need to be online -- or even exist. You can use do_push with an imaginary panel so long as it's defined in define_device. Doesn't even need to be a virtual device.

That's what I saw with an NI700 -- I suspect it may be different for Access programming.

do_push() doesn't work in terminal/telnet

Sorry, I misunderstood what you were asking. do_push works in code, but is not a valid command via telnet, nor rs232 through the programming port(I don't hink it is, anyway). I suppose that in a discussion dedicated to the telnet dialog, I should have realized.

I don't know how to simulate a button press from telnet. If I want to do it while trouble shooting or experimenting, I use the emulate device functionality in Netlinx Studio diagnostics.

When you pulse a touch panel channel (or turn one on or off) from telnet, you're manipulating touch panel feedback.