Thursday, January 17, 2019

HOW TO PROPERLY SET XGGCOMMS'S DIGIMODE-3 INTERFACE TO WORK WITH UBUNTU 18.04


Hello to everyone.

    Recently I purchased a XGGCOMS Digimode-3 interface in order to take a step in to a digital world of FT8, JT9, PSK31 and other “egsotic” digital modes of work.
    I have second hand Icom 706MKII that works well and I thought buying a digi interface will be a good reason not to use it just for SSB modes of work but also trying to gain knowledge about new ways of usage of our ham equipment.
    After arrival I read manual published on seller’s site. It quite well (maybe it need some additional text inside) describe setting of Digimode-3 under Windows OS, but sadly there is no any written word or video record how to do it under Linux OS , especially with Icom 706MKII radio :)
    My first contact was so disappointing because no matter how much I tried , suggested ALC level stayed around 5-6 squares and even I managed to work some station with such a setup.
    There must be a way to do it under Linux, in my situation Ubuntu 18.04. And there is a solution. I do not know how much people who work HAM under Ubuntu or other Linux based system are experienced but for me I may say (middle experienced user) this OS is still sometimes a mystery. You do not see it on the menu bar or program bar, then you do not know that it exist :)

The fastest way to set digimode-3 is to do it with ALSAMIXER.

Note: My Ubuntu is set to work with gnome meta-city extension (oldie but Goldie) so this explanation is for this environment. For new Ubuntu 18.04 environment it is almost the same (sidebar).

1. Open with ctrl+alt+t terminal window and at the prompt write/start alsamixer.
- Choose proper audio device (C-Media USB set) with pressing F6 and select it from menu.
- In order to see all possibilities press F5  (View All).


Picture 1. Selecting Digimode-3 in alsamixer




- Moving around given settings is possible with your cursor keys left/right arrows.     Increase/decrease of values is set with up/down arrows.
- Go to Headphones.
- With Q/Z keys change of balance is made for left channel and with W/X keys you can balance right channel.
- Set to lowest possible value for both channels (around 33%) .


Picture 2. Help menu with keys


Note: Do not close or exit alsamixer and terminal window.

2.  From drop down menu Applications-System tools-Preferences-Settings-Sound select “Digital output S/PDIF – Audio adapter” . Set value of balance to be in the middle, and mic level should be minimum. Audio level should be at minimum or near minimum.
- Start WSJT-X and wait to load. From the right side, set power meter (gliding up-down bar line) to the middle or upper to ¾ of the bar.
- Set your radio to 50% of it power (I set mine to 50W for start) and get good SWR at 7.074 (FT8) or other work frequency of available digi modes.
- Set on your radio ALC level to be displayed.

3. In WSJT-X select option TUNE and get back to terminal window and alsamixer. For now, your radio should not transmit anything, because VOX level is not enough to activate TX.
- With Q/Z keys increment audio level ONLY to LEFT channel while right stays at it present level of 33%. Around 80% you should hear relay triggering TX on your Icom. Now it is transmitting and
ALC level should be absent (no ALC level readings on indicator).
- With W/X keys slowly increment ONLY RIGHT channel until you see only one bar of ALC level indicator. When you see it, get back one step lower. Now you have set best signal for digital work.
- Get back to WSJT-X and try to move power meter to higher position and get readings on your SWR/POWER meter. At present settings you should run around 20-30W of power without any ALC activation or distortion of signal.


Picture 3. Properly set of alsamixer and power meter (background)


- Deactivate TUNE option from WSJT-X.
- Close alsamixer (ESC key) and terminal window.

Your radio now is just one step from complete settings for digi work.

Note: If above settings (step number 3) did not trigger relay for TX, then slightly increase power meter in WSJT-X and try again will it trigger TX relay. Find the balance for trigger of TX relay ONLY with your LEFT channel and power meter. DO NOT TOUCH or set right channel, it is already set on it best value (for now). You can also try leaving your left channel value just below red zone and only try with power meter from WSJT-X. Changing values of power meter is best to be done with your mouse scroll wheel or touch pad trackball option.



4. Set MIC level (Microphone audio adapter) for good receive of signals. Suggested minimum signal level should be 30db (WSJT-X suggestion). Anything in the green zone is good signal value.


