2.7.1 Networking setup - no such element in array

[AC9BJ]

Hello!

I'm having trouble setting up a networked configuration.  If run inied.tcl, select the Networking tab, and set things as follows:

Net Enable: 1

Message Popup: 1

Pass Prompt: 1

Verbose Logging:1 or 0; doesn't matter

...

My Peer Name: Foo

Peer 1: Bar 1.2.3.4 50 144 432

Peer x: stationx 127.0.0.1 0

...

then when I run Roverlog, I get the following error message that renders the whole program unusable, as it comes back immediately upon dismissal:

can't read "stuff(peersid,1)": no such element in array

can't read "stuff(peersid,1)": no such element in array

    while executing

"set s $stuff(peersid,$peerno)"

    (procedure "Peer_Puts" line 4)

    invoked from within

"Peer_Puts $peerno $r"

    (procedure "Net_Send_Kernel" line 92)

    invoked from within

"Net_Send_Kernel $what $i $msg"

The only recourse is to kill off the program from the process manager.

Am I doing something wrong?  What is the correct way to set up Networking?

I've confirmed this also happens in 2.7.0 and 2.6.11

-- 

Thomas AC9BJ

Mount Horeb, WI  EN53da

[Tom Mayo]

Thomas,

If you have two PCs, then it should look something like this:

My Peer Name: Foo

Peer1: Foo 192.168.1.1 50 144 432

Peer2: Bar 192.168.1.2 222 902

Peerx: stationx 127.0.0.1 0

If you only have one PC for RoverLog, then networking should be disabled.

You have to list every PC in the list, not just the other PCs.

Tom.

--
You received this message because you are subscribed to the Google Groups "RoverLog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roverlog+u...@googlegroups.com.
To post to this group, send email to rove...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/roverlog/58f80ca7-e12c-497f-8b48-08d191ed3315%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Thomas]

Hi Tom,

On Mon, Aug 12, 2013 at 1:53 PM, Tom Mayo <tma...@gmail.com> wrote:

You have to list every PC in the list, not just the other PCs.

That worked much better; thank you.  I also needed to read the inied peer decription and thereby learn that I needed to include a TCP port to use.

The networked operation is quite nice; thanks for making the program.

--
-Thomas AC9BJ
Mount Horeb, WI  EN53da

[Tom Mayo]

Hooray!  Glad it is working.

--

You received this message because you are subscribed to the Google Groups "RoverLog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roverlog+u...@googlegroups.com.
To post to this group, send email to rove...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/roverlog/CAFe52LUYHiJc1zYJTid%3Dxp5%3DfvOCn3GYAY9PJDqa6cniNSpyuQ%40mail.gmail.com?hl=en.

[Thomas]

On Tue, Aug 13, 2013 at 11:33 AM, Tom Mayo <tma...@gmail.com> wrote:

Hooray!  Glad it is working.

One suggestion I would humbly submit would be to hide those peers with a tcp port of 0 - in the pass dropdown, in the station information window, and anywhere else they might be listed and/or selected.