PK232.8
All users with PK-232's and PK-87's can use the MBX command in the following
manner with the NET/ROM nodes. Normally, MBX call1 monitors packets being
sent by "call1", such as from a BBS, etc. MBX call1,call2 monitors just
text being exchanged between those two stations. (Presumably it should also
prevent other packets from being included which were being sent to other
stations, but for some reason other packets find their way to the display
with W6IXU multibox.) With the NET/ROM nodes going up, here's some info for
using MBX for proper monitoring:
If the user is local and going to another user with just the one local node,
use local-15,remote. For instance, WB6WKB is using the node W6AMT-3 to get to
WB6SAN, the node will be using WB6WKB-15 to talk to WB6SAN. The MBX should be
set to WB6WKB-15,WB6SAN. If WB6WKB is talking up the network to someone else,
use the node's callsign instead, since it's whom WB6WKB is actually talking to.
In this case, set MBX WB6WKB,W6AMT-3 (assuming W6AMT-3 is the node involved
and WB6WKB is visible to you). Internode exchanges and transmissions from the
node to other stations are not shown. It's the next best thing to being the
connectee! MBX does not work on two callsigns which are not connected to each
other, so you can't follow two BBS's simultaneously.
Otherwise, I've found it very useful, many times saving me the hassle of
having to connect to read the newest messages or to download the latest
Pathefinder or Gateway.
GW1NGL NA7KR Kevin Roberts Ham Radio
Page last updated on 09/10/2012 by Kevin Roberts NA7KR a colection of Ham Radio and Electronic Information
All users with PK-232's and PK-87's can use the MBX command in the following
manner with the NET/ROM nodes. Normally, MBX call1 monitors packets being
sent by "call1", such as from a BBS, etc. MBX call1,call2 monitors just
text being exchanged between those two stations. (Presumably it should also
prevent other packets from being included which were being sent to other
stations, but for some reason other packets find their way to the display
with W6IXU multibox.) With the NET/ROM nodes going up, here's some info for
using MBX for proper monitoring:
If the user is local and going to another user with just the one local node,
use local-15,remote. For instance, WB6WKB is using the node W6AMT-3 to get to
WB6SAN, the node will be using WB6WKB-15 to talk to WB6SAN. The MBX should be
set to WB6WKB-15,WB6SAN. If WB6WKB is talking up the network to someone else,
use the node's callsign instead, since it's whom WB6WKB is actually talking to.
In this case, set MBX WB6WKB,W6AMT-3 (assuming W6AMT-3 is the node involved
and WB6WKB is visible to you). Internode exchanges and transmissions from the
node to other stations are not shown. It's the next best thing to being the
connectee! MBX does not work on two callsigns which are not connected to each
other, so you can't follow two BBS's simultaneously.
Otherwise, I've found it very useful, many times saving me the hassle of
having to connect to read the newest messages or to download the latest
Pathefinder or Gateway.
GW1NGL NA7KR Kevin Roberts Ham Radio
Page last updated on 09/10/2012 by Kevin Roberts NA7KR a colection of Ham Radio and Electronic Information