| If possible you should use Microsoft RAS
instead of CiNet. Microsoft RAS is easier to configure, faster, has
more features and is more reliable than CiNet. See the Microsoft
Windows documentation on how to setup RAS. Microsoft RAS is
supported on Windows for Workgroups 3.11, Windows 95 and Windows
NT. You should only need to use CiNet if you are running Windows
3.x. CiNet is now considered obsolete and its support will be
removed in future versions of Citect.
To configure Citect to talk from a remote computer to a host via
Cinet you need to do the following:
- Connect the remote and host via a null modem cable and make
sure that you can establish communications between the two
machines.
- Connect the 2 modems and start terminal on both machines then
dial the host machine via the remote computer. If the host computer
shows it is just ringing then you need to configure the modem so
that it answers on the first ring. This can be done via terminal by
typing
ATS0=1
You can also use the command
AT&V
to view your profiles
- In both computers you will need to edit the CITECT.INI file and
add the parameter. the watch time parameter should be set to a
different value on each machine eg:
Host
[LLC]
Watchtime=35
Remote
[LLC]
Watchtime=40
This parameter controls the frequency (in seconds) that the
driver uses to check the communications link to the I/O Device. The
difference between the two times will ensure that both do not try
to initialize communications at the same time. If you are using a
null modem cable then these values could be reduced to say 6 and 10
seconds, if you are using modems the time must be greater than the
time it takes for the modem to connect.
You should be able to have a 2 user multiuser dongle on the host
and no protection key on the remote. Once Citect has a connection
it will obtain the other licence. Sometimes though you may not be
able to connect before your demo mode times out. If this is the
case you made need to adjust this Watchtime parameter to a lower
value so that the remote tries to connect more often.
- Make sure you have echo turned off in both modems. If this is
turned on then any requests made by either computer from Citect
will be echoed back and Citect will think it has a connection when
actually it is just receiving what it has just sent out.
- Below is the communications setup in Citect for both the host
machine and the remote machine. Take note of the special options
which will be different depending on what version of Citect you are
using.
Host Machine
SERVER
Server Name : Server1
BOARDS
Server Name : Server1
Board Name : LLC_Board
Board Type : COMX
Address : 1 (For Comport 1)
Rest of the fields are blank
PORTS
Server Name : Server1
Port Name : LLC_Port
Port Number: Leave Blank
Board Name : LLC_Board
Baud Rate : 9600
Data Bits : 8
Stop Bits : 1
Parity: None
Special Options : -c
(Note: The -c option is only available in Citect V3.30 and
higher and does not require a modified cable as stated in KB
Article Q1868.
If using Citect V3.21 you will need to use the -h option as well
as the modified cable in Q1868.)
IODEVICES
Server Name : Server1
Name : Remote_1
Number : 1
Protocol : LLC
Port Name : LLC_Port
Rest of the fields are blank.
Remote Machine
SERVER
Server Name : LLC_Remote
BOARDS
Server Name : LLC_Remote
Board Name : Remote_Board
Board Type : COMX
Address : 1 (For Comport 1)
Rest of the fields are blank
PORTS
Server Name : LLC_Remote
Port Name : Remote_Port
Port Number: Leave Blank
Board Name : Remote_Board
Baud Rate : 9600
Data Bits : 8
Stop Bits : 1
Parity: None
Special Options : -iATDT (phone number)\M~{60} (e.g
-iATDT8551000\M~{60})
IODEVICES
Server Name : LLC_Remote
Name : Host
Number : 2
Protocol : LLC
Port Name : Remote_Port
Rest of the fields are blank.
|
