Date   

locked #Kenwood #WSJTX_config #Windows10 #FTDI #Kenwood #WSJTX_config #Windows10 #ftdi

mark.salvador@...
 

Hi Guys, I just bought a new xggcomms usb serial cable and was trying to make my old Kenwood ts-450s work with my laptop, but unfortunately it didnt work as easily as my xiegu with CE19.

Which documentation should i read and master before I can learn this kung fu?

Im still kinda new to hamlib so please be gentle :D also heres the debug that im trying to understand also seems like Im getting a unknown reply from the Rig.


---debug log ---

2021-11-25:23:08:25.165624: rigctld Hamlib 4.0~git
Last commit was Mon Jun 01 22:38:03 2020 +0000
2021-11-25:23:08:25.165624: Report bugs to <hamlib-developer@...>
 
2021-11-25:23:08:25.165624: rig_init called
2021-11-25:23:08:25.165624: initrigs4_kenwood called
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2012)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2013)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2001)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2025)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2003)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2004)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2016)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2024)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2005)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2007)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2009)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2010)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2022)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2014)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2030)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2021)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2029)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2043)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2044)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2045)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2047)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2038)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2002)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2011)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2006)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2008)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2015)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2026)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2017)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2033)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2042)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2020)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2023)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2027)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2034)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2031)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2039)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2037)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2028)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2019)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2032)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2036)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2048)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2040)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2041)
2021-11-25:23:08:25.165624: rig_register called
2021-11-25:23:08:25.165624: rig_register: rig_register (2046)
2021-11-25:23:08:25.165624: kenwood_init called, version 20200601/20200601.0
2021-11-25:23:08:25.165624: kenwood_init: if_len = 37
2021-11-25:23:08:25.165624: rig_open called
2021-11-25:23:08:25.165624: port_open called
2021-11-25:23:08:25.165624: serial_open called
2021-11-25:23:08:25.165624: serial_open: OPEN before
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
2021-11-25:23:08:25.675553: serial_open: OPEN after
2021-11-25:23:08:25.675553: serial_open: serial_setup before
2021-11-25:23:08:25.675553: serial_setup called
2021-11-25:23:08:25.675553: serial_setup: tcgetattr
2021-11-25:23:08:25.675553: serial_setup: cfsetispeed
2021-11-25:23:08:25.675553: serial_setup: cfsetospeed
2021-11-25:23:08:25.675553: serial_setup: tcsetattr TCSANOW
2021-11-25:23:08:25.675553: serial_open: serial_setup after
2021-11-25:23:08:25.675553: serial_open: serial_flush before
2021-11-25:23:08:25.675553: serial_flush called
2021-11-25:23:08:25.675553: serial_flush: tcflush
2021-11-25:23:08:25.675553: serial_open: serial_flush before
2021-11-25:23:08:25.675553: kenwood_open called
2021-11-25:23:08:25.675553: kenwood_get_id called
2021-11-25:23:08:25.675553: kenwood_transaction called
2021-11-25:23:08:25.675553: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.675553: serial_flush called
2021-11-25:23:08:25.675553: serial_flush: tcflush
2021-11-25:23:08:25.675553: write_block called
2021-11-25:23:08:25.691178: write_block(): TX 3 bytes
2021-11-25:23:08:25.691178: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.691178: read_string called
2021-11-25:23:08:25.722428: read_string(): RX 8 characters
2021-11-25:23:08:25.722428: 0000    f3 16 db be 67 d1 45 3b                             ....g.E;        
2021-11-25:23:08:25.722428: kenwood_transaction: read_string(len=8)='óÛ¾gÑE;'
2021-11-25:23:08:25.722428: kenwood_transaction: wrong reply ó for command ID
2021-11-25:23:08:25.722428: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.722428: serial_flush called
2021-11-25:23:08:25.722428: serial_flush: tcflush
2021-11-25:23:08:25.722428: write_block called
2021-11-25:23:08:25.738050: write_block(): TX 3 bytes
2021-11-25:23:08:25.738050: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.738050: read_string called
2021-11-25:23:08:25.738050: read_string(): RX 2 characters
2021-11-25:23:08:25.738050: 0000    45 3b                                               E;              
2021-11-25:23:08:25.738050: kenwood_transaction: read_string(len=2)='E;'
2021-11-25:23:08:25.738050: kenwood_transaction: Communication error for 'ID'
2021-11-25:23:08:25.738050: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.738050: serial_flush called
2021-11-25:23:08:25.738050: serial_flush: tcflush
2021-11-25:23:08:25.738050: write_block called
2021-11-25:23:08:25.753676: write_block(): TX 3 bytes
2021-11-25:23:08:25.753676: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.753676: read_string called
2021-11-25:23:08:25.753676: read_string(): RX 1 characters
2021-11-25:23:08:25.753676: 0000    3b                                                  ;               
2021-11-25:23:08:25.753676: kenwood_transaction: read_string(len=1)=';'
2021-11-25:23:08:25.753676: kenwood_transaction: wrong reply ;  for command ID
2021-11-25:23:08:25.753676: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.753676: serial_flush called
2021-11-25:23:08:25.753676: serial_flush: tcflush
2021-11-25:23:08:25.753676: write_block called
2021-11-25:23:08:25.769294: write_block(): TX 3 bytes
2021-11-25:23:08:25.769294: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.769294: read_string called
2021-11-25:23:08:25.769294: read_string(): RX 2 characters
2021-11-25:23:08:25.769294: 0000    45 3b                                               E;              
2021-11-25:23:08:25.769294: kenwood_transaction: read_string(len=2)='E;'
2021-11-25:23:08:25.769294: kenwood_transaction: Communication error for 'ID'
2021-11-25:23:08:25.769294: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.769294: serial_flush called
2021-11-25:23:08:25.769294: serial_flush: tcflush
2021-11-25:23:08:25.769294: write_block called
2021-11-25:23:08:25.784919: write_block(): TX 3 bytes
2021-11-25:23:08:25.784919: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.784919: read_string called
2021-11-25:23:08:25.784919: read_string(): RX 3 characters
2021-11-25:23:08:25.784919: 0000    45 45 3b                                            EE;             
2021-11-25:23:08:25.784919: kenwood_transaction: read_string(len=3)='EE;'
2021-11-25:23:08:25.784919: kenwood_transaction: wrong reply EE for command ID
2021-11-25:23:08:25.784919: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.784919: serial_flush called
2021-11-25:23:08:25.784919: serial_flush: tcflush
2021-11-25:23:08:25.784919: write_block called
2021-11-25:23:08:25.800543: write_block(): TX 3 bytes
2021-11-25:23:08:25.800543: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.800543: read_string called
2021-11-25:23:08:25.800543: read_string(): RX 1 characters
2021-11-25:23:08:25.800543: 0000    3b                                                  ;               
2021-11-25:23:08:25.800543: kenwood_transaction: read_string(len=1)=';'
2021-11-25:23:08:25.800543: kenwood_transaction: wrong reply ;  for command ID
2021-11-25:23:08:25.800543: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.800543: serial_flush called
2021-11-25:23:08:25.800543: serial_flush: tcflush
2021-11-25:23:08:25.800543: write_block called
2021-11-25:23:08:25.816170: write_block(): TX 3 bytes
2021-11-25:23:08:25.816170: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.816170: read_string called
2021-11-25:23:08:25.816170: read_string(): RX 2 characters
2021-11-25:23:08:25.816170: 0000    45 3b                                               E;              
2021-11-25:23:08:25.816170: kenwood_transaction: read_string(len=2)='E;'
2021-11-25:23:08:25.816170: kenwood_transaction: Communication error for 'ID'
2021-11-25:23:08:25.816170: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.816170: serial_flush called
2021-11-25:23:08:25.816170: serial_flush: tcflush
2021-11-25:23:08:25.816170: write_block called
2021-11-25:23:08:25.831791: write_block(): TX 3 bytes
2021-11-25:23:08:25.831791: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.831791: read_string called
2021-11-25:23:08:25.831791: read_string(): RX 1 characters
2021-11-25:23:08:25.831791: 0000    3b                                                  ;               
2021-11-25:23:08:25.831791: kenwood_transaction: read_string(len=1)=';'
2021-11-25:23:08:25.831791: kenwood_transaction: wrong reply ;  for command ID
2021-11-25:23:08:25.831791: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.831791: serial_flush called
2021-11-25:23:08:25.831791: serial_flush: tcflush
2021-11-25:23:08:25.831791: write_block called
2021-11-25:23:08:25.847419: write_block(): TX 3 bytes
2021-11-25:23:08:25.847419: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.847419: read_string called
2021-11-25:23:08:25.847419: read_string(): RX 1 characters
2021-11-25:23:08:25.847419: 0000    3b                                                  ;               
2021-11-25:23:08:25.847419: kenwood_transaction: read_string(len=1)=';'
2021-11-25:23:08:25.847419: kenwood_transaction: wrong reply ;  for command ID
2021-11-25:23:08:25.847419: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.847419: serial_flush called
2021-11-25:23:08:25.847419: serial_flush: tcflush
2021-11-25:23:08:25.847419: write_block called
2021-11-25:23:08:25.863044: write_block(): TX 3 bytes
2021-11-25:23:08:25.863044: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.863044: read_string called
2021-11-25:23:08:25.863044: read_string(): RX 3 characters
2021-11-25:23:08:25.863044: 0000    45 45 3b                                            EE;             
2021-11-25:23:08:25.863044: kenwood_transaction: read_string(len=3)='EE;'
2021-11-25:23:08:25.863044: kenwood_transaction: wrong reply EE for command ID
2021-11-25:23:08:25.863044: kenwood_transaction: cmdstr = ID
2021-11-25:23:08:25.863044: serial_flush called
2021-11-25:23:08:25.863044: serial_flush: tcflush
2021-11-25:23:08:25.863044: write_block called
2021-11-25:23:08:25.878663: write_block(): TX 3 bytes
2021-11-25:23:08:25.878663: 0000    49 44 3b                                            ID;             
2021-11-25:23:08:25.878663: read_string called
2021-11-25:23:08:25.878663: read_string(): RX 1 characters
2021-11-25:23:08:25.878663: 0000    3b                                                  ;               
2021-11-25:23:08:25.878663: kenwood_transaction: read_string(len=1)=';'
2021-11-25:23:08:25.878663: kenwood_transaction: wrong reply ;  for command ID
2021-11-25:23:08:25.878663: kenwood_transaction: returning retval=-8
2021-11-25:23:08:25.878663: kenwood_open: cannot get identification
rig_open: error = Protocol error 

