Date   

Re: Band Stacking Registers; CI-V Commands

VE2DX
 

Heres a few comments;
Mode poll Rx : FE FE 98 E0 26 01 FD (This is from the Application E0)  FE FE E0 98 26 01 00 00 02 FD  (Response back from the radio 98, with 01 00 00 02 as the DATA meaning 01 = Sub 00= LSB 00= Data mode OFF and 02= Filter is set to Filter 2
Poll Split : FE FE 98 E0 0F FD This seems to be missing a response???
Split Rx : FE FE 98 E0 0F FD You see this one is complete, why was there another above???) FE FE E0 98 0F 00 FD  and this is the proper response, the split is OFF
Direct Radio Hex Command : FE FE 98 E0 1A 01 03 02 FD Here you are asking the 7610 on 40m to select stack 2 but again I am missing a response from the radio??? radio response would start with FE FE E0 98
Poll main VFO : FE FE 98 E0 25 00 FD Agreed?
VFO poll Rx : FE FE 98 E0 25 00 FD Why are you sending it twice? this is wrong? FE FE E0 98 25 00 00 00 13 07 00 FD and a proper response from the 7610
Poll sub VFO : FE FE 98 E0 25 01 FD Agreed but no respons?
All I can think of here is that the confusion over the missing responses would be caused by the ECHO mode in your CI-V settings, are using the USB port or the CI-V (Remote port on the back of the 7610 and pls describe the setup for these recording how were they made?

Back to the Stack issue, the radio never respond to the command, I am thinking of a timing issue possible there is some confusionon the recordings, but at least the other commands were responded to, I am thinking of a possible timming issue or collisions you may want to had (too mutch) delay between the commands to see if the radio reacts and then adjust the timming between commands.

Hope this helps (and without any sales pitch :-D )

73

Richard VE2DX



 
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: Band Stacking Registers; CI-V Commands

JOHN MUNTON G7SSE
 

Hi Richard, thanks for your reply.

Got to admit I'm a bit of a novice with the CI-V commands.

I just figure out them out from the 7610 manual and set up the controls in my logging software (Logger32) with them.
Up until now all that I've tried have worked.
It might even be that the Band stacking commands are not supported by Logger32 ??

Here is an extract, if it helps, of the communication from Logger32 to my 7610 showing one of the commands being sent;

Mode poll Rx : FE FE 98 E0 26 01 FD FE FE E0 98 26 01 00 00 02 FD
Poll Split : FE FE 98 E0 0F FD
Split Rx : FE FE 98 E0 0F FD FE FE E0 98 0F 00 FD
Direct Radio Hex Command : FE FE 98 E0 1A 01 03 02 FD
Poll main VFO : FE FE 98 E0 25 00 FD
VFO poll Rx : FE FE 98 E0 25 00 FD FE FE E0 98 25 00 00 00 13 07 00 FD
Poll sub VFO : FE FE 98 E0 25 01 FD 

Oh, and FB regarding the sales pitch :-)

73
John - G7SSE

------ Original Message ------
From: "VE2DX" <ve2dx@...>
Sent: 27/04/2020 15:47:39
Subject: Re: [CIV] Band Stacking Registers; CI-V Commands

OK, when you do what response does the 7610 send back have you got a sniffer online?