Picture 4. Setting MIC level for best receive signal




That’s all folks.
Now your digimode-3 is properly set to work with Ubuntu or other Linux based system.

Small note for authors of WSJT-X:
Increase/decrease of power in WSJT-X result with not so smooth change of output power like running under Windows. On my computer (Asus 1015PEM Intel Atom N550 dual core) there is some response delay of around 0.5 sec , difference between change of power and command reaction of the radio. Take note about this when changing power to new values.


73 DE PETRIKA
Z34PEC
KN01qx


Sunday, August 12, 2018

Welcome to your new home

Yesterday new receiver has arrived in my home: Icom 706 MKII .
Got it from a friend of mine that wasn't using it for over a year.
In a good condition, maintaned and keep well.
Well, maybe this is start of something new. Z3FF, BOTA, SOTA, who knows :)
I wish to everyone to have such a pleasant surprise and good unit.
73

Monday, April 23, 2018

HBR4HF my radio

After a longer period finally I managed to start work with my HBR4HF radio station. Declared as 25-30W , Bitx based radio, 3.5-7-10-14 MHz SSB/CW together with HF-P1 antenna and MFJ 971 ATU I tried to make some QSO's in past period. Unfortunately, not so much experienced in field activities, with lot of difficulties I managed to make my first contacts.
I must admit I was little bit unprepared for such activity and I failed. Well, RA life is made of failures and sucesses, so no dissapointed at all.
I must say, I have great satisfaction about this radio and I warmly suggest this radio as a good startup equiment for every RA.

If somebody want to buy it, he/she can go to Hambuilder's site and make an order.

The only negative side is maybe lack of technical documentation but I suppose designer of this radio will manage this problem also.

Weekend is coming and I hope I will continue to make new contacts with my equiment, mostly in portable mode.

Stay well,
73
Z34PEC

Monday, March 26, 2018

How to work with HAM satellites

Browsing the web, I stopped to this interesting blog site, also HAM oriented. It's name is AMSAT-UK and they have so much interesting texts.
Here is link to one of their blogswritten for communication with satelites with given frequencies and shifts.
AMSAT-UK how to work with HAM satelites.
Enloy,
Z34PEC

Wednesday, March 21, 2018

Vellman CW (Morse) decoder

Couple of days ago a friend of mine post add, selling his almost new Vellman cw decoding kit. I miss a moment so my other friend bought it. Today he make a post on FB that show this thing actually work despite all bad copies made from China :)
I google a little and I found schematics for this great cw (morse) decoder so I decided do make a "footprint" of it on my blog.
I hope someone will find it and use it and find it interesting too.
Enjoy.
Z34PEC

Saturday, February 24, 2018

Rooting ASUS Zenpad C7.0 (Z170C and Z170CG)

Hello,
Finally after more than a year of trying to make my ASUS Zenpad C7.0 Z170CG rooted I finally make it.
I succeed it under Ubuntu 16.04 as much more easier process than under Windows (no need for installing drivers for your Asus Zenpad).

I also have to say that this procedure is also working for Z170C version of Asus Zenpad C7.0.


Thanks to this guy

https://blog.stigok.com/post/unlock-bootloader-asus-zenpad-z170cg-p01y

and this manual on XDA Developers

https://forum.xda-developers.com/general/rooting-roms/asus-zenpad-c-7-0-p01y-root-method-t3567274

I rooted my device. Must say every credit goes to these guys not me. I just summarise the whole procedure at one place.

Update: DL Link to IMG File :

https://forum.xda-developers.com/attachment.php?attachmentid=3640170&d=1455053113



So, the procedure is following:

A. Install ADB and FASTBOOT

After installing you have to do 2 things on your device:

A-1. Enable USB Debugging
A-2. Revoke USB Debugging authorisations

The second one activate question should you allow access to your computer on your Zenpad. Answer positive and remember this with check box.
Now you have done right and no info in your terminal that it is Not Authorised (or something similar) while working

B. Connect your Asus device on USB, and allow everything asked on the screen.

C. The main procedure:

- Connect your device in Terminal:
    sudo adb devices
    List of devices attached
    HELLOWORLDSECRETSERIAL    device

- Reboot into fastboot

sudo adb reboot fastboot

- Unlock bootloader