-- EOF--

thanks in advance for the help!


locked Re: #raspberryPi #install #raspberryPi #install

William Smith
 

The major advantage AFAICT of installing hamlib separately is that it can be upgraded separately, adding additional features before they make it into the hamlib-embedded-into-wsjt. 

Personal preference, I guess. 

73, Willie N1JBJ


On Nov 25, 2021, at 5:29 PM, Richard Hattaway via groups.io <rhattaway@...> wrote:

Edd,

As a guy that runs his entire shack on a Pi 4B, I find the thread fascinating.

I've built the WSJT-X from source, just to see if I could do it.  I am not a software engineer, but I have found that google is my friend also, and almost all Raspberry Pi questions can be answered there, if I can ask it correctly HI HI.  Your speedbumps with the new OS interest me, as I will be doing that soon myself.
--
73
Dick

W4PID@...





locked Re: #raspberryPi #install #raspberryPi #install

Richard Hattaway
 

Edd,

As a guy that runs his entire shack on a Pi 4B, I find the thread fascinating.

I've built the WSJT-X from source, just to see if I could do it.  I am not a software engineer, but I have found that google is my friend also, and almost all Raspberry Pi questions can be answered there, if I can ask it correctly HI HI.  Your speedbumps with the new OS interest me, as I will be doing that soon myself.
--
73
Dick

