General philosophy of modem handling in JUMP Manager
Assumptions from modem handling in JUMP Manager:
- hardware handshake is used (DTR + RTS)
- CD (Carrier Detect) is heavily used to find out, whether modem is online.
If for given modem CD does not work (or is not connected) forget everything,
modem is unusable
How it works:
- We have 3 different protocols to handle. That is why at the
beginning modem can call several times.
- Modem (if it is not online) peridically sends initialization string to
modem. It is because with external modem you can connect it several hours
(or days) later then JUMP Manager was started.
During attemp to connect:
- Serial port of modem is put into one of possible regimes
(speed for ComProt4, IMT or IMV protocol).
- Modem is reinitialized
- Based on setting to call out or expect calls Autoanswer on modem is removed
or set
- Modem is heavily tried to be hanguped (ATH0 sequence) every time there is
a chance it is online and we change regime or so.
- Modem dials (using speed and params set before), attempts to discover
whether it is online (uses up to timout for waiting, which is currently
60 seconds, so please be patient). In case it connects, it tries to
discover protocol or communication with UPS on othr side). If it starts
to communicate using assumed protocol, everything is fine and it stays
connected.
- If modems were connected, but protocol was not right, regime (protocol) is
changed and we try again the same thing - to test new protocol for
communication with UPS.
- In order to save costs successful discovery of appropriate
protocol is written into database, so next time most probable (if UPS
was not changed) protocol is used as first, so we probably call next
time only once.
General philosophy is that modem support is as simple and as generic as
possible, with the hope that all modem dependence will be hidden in init
strings. Experience says, that after one finds semidecent init string
everything tends to work fairly smoothly.
There is useful command line switch: -serdebugCOMPORT
(where COMPORT is COM1 on Win, /dev/ttyS0 for Linux etc).
If you use it, it will start writting messages to console and user will see
what happens with modem (or serial line) at given moment. It is far from
perfect, but should be useful for understanding what is going wrong with modem.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.