sudo fastboot oem asus-go

THis will result in following response:
...
(bootloader)  Unlocking the bootloader means the following:
(bootloader)  All user data will be deleted
(bootloader)  Any securely stored data will be inaccessible
(bootloader)  Warranty will be void
(bootloader)  After unlocking you have to execute
(bootloader)  > fastboot format userdata
(bootloader)  > fastboot format cache
(bootloader)  or carry out a factory reset from recovery
(bootloader)  To confirm the unlock, please execute the command
(bootloader)  > fastboot oem unlock confirm
OKAY [  0.057s]
finished. total time: 0.057s

- Confirm unlocking

sudo fastboot oem asus-go confirm

And as a result you will get
...
(bootloader)  Unlocking and rebooting into unlocked state
OKAY [  0.070s]
finished. total time: 0.070s

- Get a var dump for later (copy this to some TXT file)

sudo fastboot getvar all

Result is something like this:

(bootloader)  version-baseband: 24832
(bootloader)  version-bootloader: 1638.500_M1S1
(bootloader)  product: SF_3GR
(bootloader)  secure: YES
(bootloader)  unlocked: YES
(bootloader)  off-mode-charge: 1
(bootloader)  ========== parition type ==========
(bootloader)  system parition type: ext4
(bootloader)  userdata parition type: ext4
(bootloader)  cache parition type: ext4
(bootloader)  hypervisor parition type: raw
(bootloader)  boot parition type: raw
(bootloader)  recovery parition type: raw
(bootloader)  splash parition type: raw
(bootloader)  mvconfig parition type: raw
(bootloader)  secvm parition type: raw
(bootloader)  vrl parition type: raw
(bootloader)  psi parition type: raw
(bootloader)  slb parition type: raw
(bootloader)  ucode_patch parition type: raw
(bootloader)  APD parition type: ext4
(bootloader)  ADF parition type: ext4
(bootloader)  factory parition type: ext4
(bootloader)  nvm_static_calib parition type: raw
(bootloader)  nvm_static_fix parition type: raw
(bootloader)  nvm_dynamic parition type: raw
(bootloader)  linux_nvm_fs parition type: ext4
(bootloader)  ===================================
(bootloader)  ========== parition size ==========
(bootloader)  system parition size: 0x0000000090000000
(bootloader)  userdata parition size: 0x00000002f0380000
(bootloader)  cache parition size: 0x0000000017200000
(bootloader)  hypervisor parition size: 0x0000000000100000
(bootloader)  boot parition size: 0x0000000001100000
(bootloader)  recovery parition size: 0x0000000001100000
(bootloader)  splash parition size: 0x0000000002080000
(bootloader)  mvconfig parition size: 0x0000000000080000
(bootloader)  secvm parition size: 0x0000000000c00000
(bootloader)  vrl parition size: 0x0000000000040000
(bootloader)  psi parition size: 0x0000000000020000
(bootloader)  slb parition size: 0x0000000000100000
(bootloader)  ucode_patch parition size: 0x0000000000003000
(bootloader)  APD parition size: 0x0000000009600000
(bootloader)  ADF parition size: 0x0000000000100000
(bootloader)  factory parition size: 0x0000000000900000
(bootloader)  nvm_static_calib parition size: 0x0000000000800000
(bootloader)  nvm_static_fix parition size: 0x0000000000100000
(bootloader)  nvm_dynamic parition size: 0x0000000000100000
(bootloader)  linux_nvm_fs parition size: 0x0000000000500000
(bootloader)  ===================================
(bootloader)  max-download-size: 0x3cc00000
all:
finished. total time: 0.261s

- Continue booting the device normally

sudo fastboot reboot

D. Upload IMG file to your device and enjoy :) . Your device is unlocked in less than a 5 minutes.
Note: You must reconnect the device again as in step B

sudo adb devices
sudo adb reboot fastboot
sudo fastboot boot "<path to your IMG file>/root-z170c_cg.img"

- Now device will reboot and you can install roo tcheck and Superuser applications.


Link to IMG file is given in XDA Developers site at the beginning of this text.

See ya.

Regards,
Z34PEC

P.S. If you can't download IMG file, please post here with your email and I will send it to you.
It is planned to attach it as a public file. PLease be patient.