Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
CAT - Control - Yet another post
|
Hi,?
I have been trying to connect my FT-847 to my RigPi. After a few unsuccessful attempts (many), I then tried to use flrig via a USB (CH340), CAT-847, FTBCAT and FTBASICMMO. In some cases, the 'CAT' symbol appeared on the rig, but the radio failed to connect. I've read the posts on the serial number saga and unfortunately my serial number is 4M950027.? Anyway, while trying out the programs above, I found something called CommsTester and this allowed me to 'see' the incoming data while tuning the rig.This is what is see: CommTest Version 1.1.8
Received FF00 on COM 5
Received 20FE00 on COM 5
Received 20FA00 on COM 5
Received 20FE00 on COM 5
Received 20FA00 on COM 5
Received 20F600 on COM 5
Received 20F200 on COM 5
Received 20EE00 on COM 5
Received 20EA00 on COM 5
Received 20E600 on COM 5
Received 20E200 on COM 5
I haven't been able to decode the data yet, but would this kind of patch work? See? See:?Mon Jun 9 23:09:52 CDT 2014 [CC-USB232?] Yaesu have just mentioned that they do not support the firmware update at present. Are there any other avenues open for me? Many thanks Ravi |
|
Douglas Richards
开云体育I know that this is an obvious question, but are you using a null modem cable to connect from the PC to radio? I've been using my Ft-847 for 2-3 years with a null modem cable on HRD and have had no problems. I let the computer boot up, turn on the radio, then open HRD. No problem. Good luck. Douglas VE3FFR On 2/9/2022 5:49 PM, Ravi Miranda
wrote:
Hi,? -- 73 Douglas Richards VE3FFR ve3ffr@... |
|
on6ab
Hi Ravi, What is there unfortunate about your serial number? As far as I can tell, your FT847 is a november 2004 model which makes it one of the last ones (2005) produced. 73, Bruno Op do 10 feb. 2022 om 00:04 schreef Ravi Miranda <ravimiranda@...>: Hi,? |
|
Hi, Douglas, Bruno
toggle quoted message
Show quoted text
I've used a Serial to USB cable to connect the rig to the Raspberry Pi and the laptop. In both cases, the 'CAT' comes up on the rig, but programs fail to complete the connection. The Serial number that I made reference to was from a post: "...Yaesu appears to use the following format for serial numbers on their amateur products: Year of manufacture-Month of manufacture-Production Run-Individual Unit number, where the month of manufacture is offset by 2, so "C" means January, "D" means February, "E" means March, and so forth. Example: 8G051234 = 1998, May (fifth month, or "G"), Production Run 05, unit #1234 in this run. One key serial number range is 8G05. This seems to be the point at which Yaesu had corrected the bi-directional CAT issue and made some other improvements. This version was made in May 1998. Later serial numbers (e.g., 8L09nnnn) all seem to have incorporated the earlier improvements plus new ones...." That would mean that the port was unidirectional prior to this, my serial number is "4M950027", hence I was wondering what data is that the rig was sending back to the CommsTest program when tuning across a band. Thanks. Ravi On Thu, 10 Feb 2022 at 00:45, on6ab <bruno.beckers@...> wrote:
--
I'm here to add more value to the world than I'm using up. |
|
on6ab
Hi Ravi, you are right about the serial number coding. Only, a number starting with a "4" is not older than one starting with an "8" as the production started in 1998 and "8" therefore was the first production year. So, the sequence is (199)8,(199)9,(200)0,(200)1,(200)2,(200)3,(200)4 and finally the year 2005. Maybe it is easier to first get the serial data working with a simple RS232 link to a normal PC running WSJT-X or something. If that works, you can tackle the RigPi problem with more confidence. Op do 10 feb. 2022 om 10:27 schreef Ravi Miranda <ravimiranda@...>: Hi, Douglas, Bruno |
|
I have been having trouble with CAT control as well, trying to use WSJT-X as well as JTDX. There are 2 selections within OmniRig that I can use - FT847 and FT847 (UNI) which I believe would stand for unidirectional. I can get the UNI setting to work, sending commands to the rig, but am unable to get the rig to send it's status back to the laptop.
I am about at my wits end, and will probably use a different rig with better CAT control... Micky K1XH |
|
Ian
I've been running JTDX with JTAlert and OMlog for so long that I can't recall whether Omnirig is used at all here, certainly not loaded as a seperate item. Attached is a screen capture of my JTDX Radio config page. All I get out of it is PTT and the reporting back of frequency, the 847 has really limited CAT functions, no S meter or such. 73 de Ian VK6CR |
开云体育Is your 847 one of the early ones, without the bi-directional serial capability?? That's why the UNI was created.? The symptoms suggest yours is an early model.There's a decoder table somewhere that lists what serial numbers are in which group, but I don't have it handy. Greg? KO6TH Micky Corrow via groups.io wrote:
I have been having trouble with CAT control as well, trying to use WSJT-X as well as JTDX. There are 2 selections within OmniRig that I can use - FT847 and FT847 (UNI) which I believe would stand for unidirectional. I can get the UNI setting to work, sending commands to the rig, but am unable to get the rig to send it's status back to the laptop. |
to navigate to use esc to dismiss