Rotor

[py4xx]

Hi Mike... 73.
Where do I set up the rotor?

[mbridak]

Hello Carlos,

You setup the rotator using rotctld using it's default port # of 4533.
If it's there Not1MM will find and connect to it as long as it's running on the same computer. That's about all there is to it.

I can see in the future adding the use of a non standard port number. Or even having different port numbers for different operating bands, in case the station has more than one. But seeing that I don't even own a rotatable antenna of any kind, this is a bit low on my priority list.

Cheers!
Mike K6GTE

[py4xx]

And how do I do this??? I didn't find anything in settings...

[mbridak]

..., File -> Configuration Settings, choose Lookup.

[py4xx]

Hi Mike.. 73...
See that my configuration is as you showed me, I put a PY1 call and the needle continues to indicate 180° of the real direction.
Do I need the rotor working??? I still haven't managed to get it to work. I don't know what not1mm has against me... kkkk In CQRLog the rotor turns normally...

[mbridak]

Same reason. Still has 'Regional' to the left of the heading. So for some reason you're not getting a valid return from QRZ.

[mbridak]

I've added a critical log entry output for qrz session fails. So if launched from a terminal and your session fails, it'll show the error returned from QRZ. Like:

[2025-06-18 10:12:19,212] CRITICAL lookup - getsession Line 173: key: error:Username/password incorrect message:

Hope that helps.

[py4xx]

Hi Mike... 73...
Can we do a test?

Make not1mm accept both:
AZ= 255
and
+0255

Why?

I discovered that the K3NG firmware sends both pieces of information together and this, I believe, is causing my configuration not to be accepted by rotctld, which only receives "+0255" and since AZ=255 arrives first, rotctld rejects it and therefore, it fails.

If we can do this test, we would clear up this doubt.

Thank you

[mbridak]

Not sure what you mean. I don't have a way to tell rotctld what to accept from your k3ng device.
The only thing not1mm is doing is talking to rotctld, which is an abstraction layer.

I'm assuming the -m device number you choose when starting up rotctld tells it what to expect from your k3ng device.
And this is defined from which feature you un-commented in k3ng source code.

The unit is interfaced to the computer simply using the native Arduino USB port. Currently Yaesu and Easycom protocols are supported.

To enable Yaesu GS-232A emulation, uncomment this line:

#define FEATURE_YAESU_EMULATION

To activate Yaesu GS-232B emulation, also uncomment this line:

#define OPTION_GS_232B_EMULATION

To activate Easycom emulation, uncomment just this line:

#define FEATURE_EASYCOM_EMULATION

So if we grep the output from rotctld -l These device numbers seem reasonable to choose from.

   601  Yaesu                  GS-232A                 20220109.0      Stable        ROT_MODEL_GS232A
   602  Various                GS-232 Generic          20240921.0      Stable        ROT_MODEL_GS232_GENERIC
   603  Yaesu                  GS-232B                 20220109.0      Stable        ROT_MODEL_GS232B
   606  Yaesu/Kenpro           GS-232                  20220109.0      Stable        ROT_MODEL_GS232
   609  Yaesu                  GS-232A azimuth         20220109.0      Stable        ROT_MODEL_GS232A_AZ
   611  Yaesu                  GS-232B azimuth         20220109.0      Stable        ROT_MODEL_GS232B_AZ
   201  Hamlib                 EasycommI               20231219.0      Stable        ROT_MODEL_EASYCOMM1
   202  Hamlib                 EasycommII              20231218.0      Stable        ROT_MODEL_EASYCOMM2
   204  Hamlib                 EasycommIII             2022312180      Stable        ROT_MODEL_EASYCOMM3

Which one is right.... I have no idea.

[py4xx]

Hi Mike... 73... Actually, I've already tested all the YAESUS on this list. But I just realized that not1mm doesn't receive data directly from K3NG, but from rotctld... So rotctld isn't accepting the information AZ=255. It only accepts the information "+0255". So, I can only apologize for not realizing this before... Since I don't know how to program, I don't know how to modify K3NG to invert this information. The strange thing is that in CQRLog, the rotor turns when I click on the CCW and CW buttons. Go figure... kkkk 73. Em dom., 22 de jun. de 2025 às 01:32, Michael Bridak < ***@***.***> escreveu:

…

Not sure what you mean. I don't have a way to tell rotctld what to accept from your k3ng device. The only thing not1mm is doing is talking to rotctld, which is an abstraction layer. I'm assuming the -m device number you choose when starting up rotctld tells it what to expect from your k3ng device. And this is defined from which feature you un-commented in k3ng source code. The unit is interfaced to the computer simply using the native Arduino USB port. Currently Yaesu and Easycom protocols are supported. To enable Yaesu GS-232A emulation, uncomment this line: #define FEATURE_YAESU_EMULATION To activate Yaesu GS-232B emulation, also uncomment this line: #define OPTION_GS_232B_EMULATION To activate Easycom emulation, uncomment just this line: #define FEATURE_EASYCOM_EMULATION So if we grep the output from rotctld -l These device numbers seem reasonable to choose from. 601 Yaesu GS-232A 20220109.0 Stable ROT_MODEL_GS232A 602 Various GS-232 Generic 20240921.0 Stable ROT_MODEL_GS232_GENERIC 603 Yaesu GS-232B 20220109.0 Stable ROT_MODEL_GS232B 606 Yaesu/Kenpro GS-232 20220109.0 Stable ROT_MODEL_GS232 609 Yaesu GS-232A azimuth 20220109.0 Stable ROT_MODEL_GS232A_AZ 611 Yaesu GS-232B azimuth 20220109.0 Stable ROT_MODEL_GS232B_AZ 201 Hamlib EasycommI 20231219.0 Stable ROT_MODEL_EASYCOMM1 202 Hamlib EasycommII 20231218.0 Stable ROT_MODEL_EASYCOMM2 204 Hamlib EasycommIII 2022312180 Stable ROT_MODEL_EASYCOMM3 Which one is right.... I have no idea. — Reply to this email directly, view it on GitHub <#340 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZLHTQ7CDHB3572L5JTTJ5T3EYWVVAVCNFSM6AAAAAB7JIG4DCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJUGA3DOMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>