Rotar options
Tucnak supports many antenna rotators (called rotars in Tucnak). They are accessed by Hamlib, or over the network from another Tucnak. You can use more rotators at a time, so when you choose the menu item Setup -> Rotar options, a menu with the list of the rotators appears. Every rotator has a letter (the key) and your description. The lines of the disabled rotators end with (disabled). Select a rotator to open its dialog. The menu also has the items Add new rotator and Remove rotator.

Add rotator
Shows the rotator options:

- Enabled - uncheck it to switch the rotator off.
- Description is a text for the operator which describes the rotator.
- Hamlib - the rotator is accessed using Hamlib.
- Remote - the rotator is physically connected to another Tucnak over the network.
- Filename - the port where the rotator is connected (/dev/ttyS0, /dev/ttyUSB0 or COM1). For network-controlled Hamlib rotators it is the hostname (for model 1 use 127.0.0.1).
- Hostname - the IP address of the other Tucnak for the type Remote. You can find it in Network info.
- UDP port - the port of the other Tucnak for the type Remote (it is a TCP port, normally 55555).
- Poll interval [ms] - the delay between the QTF queries, 300 to 2000 ms. A new rotator has 500 ms.
- Beam width - the value for the map to show the relevant antenna width. It is used also for the gain chart.
- Azimuth offset (0 to 359 degrees) - the difference between the scale of the rotator and the real azimuth. Tucnak sends azimuth minus offset to the rotator and shows the azimuth of the rotator plus offset. Use it when the zero of the rotator is not in the north.
- Hamlib model - the Hamlib model number of the rotator
- Hamlib speed - the speed of the serial port for the Hamlib rotator. 0 means the default value.
- Rotator letter for remote - the letter which the rotator has on the remote side.
Oct8tor
The first item of the rotator menu is Oct8tor. It opens the settings of the rotator system Oct8tor, see Oct8tor.
Remove rotator

Choose one rotator to remove from the configuration of Tucnak.
Problems with hamlib rotators
How to establish communication with a rotator using Hamlib.
First, we have to ensure that Hamlib is capable to work with your rotator. Under Linux open a terminal window. Under Windows run cmd.exe and change the directory to the Tucnak program files (C:\Program Files\Tucnak), where the installer puts rotctl.
Run rotctl -l (maybe enlarge the window to see all). The program lists all supported rotators. The first number is the model number. Choose the right model and type:
rotctl -m <MODEL> -r <COM> p
Example with an unconnected EasycommII:
bash$ rotctl -m 202 -r /dev/ttyS0 p get_pos: error = Communication timed out 0.000000
Detailed data is shown if you add the -vvvvv argument.
bash$ rotctl -vvvvv -m 202 -r /dev/ttyS0 p rotctl, Hamlib 3.1~git Report bugs to <hamlib-developer@lists.sourceforge.net>
rot:rot_init called initrots3_easycomm called rot_register (201) rot_register (202) rot_register (204) rot:rot_open called Opened rot model 202, 'EasycommII' Backend version: 0.4, Status: Beta easycomm_rot_get_position called easycomm_transaction called: AZ EL
write_block(): TX 7 bytes 0000 41 5a 20 45 4c 20 0a AZ EL . read_string(): Timed out 0.300000 seconds after 0 chars easycomm_transaction read_string failed with status -5 easycomm_rot_get_position got error: -5 get_pos: error = Communication timed out rot:rot_close called rot:rot_cleanup called
If rotctl is not able to work with your rotator, Tucnak will not work either, but the problem is in Hamlib. Contact the Hamlib development team, send detailed info with -vvvvv.