Date   

NEW! CT-17B-6BT Bluetooth 6 ports CI-V hub.

VE2DX
 

Hey Gang, here is anothor of my TERRIBLE quality videos of a Bluetooth 6 port CI-V hub.

The CT-17B-6BT (Name change from the unit in the video CT-17B-5B) has 5 RF filtered CI-V ports and a Bluetooth interface for a serial port to your PC application.

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

The unit is powered by any regular Micro-USB power supply and the USB power is also RF Filtered.

Finaly it is enclosed in a 3D printed custom enclosure with magnets to help with the unit installation.

It should be available by july 2020, more info on www.VE2DX.com.

73
 
Richard VE2DX, Jesus Island, PQ-014nd, PQ-014

VE2DX ELECTRONIC 
WWW.VE2DX.COM
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
 


How To 101 for CI-V installations.

VE2DX
 

Following Mel's message earlier I decided to make to post to put together a list of DOs and DONTs for CI-V...

DOs;

1- Use only mono 1/8 cables
2- do use ferrite cores rf choes that snap on the cables to prevent damages to your radios, the ICOM CT-17 and VE2DX CT-17B do use RF filtering to help, but simple snap on ferrite cores are also a very good ideal and easy to install!
3- do your CI-V buss planning properly, the beauty of CI-V is that it is an addressable network wich means you CAN have multiple radios on the same CI-V bus, BUT if you use 2 identical radios in an environnement like SO2R, you MUST manage your CI-V adressing since by default both radios would have the same address (exemple : IC-7300 both would be 94H) thus one of them would have to be changed to an address not used on your CI-V network.
4- Should I put everything on a single CI-V network or NOT?  well the answer is it depends!  You see not all applications support multiple radios on a single serial port?  for exemple HRD does not, thus if you want all your radios on the same CI-V buss you WILL have to use multiple USB (FTDI recommended!) serial ports.  also you must keep in mind that you may want to seperate the radios and there assigned devices on seperate CI-V Networks, a lot of these devices are NOT device specific, they just listen to ANY CI-V comms going on the CI-V Network and react to it (for exemple change bands!), thus if you have multiple radios and you want to use one Bandselector on radio1 and a second on radio2 you WILL have to use a device like the CT-17B-12DualUSB that gives you the possibility of seperating the hub into two seperate hubs by removing JP-1.
5- My ICOM radio have a USB port should I use it for the CI-V communications, the answer is YES, if supported like on most newer ICOM radios then you should.  The radio CAN be configured to echo the CI-V commands from the USB port on the CI-V port in the back of the radio (Remote connector) you can then configure your radio to do so and thus still attach your CI-V devices via a CT-17B on the back of the radio.
6- Do I need special 1/8 or USB cables for the radio ; NO, good quality standard cables can be used just make certain to add snapped on ferrite Cores to filter the RF.
7- Why would I use a CT-17B-12DualUSB; well simply to give you if needed the flexibility of splitting easilly the CI-V Network into two distinch networks,
8- Should I use Tranceive in my radios CI-V settings; the answer is it depends!  Some external CI-V device NEED CI-V Tranceive to be on, but if you do beware of you CI-V network planing, since Tranceive WILL make other radios on the same CI-V Network react 

Donts:

1- NEVER USE stereo  1/8 cables on your CI-V netwrok.
2- DONT pay for SPECIAL CI-V 1/8 or USB cables, these are just regulare cables with possibly a ferrite core.
3- DONT use your USB port ONLY for CI-V, you can also use it for AUDIO CODEC and other interfacing.
4- Try not to use cables that are too long forcing you to coil them behing the radio, this is an RF nightmare and WILL cause you trouble.

More info and tips on our web site www.ve2dx.com .

Hope this helps :P

--
73
 
Richard VE2DX, Jesus Island, PQ-014nd, PQ-014

VE2DX ELECTRONIC 
WWW.VE2DX.COM
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
 


Re: Instructions on using the CI-V units

VE2DX
 

Hello Mel, you can download the manual and see some tips in the support section of our web site. Www.ve2dx.com

Hope this helps


Téléchargez Outlook pour iOS

De : CIV@groups.io <CIV@groups.io> de la part de Mel - N7GCO - Cheney, WA <teammel@...>
Envoyé : Monday, June 8, 2020 12:06:02 AM
À : CIV@groups.io <CIV@groups.io>
Objet : [CIV] Instructions on using the CI-V units
 
Are there any instructions on how best to use the CI-V units?
Mel
N7GCO

--
73
 
Richard VE2DX, Jesus Island, PQ-014nd, PQ-014

VE2DX ELECTRONIC 
WWW.VE2DX.COM
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
 


Instructions on using the CI-V units

Mel - N7GCO - Cheney, WA
 

Are there any instructions on how best to use the CI-V units?
Mel
N7GCO


Re: Bluetooth CT-17B-5B CI-V Hub

VE2DX
 

updated it to the latest version here

https://www.dropbox.com/s/6l87katdngcerys/IC-9700_ENG_CI-V_2.pdf?dl=0

--
73
 
Richard VE2DX, Jesus Island, PQ-014nd, PQ-014

VE2DX ELECTRONIC 
WWW.VE2DX.COM
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
 


Bluetooth CT-17B-5B CI-V Hub

VE2DX
 

Ok, there has been some request for this and it is coming along fairly fast.

The evolution of the CT-17B series will include the CT-17B-5B(Bluetooth), it will be a 5 CI-V ports and 1 Bluetooth port CI-V Hub compatible with windows 10.