That data would really help! if you dont have one look at HHD Device Monitoring studio freeware (for 20 minutes sessions thats plenty!) you may have to either use a virtual port or even easier simple install another usb ftdi port on your CI-V bus (wiat for it sales pitch coming! :-P ) or use a CT-17B :-D (sorry could not hold myself back!

do you get a FA or FB or what else?

73

Richard VE2DX
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: Band Stacking Registers; CI-V Commands

VE2DX
 

OK, when you do what response does the 7610 send back have you got a sniffer online?

That data would really help! if you dont have one look at HHD Device Monitoring studio freeware (for 20 minutes sessions thats plenty!) you may have to either use a virtual port or even easier simple install another usb ftdi port on your CI-V bus (wiat for it sales pitch coming! :-P ) or use a CT-17B :-D (sorry could not hold myself back!

do you get a FA or FB or what else?

73

Richard VE2DX
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Band Stacking Registers; CI-V Commands

JOHN MUNTON G7SSE
 

Hi Group

Trying to get commands for the Band Stacking Registers working with my IC-7610 so as to switch between them using programable "buttons" in my logging software.
Not having any joy however.

These are what I've tried for the 40m band;

$hexcommand FE FE 98 E0 1A 01 03 01 FD$     (latest)
 
$hexcommand FE FE 98 E0 1A 01 03 02 FD$        2
 
$hexcommand FE FE 98 E0 1A 01 03 03 FD$     (oldest)

Any insights appreciated.

73
John - G7SSE


IMK1 2 and 3,hints of things to come...

VE2DX
 

Here we go, totaly rethinking IMK1 and added IMK2 and IMK3.  they will be CI-V based memory keypads in 3 variations.

This small video will show you the diretion I am going... NOT!

https://www.youtube.com/watch?v=RwP_Miw0Kgw

:-P

73

Richard VE2DX
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: Lets TALK CI-V, an INTRO!

Michael WA7SKG
 

Trivia note:
I had always pronounced CI-V as "See-Eye-Vee", as did everybody I've ever heard discuss it. I had occasion to talk to an Icom guy a while back and he politely informed me it was properly pronounced "See-Eye-FIVE".

One of those FWIW things.

Michael WA7SKG


VE2DX wrote on 4/23/20 2:24 PM:

Ok,*ICOMs CI-V* it a very usefull and very simple protocol.
In this posting we will look at how we can figure out if the radio is in *RX or TX* and switch it to RX or TX.
First the CI-V protocol is a *handshake* protocol, someone must initiate the conversation and then who ever he is talking to will respond (sorry about the BAD english sometimes I am a frenchy and from the GREAT WHITE NORTH :P ) if available.
The structure of a CI-V exchange is simple enough;
*Header (Two FE)*
*address of the destination*
*address of the sender*
*command*
*sub command*
*Data (optional)*
*Trailer*
So if I want to know what is the radio doing (RX or TX) I would use the 1C command (see table below) and send;
*FE FE* (HEADER) *94* (Address for a 7300) *E9* (address I chose for my applications also known as Controller) *1C* (Command to reques/control tranceiver, tuner and other functions (see table attached)) 00 (Subcommand for RX/TX status/Control) *FD* (Trailer, notice NO DATA! very important)
Thus;
*FE FE 94 E9 1C 00 FD*
Note that *E9* is just an address I use to make it easier for locate my stuff, *E0* is more common, this can be anything that is not aready assigned on your CI-V buss.
the 7300 will respond like this;
*FE FE E9 94 1C 00 00 FD*
Note that now *DATA* is present aka our resonse; a *00* means (see table) I am in *Receive*, *01 TX*.  Also you noticed that the addresses are reversed, E9 94 thus 94 (7300) is responding to E9 (application).
*Ok what if I want to remotly put the radio in TX.*
you remember the *DATA* wasnt used in my command above, thats because I was doing a query, well what if I use it! if I were to put a *01* in there then I would be requesting the radio to transmit, thus;
*FE FE 94 E9 1C 00 01 FD*
so now instead of asking a status I am sending a command!
The response changes when you do this, the radio will now ACKNOLEDGE (*ACK* or ICOMs *FB* I like to remember this as FINE BUSINESS!) or return a NEGATIVE ACKNOLEDGE (*NACK or FA)* to the command.
in the second table below you see the format of these.
so if I send a GO TO TX command
*FE FE 94 E9 1C 00 01 FD*
if it does it will respond with ACK (FB) ;
FE FE E9 94*FB* FD
But if for ANY reason it can not it will respond with a *NACK (FA)*;
FE FE E9 94 *FA* FD
That was an *INTRO*,  I will try to go into more advance commands later.
*Hope this helped :-P*
Image preview
1C command set
Image preview
ICOMs CI-V handshake protocol,
*73*
*Richard VE2DX*
--
Only the Best ICOM, ERC and HRD
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/ <http://www.facebook.com/VE2DX/>
73
Richard VE2DX, Jesus Island, PQ-014
_._,_._,_


Re: Lets TALK CI-V, an INTRO!

VE2DX
 

Yes, my understanding is that it is 'See-EYE-FIVE' one of the variations of the definition is Computer Interface release 5, there are others even ICOM changed this over the years.

Hope this helps 😋

73

Richard VE2DX


From: Michael WA7SKG <wa7skg@...>
Sent: April 23, 2020 21:47
To: CIV@groups.io <CIV@groups.io>
Subject: Re: [CIV] Lets TALK CI-V, an INTRO!
 
Trivia note:
I had always pronounced CI-V as "See-Eye-Vee", as did everybody I've
ever heard discuss it. I had occasion to talk to an Icom guy a while
back and he politely informed me it was properly pronounced "See-Eye-FIVE".

One of those FWIW things.

Michael WA7SKG


VE2DX wrote on 4/23/20 2:24 PM:
> Ok,*ICOMs CI-V* it a very usefull and very simple protocol.
>
> In this posting we will look at how we can figure out if the radio is in
> *RX or TX* and switch it to RX or TX.
>
> First the CI-V protocol is a *handshake* protocol, someone must initiate
> the conversation and then who ever he is talking to will respond (sorry
> about the BAD english sometimes I am a frenchy and from the GREAT WHITE
> NORTH :P ) if available.
>
> The structure of a CI-V exchange is simple enough;
>
> *Header (Two FE)*
> *address of the destination*
> *address of the sender*
> *command*
> *sub command*
> *Data (optional)*
> *Trailer*
>
> So if I want to know what is the radio doing (RX or TX) I would use the
> 1C command (see table below) and send;
>
> *FE FE* (HEADER) *94* (Address for a 7300) *E9* (address I chose for my
> applications also known as Controller) *1C* (Command to reques/control
> tranceiver, tuner and other functions (see table attached)) 00
> (Subcommand for RX/TX status/Control) *FD* (Trailer, notice NO DATA!
> very important)
>
> Thus;
>
> *FE FE 94 E9 1C 00 FD*
>
> Note that *E9* is just an address I use to make it easier for locate my
> stuff, *E0* is more common, this can be anything that is not aready
> assigned on your CI-V buss.
>
> the 7300 will respond like this;
>
> *FE FE E9 94 1C 00 00 FD*
>
> Note that now *DATA* is present aka our resonse; a *00* means (see
> table) I am in *Receive*, *01 TX*.  Also you noticed that the addresses
> are reversed, E9 94 thus 94 (7300) is responding to E9 (application).
>
> *Ok what if I want to remotly put the radio in TX.*
>
> you remember the *DATA* wasnt used in my command above, thats because I
> was doing a query, well what if I use it! if I were to put a *01* in
> there then I would be requesting the radio to transmit, thus;
>
> *FE FE 94 E9 1C 00 01 FD*
>
> so now instead of asking a status I am sending a command!
>
> The response changes when you do this, the radio will now ACKNOLEDGE
> (*ACK* or ICOMs *FB* I like to remember this as FINE BUSINESS!) or
> return a NEGATIVE ACKNOLEDGE (*NACK or FA)* to the command.
>
> in the second table below you see the format of these.
>
> so if I send a GO TO TX command
>
> *FE FE 94 E9 1C 00 01 FD*
>
> if it does it will respond with ACK (FB) ;
>
> FE FE E9 94*FB* FD
>
> But if for ANY reason it can not it will respond with a *NACK (FA)*;
>
> FE FE E9 94 *FA* FD
>
> That was an *INTRO*,  I will try to go into more advance commands later.
>
> *Hope this helped :-P*
>
> Image preview
> 1C command set
> Image preview
> ICOMs CI-V handshake protocol,
>
> *73*
>
> *Richard VE2DX*
> --
> Only the Best ICOM, ERC and HRD
> https://groups.io/g/CIV
> Follow my projects on www.facebook.com/VE2DX/
> <http://www.facebook.com/VE2DX/>
> 73
> Richard VE2DX, Jesus Island, PQ-014
> _._,_._,_

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Lets TALK CI-V, an INTRO!

VE2DX
 

Ok, ICOMs CI-V it a very usefull and very simple protocol.

In this posting we will look at how we can figure out if the radio is in RX or TX and switch it to RX or TX.

First the CI-V protocol is a handshake protocol, someone must initiate the conversation and then who ever he is talking to will respond (sorry about the BAD english sometimes I am a frenchy and from the GREAT WHITE NORTH :P ) if available.

The structure of a CI-V exchange is simple enough;

Header (Two FE)
address of the destination
address of the sender
command
sub command
Data (optional)
Trailer

So if I want to know what is the radio doing (RX or TX) I would use the 1C command (see table below) and send;

FE FE (HEADER) 94 (Address for a 7300) E9 (address I chose for my applications also known as Controller) 1C (Command to reques/control tranceiver, tuner and other functions (see table attached)) 00 (Subcommand for RX/TX status/Control) FD (Trailer, notice NO DATA! very important)

Thus;

FE FE 94 E9 1C 00 FD

Note that E9 is just an address I use to make it easier for locate my stuff, E0 is more common, this can be anything that is not aready assigned on your CI-V buss.

the 7300 will respond like this;

FE FE E9 94 1C 00 00 FD

Note that now DATA is present aka our resonse; a 00 means (see table) I am in Receive, 01 TX.  Also you noticed that the addresses are reversed, E9 94 thus 94 (7300) is responding to E9 (application).

Ok what if I want to remotly put the radio in TX.

you remember the DATA wasnt used in my command above, thats because I was doing a query, well what if I use it! if I were to put a 01 in there then I would be requesting the radio to transmit, thus;

FE FE 94 E9 1C 00 01 FD

so now instead of asking a status I am sending a command!

The response changes when you do this, the radio will now ACKNOLEDGE (ACK or ICOMs FB I like to remember this as FINE BUSINESS!) or return a NEGATIVE ACKNOLEDGE (NACK or FA) to the command.

in the second table below you see the format of these.

so if I send a GO TO TX command

FE FE 94 E9 1C 00 01 FD

if it does it will respond with ACK (FB) ;

FE FE E9 94 FB FD 

But if for ANY reason it can not it will respond with a NACK (FA);

FE FE E9 94 FA FD 

That was an INTRO,  I will try to go into more advance commands later.

Hope this helped :-P

Image preview
1C command set
Image preview
ICOMs CI-V handshake protocol,

73

Richard VE2DX
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Yeasu ATAS-100/120 to ICOM CI-V project automatic controller (IAC1)

VE2DX
 

Here is another Ham project been working on for a while now and with warmer weathers up here in the GREAT WHITE NORTH! I realy need to finish this one soon and install the antenna on the mobile :-P

the IAC1 (Icom Atas-100/120 automatic controller) is working on the bench and is really simple, but I am sorry to say trying to make better (a bit more complicated, just a bit promise!) the unit uses CI-V to monitor the radio and when you change frequency or hit the TUNE button will move the ATAS-100/120 to the needed frequency, to my knowledge (Google searchs) it would be the only automatic interface existing.

the issue I am dealing with are ;

1- making it smaller, ok almost done
2- the unit sits near the radio and often the radio is in the trunk so the unit must have a seperate control head, well should (SHOULD) not be an issue just run a cable!
3- I dont want to run ANOTHER cable! so looking at wireless (wifi or Bluetooth!), found solution now GOT TO MAKE IT WORK!

OK, OK, OK! I like to have lots of BELLS and WISTLES...  and flashing lights...

But dont worry, I will keep the unit and remote very small and simple, a small display and coup of buttons (what...  up down and tune. is what I am thinking of, for manual operations.)

so this one I hope should be coming soon, PCB design is almost done and need to get the prototype working to send the PCB to manufacturing.

ah! AH! some older ICOM radio wont have all the needed commands, thats ok, I can still use CI-V and will have the option of added hardware to fix that...

Hope this helps :-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


CI-V Project hoping to get working... soon... :-P

VE2DX
 

Ok, here is a project I am still working on, the IMK1 (ICOM 8 MEMRY KEYPAD), is a 8 memory keys keypad for the 7300, 9700 and 7610 probably other need to check...

the unit is NOT attached to the microphone, it is attached to the REMOTE (CI-V) port on the back of the radio and uses CI-V to trigger ALL 8 memories unlike the standard 4 keys setup from ICOM using the Microphone.

I will also come out with a standard microphone 4 memories variation with PTT, up and down buttons, Foot PTT plug, 2 Memry Foot switch plug, aux mic and headphone plug

and finaly for highend ICOM radios like 7610 a simple 8 button external keypad.

so its coming (I think! I guess! yep it will like all my other Ham projects! oops!)

73

Richard ve2dx

Hope this helps :-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: CI-V address can I change them?

VE2DX
 

Very good info Micheal...

yes address 00 is often used by hardware also... it is also interresting to know that CI-V is a handshake protocol thus the protocol ids the host (application or device starting the conversation) and destination (likely to be radio).

and response reverses these two to reply .

i will put a post up on this

hope this helps :-P
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: CI-V address can I change them?

Michael WA7SKG
 

Also keep in mind that while there is a default address for each model of radio, some applications hardcode these addresses, so if you change the address in the radio, the application may not work.

Further, the universal address of 00 will work with most Icom radios. This address is used by some applications that control only basic functions like mode and PTT. In some radios, there are menu settings that may control whether the radio responds to the universal address.

Normally, about the only reason to change the CI-V address is if you have multiple radios of the same model on a common CI-V bus. In that case, it would be a good idea to refer to a list of default addresses to avoid a conflict.

73,
Michael WA7SKG


What is the difference between an original Icom CT17 and the VE2DX CT-17B

VE2DX
 

the original Icom CT-17 is still available from some Ham Radio retaillers, but it is dating from the 1980s.

the new just release VE2DX CT-17B Icom CI-V hub, is an improved windows 10 plug and play variation of the original ICOM CT17.

Here are the difference
1- ICOM CT17  needs external Power the VE2DX CT-17B does not need ANY external power since it is powered via the USB port.
2- Icom CT17 computer interface is via an RS232c DB25 connector while the VE2DX CT-17B is using an FTDI Chipset USB port.
3- Icom CT17 is 4 CI-V ports and one RS232C DB25, while the VE2DX CT-17B can be 5 CI-V ports, 5 CI-V ports plus an FTDI USB port, 10 CI-V ports, 10 CI-V ports plus an FTDI USB port or 10 CI-V ports plus two FTDI USB port.
4- Icom CT17 all ports are talking to each other, also true on 5 and 6 ports  VE2DX CT-17B but on the CT17B1X series (10, 11 and 12 ports) the CT17B can be split into two seperate 5 or 6 ports hubs thus giving the user more flexibility.
5- Icom CT17 has a rf choke seperating the ci-v ports from the RS232C port, while on the  VE2DX CT-17B  each ci-v and usb ports are isolated fom each othe with RFI protections.
6- Icom CT17 is 4 times larger then the  VE2DX CT-17B .
7- The  VE2DX CT-17B  has magnets under the unit to help attach the  VE2DX CT-17B  to the side of your radio.

https://www.youtube.com/watch?v=s9VK6s632n0

https://www.youtube.com/watch?v=jhb7Ef3kXn0&t=11s

https://www.youtube.com/watch?v=YkKvKKsjOXI&t=59s

We are now shipping if interrested please send me an email at ve2dx@...

hope this helps :-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


CI-V External Meter Project from VE2 Land

VE2DX
 

Here is a really nice simple (very!) project from a VE2 Friend of mine.

https://create.arduino.cc/projecthub/ddufault/external-s-meter-on-icom-radios-with-ci-v-port-d4e783

External S-Meter on Icom Radios with CI-V Port

it is using a Yaesu made external meter adapted using and arduino nano to snif the CI-V protocol to display the S-Meter.

here is a hint I modified the code on mine just a little and added a couple of buttons to ALSO display SWR or Power :-P

Hope this helps :-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


FTDI vs Prolific USB Adapter chip set

VE2DX
 

If you are shopping for a USB cable to use with ICOM radios, the most important thing to look for is the chipset.

over the years we have encountered thousands of issues with Prolific and pl2303 chip sets, you realy want to stay anway from these.The main issue is that they have been counterfieted in China and the copies are really bad, causing configurations and communication issues.
 
the chip set you want to look for are FTDI chip sets like we use in the CT-17B VE2DX ICOM CI-V hubs, these are the best and really plug and play in Windows 10.

hope this helps :-P
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Re: CI-V what cable should be used!

VE2DX
 


--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


ICOM CI-V Reference manual 3rd Edition 1991

VE2DX
 

its a little (lot!) old the basic principals are still the same, the commands have had an evolution.

https://www.dropbox.com/s/dim7d2ts0yfm3qa/CI-V%20Reference%20Manual%20Third%20Edition.pdf?dl=0

The 7610 CI-V manual is newer and a mutch better reference 

https://www.dropbox.com/s/1n932vd4vdl5874/ico-ic-7610_yj.pdf?dl=0

hope this helps :-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Project page

VE2DX
 

I am working on multiple CI-V designs like the IMK1 (8 memory keypad for 7300, 9700, 7610), IAC(Atas-100/120 CI-V interface) and CT-17B ICOM CI-V Hub and planning other like possibly the external keypad for ICOM radios via CI-V and CI-V Switch to mange collisions and other CI-V protocol issues that will come ... one of these days :-P

please follow us here or on our (yes I am going to say the swear F word!) facebook page

you can also follow our youtube videos were I try to post usefull videos of my projects.

;-P
--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


CI-V address can I change them?

VE2DX
 

The answer is YES, but you must understand that this will affect your applications and something the other devices linked to your radio

The ICOM CI-V protocol uses 2 digit adressing for the ICOM radios, in most cases the addresses are predefine depending on the radios example 7300 is H94.

obviously because of this, most softwares have these addresses defined also by default, thus if you change you CI-V address then you MUST also change your software.

This is common is situation like SO2R where you want to have lets say 2 IC-7300 on the same CI-V bus obviously one of them will be at H94 but what about the otheone, you must change the address of the second one or there will be a conflict.

becarefull, some non-icom CI-V devices like the WX0B first generation Bandmaster need to have the ICOM device address of the originating radio to be able to work thus these may also need to be reconfigured.

:-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014


Are all ICOM radios using same CI-V commands?

VE2DX
 

Answer is NO, the CI-V protocol has evolved since the early days on radios like the IC-735 where the commands sets were very basic like freq up and down, set freq and set bands (and more obviously!)

Now you can send your radios in TX, trigger the Voice Keyer, even program your CW Keyer via CI-V and A LOT MORE...

Most ICOM radios manual contain all the CI-V supported by the radios, but we did find some hidden gems like on the 7300 were some 7610 commnds that are REALLY nice that work ALSO on the 7300 that are NOT in hte 7300 manuals!!!  Hint!

there is older german web site that shows this information but only on older ICOM radios, still very good reference http://www.plicht.de/ekki/civ/index.html

:-P

--
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
73
 
Richard VE2DX, Jesus Island, PQ-014

41 - 60 of 64