W4PID@...


locked Re: #raspberryPi #install #raspberryPi #install

Gary trock
 

Sorry, meant W8MDB


On Nov 25, 2021, at 12:53 PM, Gary trock <gtrockmd@...> wrote:

 Thanks. Very helpful. I’ve been thinking about starting with an Arduino kit. I’m only up and running after much help from W9MJB


On Nov 25, 2021, at 12:50 PM, jbozell via groups.io <jbozell@...> wrote:



Hi Gary,

 

Don’t feel bad...I understand where you’re coming from. I in no way am intending anything derogatory to the Raspberry Pi users here (and there’s a lot of them), but those that want to install the Linux version of WSJT-X will likely have a strong parallel interest in digging into the code and during installation, using the specialized language of Linux for installation and communication with their computers. G4WJS and W9MDB are a couple of the true experts in that area and regularly answer the really arcane questions about its operation. I know enough Linux to be dangerous, and that’s why I like my Mac and use the Mac version of WSJT-X. It installed easily, and has operated pretty flawlessly with my IC-7610. Yes, I’m doing it in kind of a “black box” mode, but have a rough idea of how it works by reading the QST and QEX papers by K1JT. IMHO, the papers do a good job describing what WSJT-X does, although I’d prefer more on how it does it.

 

In any case, to your original question about reading opportunities, I’ve seen some good reviews on the Dr. Duino electronics kit as advertised in QST (https://www.drduino.com/blogs/news/tagged/ham-radio). It combines hands on project building with the coding that can be used for computer control. It might be one place to start as it’s pretty reasonably priced.

 

Just a few suggestions...hope this helps.

 

Joe/WB0CDY

 








locked Re: #raspberryPi #install #raspberryPi #install

Gary trock
 

Thanks. Very helpful. I’ve been thinking about starting with an Arduino kit. I’m only up and running after much help from W9MJB


On Nov 25, 2021, at 12:50 PM, jbozell via groups.io <jbozell@...> wrote:



Hi Gary,

 

Don’t feel bad...I understand where you’re coming from. I in no way am intending anything derogatory to the Raspberry Pi users here (and there’s a lot of them), but those that want to install the Linux version of WSJT-X will likely have a strong parallel interest in digging into the code and during installation, using the specialized language of Linux for installation and communication with their computers. G4WJS and W9MDB are a couple of the true experts in that area and regularly answer the really arcane questions about its operation. I know enough Linux to be dangerous, and that’s why I like my Mac and use the Mac version of WSJT-X. It installed easily, and has operated pretty flawlessly with my IC-7610. Yes, I’m doing it in kind of a “black box” mode, but have a rough idea of how it works by reading the QST and QEX papers by K1JT. IMHO, the papers do a good job describing what WSJT-X does, although I’d prefer more on how it does it.

 

In any case, to your original question about reading opportunities, I’ve seen some good reviews on the Dr. Duino electronics kit as advertised in QST (https://www.drduino.com/blogs/news/tagged/ham-radio). It combines hands on project building with the coding that can be used for computer control. It might be one place to start as it’s pretty reasonably priced.

 

Just a few suggestions...hope this helps.

 

Joe/WB0CDY

 





locked Re: #raspberryPi #install #raspberryPi #install

jbozell
 

Hi Gary,

 

Don’t feel bad...I understand where you’re coming from. I in no way am intending anything derogatory to the Raspberry Pi users here (and there’s a lot of them), but those that want to install the Linux version of WSJT-X will likely have a strong parallel interest in digging into the code and during installation, using the specialized language of Linux for installation and communication with their computers. G4WJS and W9MDB are a couple of the true experts in that area and regularly answer the really arcane questions about its operation. I know enough Linux to be dangerous, and that’s why I like my Mac and use the Mac version of WSJT-X. It installed easily, and has operated pretty flawlessly with my IC-7610. Yes, I’m doing it in kind of a “black box” mode, but have a rough idea of how it works by reading the QST and QEX papers by K1JT. IMHO, the papers do a good job describing what WSJT-X does, although I’d prefer more on how it does it.

 

In any case, to your original question about reading opportunities, I’ve seen some good reviews on the Dr. Duino electronics kit as advertised in QST (https://www.drduino.com/blogs/news/tagged/ham-radio). It combines hands on project building with the coding that can be used for computer control. It might be one place to start as it’s pretty reasonably priced.

 

Just a few suggestions...hope this helps.

 

Joe/WB0CDY

 


locked Re: TCI-Client for Sun SDR #Cat_RigControl

Randy Diddel
 

Hi Bill,

I am a Mac user. I use MacLoggerDX. I have to set up operation as outlined here: https://dogparksoftware.com/MacLoggerDX%20Help/sunsdr_wsjt-x.html

It works, but is a little to Rube Goldberg-like for my taste. Ideally, having the radio run 100% as the source for all band, mode data, etc. would be great instead of relying on a loopback audio driver and the logging software to all be good. 

I would be open to help test on the Mac.

73
--
Randy Diddel
K5RHD
DM79ku
Arvada, CO


locked Re: TCI-Client for Sun SDR #Cat_RigControl

Charlie Morrison
 

Hi Mike

 

I would need either. TCI 1.5 is current with ExpertSDR V2, 1.6 is required for V3

 

73, Charlie GI4FUE

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Michael Black via groups.io
Sent: 25 November 2021 15:50
To: main@wsjtx.groups.io
Subject: Re: [WSJTX] TCI-Client for Sun SDR #Cat_RigControl

 

I need volunteers who have the need for TCI 1.5 and one for TCI 1.6

Does anybody need TCI 1.4?

 

I don't yet what the difference is but apparently JTDX's implementation only works on 1.5.

 

I'm going to add it to hamlib so you'll be able to download the new DLL to get it.

 

Mike W9MDB

 

 

 

 

On Thursday, November 25, 2021, 09:43:04 AM CST, Randy Diddel <k5rhd.73@...> wrote:

 

 

Add me to the list that would like to see TCI added at least for CAT-type control. I am good with using VAC for now although it would be nice to have it all rolled together.
--
Randy Diddel
K5RHD
DM79ku
Arvada, CO




locked Re: TCI-Client for Sun SDR #Cat_RigControl

Michael Black
 

Hi Ronald,

Are you on Windows?

I'm starting to make the TCI interface and need a tester.

Mike W9MDB




On Wednesday, November 24, 2021, 02:19:57 PM CST, PH7R - Ronald <rpmeier.ned@...> wrote:


Same +1




locked Re: #raspberryPi #install #raspberryPi #install

Gary trock
 

I am interested in ALL these discussions on this group. I’m hoping to better understand most of it in the future.
Gary


On Nov 25, 2021, at 8:44 AM, Edward Seeliger <eseeliger@...> wrote:



[Edited Message Follows]

Good morning again Bill.
Yes, using apt to install cmake worked.
I moved the package from the RPI 4 to the RPI Zero using a memory stick (had not occurred to me that they can be read by the RPI OS when I previously used it on Windows machines).
wsjtx is now installed on the RPI Zero W2 and opens without errors - it even has the wsjtx icon installed.

Gary, I am not a software professional but a mere ham who likes to tinker. To learn more just use your search engine of choice - you can eventually find answers to most of your questions about Linux, Raspian OS, Debian, Windows operating systems as you need. And sometimes there is someone like Bill who can provide the snippet of guidance to push you forward.

I apologize to those who found this thread not of interest in this forum, but maybe someone else trying to build wsjtx on the RPI Zero want use his time as I have.

Happy Thanksgiving to those in the US.
Bill, again, thanks for your help and all you and the team have done in perfecting wsjtx for us weak signal hams!

Edd - KD5M



locked Re: #raspberryPi #install #raspberryPi #install

Edward Seeliger
 
Edited

Good morning again Bill.
Yes, using apt to install cmake worked.
I moved the package from the RPI 4 to the RPI Zero using a memory stick (had not occurred to me that they can be read by the RPI OS when I previously used it on Windows machines).
wsjtx is now installed on the RPI Zero W2 and opens without errors - it even has the wsjtx icon installed.

Gary, I am not a software professional but a mere ham who likes to tinker. To learn more just use your search engine of choice - you can eventually find answers to most of your questions about Linux, Raspian OS, Debian, Windows operating systems as you need. And sometimes there is someone like Bill who can provide the snippet of guidance to push you forward.

I apologize to those who found this thread not of interest in this forum, but maybe someone else trying to build wsjtx on the RPI Zero want use his time as I have.

Happy Thanksgiving to those in the US.
Bill, again, thanks for your help and all you and the team have done in perfecting wsjtx for us weak signal hams!

Edd - KD5M


locked Re: #raspberryPi #install #raspberryPi #install

Gary trock
 

No current issues but I don’t understand most of this. 


On Nov 25, 2021, at 8:31 AM, Bill Somerville <g4wjs@...> wrote:


Gary,

Edd is trying to install WSJT-X on a Raspberry Pi Zero 2 W board. He can't use the Debian package we provide because he has installed a later version of Raspberry Pi OS on his board which means he needs to to compile WSJT-X from sources. He can't do that on the target board because it has insufficient RAM to complete the build. He is able to build on another Raspberry Pi with more resources and then should be able to build a Debian package that he can transfer to the target board and install.

If any of that is relevant to you then let us know what issues you have?

73
Bill
G4WJS.

On 25/11/2021 16:25, Gary trock wrote:
Pardon my ignorance. These discussions are so far above me. Are many of you software professionals or can you point out to me reading to help me better understand?
Gary N8GT


On Nov 25, 2021, at 8:17 AM, Bill Somerville <g4wjs@...> wrote:


On 25/11/2021 16:10, Edward Seeliger wrote:
Good morning Bill
sudo -E cmake .... didn't work. I also tried to install cmake on a fresh OS Bullseye image using the sh script as described on the cmake site - that didn't seem to work either.
On my RPI 4B 4GB I started with a clean RPI OS Bullseye again, installed all the prerequisites from the INSTALL recipe using APT package manager including cmake and built the install and package versions following the recipe. It all works as it should.
Thanks for your help.
Yes, my original goal was to build and install on the RPI Zero W2. Now I must learn how to move the wsjtx package version from one RPI to another.
There is always something else to learn.
Have a nice weekend.
Edd - KD5M

Edd,

have you tried installing the default cmake package from the Raspberry Pi OS repository?

sudo apt install cmake

73
Bill
G4WJS.






locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

Gary,

Edd is trying to install WSJT-X on a Raspberry Pi Zero 2 W board. He can't use the Debian package we provide because he has installed a later version of Raspberry Pi OS on his board which means he needs to to compile WSJT-X from sources. He can't do that on the target board because it has insufficient RAM to complete the build. He is able to build on another Raspberry Pi with more resources and then should be able to build a Debian package that he can transfer to the target board and install.

If any of that is relevant to you then let us know what issues you have?

73
Bill
G4WJS.

On 25/11/2021 16:25, Gary trock wrote:
Pardon my ignorance. These discussions are so far above me. Are many of you software professionals or can you point out to me reading to help me better understand?
Gary N8GT


On Nov 25, 2021, at 8:17 AM, Bill Somerville <g4wjs@...> wrote:


On 25/11/2021 16:10, Edward Seeliger wrote:
Good morning Bill
sudo -E cmake .... didn't work. I also tried to install cmake on a fresh OS Bullseye image using the sh script as described on the cmake site - that didn't seem to work either.
On my RPI 4B 4GB I started with a clean RPI OS Bullseye again, installed all the prerequisites from the INSTALL recipe using APT package manager including cmake and built the install and package versions following the recipe. It all works as it should.
Thanks for your help.
Yes, my original goal was to build and install on the RPI Zero W2. Now I must learn how to move the wsjtx package version from one RPI to another.
There is always something else to learn.
Have a nice weekend.
Edd - KD5M

Edd,

have you tried installing the default cmake package from the Raspberry Pi OS repository?

sudo apt install cmake

73
Bill
G4WJS.



locked Re: #raspberryPi #install #raspberryPi #install

Gary trock
 

Pardon my ignorance. These discussions are so far above me. Are many of you software professionals or can you point out to me reading to help me better understand?
Gary N8GT


On Nov 25, 2021, at 8:17 AM, Bill Somerville <g4wjs@...> wrote:


On 25/11/2021 16:10, Edward Seeliger wrote:
Good morning Bill
sudo -E cmake .... didn't work. I also tried to install cmake on a fresh OS Bullseye image using the sh script as described on the cmake site - that didn't seem to work either.
On my RPI 4B 4GB I started with a clean RPI OS Bullseye again, installed all the prerequisites from the INSTALL recipe using APT package manager including cmake and built the install and package versions following the recipe. It all works as it should.
Thanks for your help.
Yes, my original goal was to build and install on the RPI Zero W2. Now I must learn how to move the wsjtx package version from one RPI to another.
There is always something else to learn.
Have a nice weekend.
Edd - KD5M

Edd,

have you tried installing the default cmake package from the Raspberry Pi OS repository?

sudo apt install cmake

73
Bill
G4WJS.





locked Re: #raspberryPi #install #raspberryPi #install

Bill Somerville
 

On 25/11/2021 16:10, Edward Seeliger wrote:
Good morning Bill
sudo -E cmake .... didn't work. I also tried to install cmake on a fresh OS Bullseye image using the sh script as described on the cmake site - that didn't seem to work either.
On my RPI 4B 4GB I started with a clean RPI OS Bullseye again, installed all the prerequisites from the INSTALL recipe using APT package manager including cmake and built the install and package versions following the recipe. It all works as it should.
Thanks for your help.
Yes, my original goal was to build and install on the RPI Zero W2. Now I must learn how to move the wsjtx package version from one RPI to another.
There is always something else to learn.
Have a nice weekend.
Edd - KD5M

Edd,

have you tried installing the default cmake package from the Raspberry Pi OS repository?

sudo apt install cmake

73
Bill
G4WJS.


locked Re: TCI-Client for Sun SDR #Cat_RigControl

Bill Somerville
 

On 25/11/2021 15:42, Randy Diddel wrote:
Add me to the list that would like to see TCI added at least for CAT-type control. I am good with using VAC for now although it would be nice to have it all rolled together.
--
Randy Diddel
K5RHD
DM79ku
Arvada, CO
Hi Andy,

can you detail what issues exist with using the ExpertSDR TS-480 emulation for CAT control please?

73
Bill
G4WJS.


locked Re: #raspberryPi #install #raspberryPi #install

Edward Seeliger
 

Good morning Bill
sudo -E cmake .... didn't work. I also tried to install cmake on a fresh OS Bullseye image using the sh script as described on the cmake site - that didn't seem to work either.
On my RPI 4B 4GB I started with a clean RPI OS Bullseye again, installed all the prerequisites from the INSTALL recipe using APT package manager including cmake and built the install and package versions following the recipe. It all works as it should.
Thanks for your help.
Yes, my original goal was to build and install on the RPI Zero W2. Now I must learn how to move the wsjtx package version from one RPI to another.
There is always something else to learn.
Have a nice weekend.
Edd - KD5M


locked Re: TCI-Client for Sun SDR #Cat_RigControl

Michael Black
 

I need volunteers who have the need for TCI 1.5 and one for TCI 1.6
Does anybody need TCI 1.4?

I don't yet what the difference is but apparently JTDX's implementation only works on 1.5.

I'm going to add it to hamlib so you'll be able to download the new DLL to get it.

Mike W9MDB




On Thursday, November 25, 2021, 09:43:04 AM CST, Randy Diddel <k5rhd.73@...> wrote:


Add me to the list that would like to see TCI added at least for CAT-type control. I am good with using VAC for now although it would be nice to have it all rolled together.
--
Randy Diddel
K5RHD
DM79ku
Arvada, CO




locked Re: TCI-Client for Sun SDR #Cat_RigControl

Randy Diddel
 

Add me to the list that would like to see TCI added at least for CAT-type control. I am good with using VAC for now although it would be nice to have it all rolled together.
--
Randy Diddel
K5RHD
DM79ku
Arvada, CO


locked Re: #Kenwood #Cat_RigControl #IssueReport #Kenwood #Cat_RigControl #IssueReport

mark.salvador@...
 

Hi Chris, can I ask for your configuration and settings? what OS are you using? What cable is it an FTDI?

I tried rolling back to ver 2.2 but still doesnt work on my laptop. Om using the xggcomms cable. seems that the laptop to rog has connectivity its just that im getting protocol errors.

thanks in advance for your insights and reply. 

1241 - 1260 of 31319