- It will be fix baud rate at 9600 at this time.
- Power for the device will be RF Filtered via USB power via a regular Micro-USB USB connector.
- USB cable and USB transformer will NOT be included.

stay tune for up coming demo and video.

release probably late June 2020

73
 
Richard VE2DX, Jesus Island, PQ-014nd, PQ-014

VE2DX ELECTRONIC 
WWW.VE2DX.COM
Only the Best ICOM, ERC and HRD 
https://groups.io/g/CIV
Follow my projects on www.facebook.com/VE2DX/
 


ICOM 9700 CI-V reference manual.

VE2DX
 

For those like me that were looking for this, here is a copie of the ICOM 9700 CI-V Reference Manual.

https://www.dropbox.com/s/bqbuv36o3zqr3so/IC-9700_ENG_CI-V_0.pdf?dl=0

Hope this helps :P


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


CT-17B evolution

VE2DX
 

Some users have asked us about the fact that the USB cable on the CT-17Bs are fixed length and hardwire, the present design was done to keep the units as small as possible.  The USB cables presently used are 36 inches long wich is appropriate for most application, but we do understand not all!  And being in an RF environnement we understand that the users are concerned about using extension cables.

In our next generation CT-17B (late summer 2020) the original design will still be available, but we will also offer a little larger design second generation with a USB Mini connector thus giving the user the possibility of replacing the cable as needed.

other variant and improvement of the CT17B second generation ;
- mini FTDI USB connector.
- Better RF filtering.
- A Bluetooth version that will not have any USB ports and will communicat with the computer via bluetooth.
- A version with DTR and DCD opto isolated keyed output for CW, PTT and RTTY FSK.

73

Richard VE2DX
VE2DX ELECTRONIC 
WWW.VE2DX.COM
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-014nd, PQ-014


www.ve2dx.com

VE2DX
 
Edited

OK, well after many months working at everything, a big piece of the puzzle is now online.

www.ve2dx.com

our new web site is live.

you will find information on our project, ham radios tips on ICOM, CI-V, Rotor controllers, etc...

please pass the word.
-- 
VE2DX ELECTRONIC 
WWW.VE2DX.COM
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: What is the difference between an original Icom CT17 and the VE2DX CT-17B

VE2DX
 

Ok, 3D printer back online and plenty of parts came in so the CT-17Bs (Icom CI-V hubs) and IAB1 (Icom Breakout Boxes are available for shipment again this week.

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

let me know if your are interrested ve2dx@...

73
--
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: ICOM Memory keypads family of products comming soon.

VE2DX
 

OK Guys! Finale version of the IMK (Icom Memory Keypad) family, bigest changes;
 
- IMK2 None, ready to go.
- IMK3, added TX light, changed for the Larger PTT button.
- IMK3B well thats where most of the major changes are, the radio switching was a challenge, ended up using a very small microprocessor and it works GREAT, added LEDs for TX and Radio indicator (radio1 / Radio2) positioning is key to helping the operator.
 
sending the design for PCB fabrication tonite and ordering my parts the whole family will be great but IMK3B uP will be WOW!
 
And YES I am still working on the IMK1, the first one will be same form factor as the existing IMK family products, the touch screen (if I can find a capacitive touch screen that works well enough!) will likely be similar form factor, this design is small ergonimic and really great.
 
Hope you like it, please send me your questions and suggestions at ve2dx@....
 
PS: still aiming for June release :-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


ICOM Memory keypads family of products comming soon.

VE2DX
 

Well am still working on the CI-V based 8 memories keypad for the 7300, 9700and 7610, but running into major issues with finding a 
good quality capacity touch screen at a fair price to make the keypad feasable, the resistive touch keypads are just not good enougth,
will probably release a tactile switch version first (like IMK2, 3 and 3B.

Meanwhile, am looking at releasing soon the IMK2, IMK3 and IMK3B family, the IMK1 Tactile version will look similar to IMK3B but with 8 memories...

https://www.youtube.com/watch?v=3FWcMfHGcwQ
 
Well still working on the IMK keypads family of products, looks like the first products to come out will be the IMK2 for highend
ICOM radios with Keypad jacks in the back, we added PTT and Spare buttons, these come out on the tip (PTT) and Ring (Spare)
of the PTT Out jack in the back of the IMK2, the spare is a Normaly Open switch (low current) to control other devices in the shack.
 
The IMK3 I am still debating using the VERY large PTT button like on the IMK3B (comments?) other then that unit is pretty mutch
done, we did have to make the PCB 10mm larger then originaly planned for prper key spacing issues.
 
The IMK3B is the BIG BROTHER of the others, the IMK3B is an IMK3 on steroids! it supports via a new option card 2 radios,
you can switch from Radio1 to Radio2 on the fly with the two distinct radio selectors. The PTT button is larger and based on 4
seperate switchs making operations easier, the Headphone jacks have both radios (one on each side) as with all the IMK
products you have the MFS (Mempry footswitch) jacks, MFS1 can be configured via jumpers inside the IMK to any of the
memory (8 on IMK2 and 4 on IMK3 and IMK3B), PTT input, Front and Rear audio output (rear is switched off when
front is in use) and powered aux input microphone perfect for your BM800,
 
let me know what you think.
 
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


Just kidding around... :-P

VE2DX
 

Or am I!

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

--
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
 

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

61 - 80 of 97