K3S USB port
Locked
 
|
First off, this is NOT a complaint, merely an observation. and in my
opinion, worthy of note for the programmers to check out. I didn't think this was supposed to work but it seems to work quite well, at least in my case. I am using serial RS-232 with the following cabling - Desktop COM-1 to P3, P3 to K3S using the DE-9 to RJ-45 adapter (not the two headed cable between the P3 and K3S) from my desktop computer. I am also running the USB port cable to a Raspberry Pi model 2, single board Linux computer with the K3S configured as the USB Audio Codecs AND serial comms using /devttyUSB0 for rig control with VOX for PTT, in FLDIGI on the Raspberry Pi. All serial speeds are set to 38.4K baud. The P3 still indicates the K3S frequency as I tune (slight delay), FLDIGI on the Pi 2 indicates the K3S frequency as I tune. TX/RX audio from and to FLDIGI on the Pi 2 work properly, and I am able to make contacts with no problem as well. I can also tune the K3S using FLDIGI's frequency control. I am using N3FJP's AC Log program on the big desktop computer for logging and it also displays the proper band/mode from the K3S. It also follows frequency changes made by the FLDIGI program on the Pi 2. I did not attempt to configure DTR or RTS for push to talk as VOX works so well. It was my original understanding that you couldn't do this (RS-232 using the RJ-45 jack AND the USB port simultaneously). I DO have the K3S RS-232 configured to USB in the menu. The difference may be due to the fact that I'm using two separate computers here with both talking/listening to the K3S. I'm running FW version UC 5.46, DSP 1 and 2 version 2.86, FL version 1.25 on the K3S and MCU 1.57, SVGA 1.31 and the FPGA's 1.04 in the P3. DISCLAIMER: If anyone else tries this, make sure to SAVE YOUR CONFIGURATION prior to making any changes so you won't forget what they were before and if something messes up you can re-load the previous version. Jim Sheldon, W0EB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
Hi Jim,
It's my understanding that the RS232 port is live for serial data out from the K3 (RXD) but not for serial data in (TXD). Have you tried to use the K3 Utility with your set up? That would require bidirectional serial data and in theory shouldn't work. Cheers, Fred KE7X ________________________________________ From: Elecraft <[hidden email]> on behalf of Jim Sheldon <[hidden email]> Sent: Thursday, March 3, 2016 10:48 AM To: Elecraft Mailing List Subject: [Elecraft] K3S USB port First off, this is NOT a complaint, merely an observation. and in my opinion, worthy of note for the programmers to check out. I didn't think this was supposed to work but it seems to work quite well, at least in my case. I am using serial RS-232 with the following cabling - Desktop COM-1 to P3, P3 to K3S using the DE-9 to RJ-45 adapter (not the two headed cable between the P3 and K3S) from my desktop computer. I am also running the USB port cable to a Raspberry Pi model 2, single board Linux computer with the K3S configured as the USB Audio Codecs AND serial comms using /devttyUSB0 for rig control with VOX for PTT, in FLDIGI on the Raspberry Pi. All serial speeds are set to 38.4K baud. The P3 still indicates the K3S frequency as I tune (slight delay), FLDIGI on the Pi 2 indicates the K3S frequency as I tune. TX/RX audio from and to FLDIGI on the Pi 2 work properly, and I am able to make contacts with no problem as well. I can also tune the K3S using FLDIGI's frequency control. I am using N3FJP's AC Log program on the big desktop computer for logging and it also displays the proper band/mode from the K3S. It also follows frequency changes made by the FLDIGI program on the Pi 2. I did not attempt to configure DTR or RTS for push to talk as VOX works so well. It was my original understanding that you couldn't do this (RS-232 using the RJ-45 jack AND the USB port simultaneously). I DO have the K3S RS-232 configured to USB in the menu. The difference may be due to the fact that I'm using two separate computers here with both talking/listening to the K3S. I'm running FW version UC 5.46, DSP 1 and 2 version 2.86, FL version 1.25 on the K3S and MCU 1.57, SVGA 1.31 and the FPGA's 1.04 in the P3. DISCLAIMER: If anyone else tries this, make sure to SAVE YOUR CONFIGURATION prior to making any changes so you won't forget what they were before and if something messes up you can re-load the previous version. Jim Sheldon, W0EB --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
On the K3, the serial port is perfect - for use with either a real
serial port or a USB adapter. I prefer going direct to a real serial port, without any adapter. Is the USB in the K3S merely a built-in adapter? That would eliminate a problem some ops have had with external adapters (Prolific??). Bill W2BLC K-Line ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
|
In reply to this post by Cady, Fred-2
Hi Fred,
Not the K3 utility, but I did have the P3 utility running simultaneously for a time and it seemed to work just fine. It connected and pulled in the FW versions I was looking for. I did find what was giving the P3 it's information and the reason it had a slight update delay. Turns out that FLDIGI on the Raspberry Pi 2 was echoing the serial information via /devttyUSB0 from the Pi and that was getting sent back to the P3 over the K3S's RS-232 on the RJ-45 connection. After I shut down FLDIGI on the Pi, the updates stopped and the P3 no longer changed the displayed frequency as the K3S was tuned. As soon as I restarted FLDIGI on the Pi 2, it went back to updating as the K3S changed frequency (with a slight delay) and almost instantly if the point and click controls in FLDIGI were used to change frequency. I understand what's happening now and it seems to be only with the Pi 2 and FLDIGI that it works this way. Could prove to be useful, but I don't plan to rely on it - LOL. Jim ------ Original Message ------ From: "Cady, Fred" <[hidden email]> To: "Elecraft Mailing List" <[hidden email]>; "Jim Sheldon" <[hidden email]> Sent: 3/3/2016 1:56:03 PM Subject: Re: [Elecraft] K3S USB port >Hi Jim, >It's my understanding that the RS232 port is live for serial data out >from the K3 (RXD) but not for serial data in (TXD). >Have you tried to use the K3 Utility with your set up? That would >require bidirectional serial data and in theory shouldn't work. >Cheers, >Fred KE7X > > >________________________________________ >From: Elecraft <[hidden email]> on behalf of Jim >Sheldon <[hidden email]> >Sent: Thursday, March 3, 2016 10:48 AM >To: Elecraft Mailing List >Subject: [Elecraft] K3S USB port > >First off, this is NOT a complaint, merely an observation. and in my >opinion, worthy of note for the programmers to check out. I didn't >think this was supposed to work but it seems to work quite well, at >least in my case. > >I am using serial RS-232 with the following cabling - Desktop COM-1 to >P3, P3 to K3S using the DE-9 to RJ-45 adapter (not the two headed cable >between the P3 and K3S) from my desktop computer. I am also running >the >USB port cable to a Raspberry Pi model 2, single board Linux computer >with the K3S configured as the USB Audio Codecs AND serial comms using >/devttyUSB0 for rig control with VOX for PTT, in FLDIGI on the >Raspberry >Pi. All serial speeds are set to 38.4K baud. > >The P3 still indicates the K3S frequency as I tune (slight delay), >FLDIGI on the Pi 2 indicates the K3S frequency as I tune. TX/RX audio >from and to FLDIGI on the Pi 2 work properly, and I am able to make >contacts with no problem as well. I can also tune the K3S using >FLDIGI's frequency control. I am using N3FJP's AC Log program on the >big desktop computer for logging and it also displays the proper >band/mode from the K3S. It also follows frequency changes made by the >FLDIGI program on the Pi 2. I did not attempt to configure DTR or RTS >for push to talk as VOX works so well. > >It was my original understanding that you couldn't do this (RS-232 >using >the RJ-45 jack AND the USB port simultaneously). I DO have the K3S >RS-232 configured to USB in the menu. The difference may be due to the >fact that I'm using two separate computers here with both >talking/listening to the K3S. > >I'm running FW version UC 5.46, DSP 1 and 2 version 2.86, FL version >1.25 on the K3S and MCU 1.57, SVGA 1.31 and the FPGA's 1.04 in the P3. > >DISCLAIMER: If anyone else tries this, make sure to SAVE YOUR >CONFIGURATION prior to making any changes so you won't forget what they >were before and if something messes up you can re-load the previous >version. > > >Jim Sheldon, W0EB > > > > >--- >This email has been checked for viruses by Avast antivirus software. >https://www.avast.com/antivirus >______________________________________________________________ >Elecraft mailing list >Home: http://mailman.qth.net/mailman/listinfo/elecraft >Help: http://mailman.qth.net/mmfaq.htm >Post: mailto:[hidden email] > >This list hosted by: http://www.qsl.net >Please help support this email list: http://www.qsl.net/donate.html >Message delivered to [hidden email] > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
«
Return to Elecraft
|
1 view|%1 views
| Free forum by Nabble | Edit this page |