Large station CI-V Operations


VE2DX
 

When automating your ICOM Radio stations you will likely be using CI-V here are a couple of things to keep in mind when you do especially for larger multiple radio stations.

1- Collision, when you have multiple radios and other CI-V compatible devices all talking to each other on a single CI-V Bus you may (WILL!) encounter collisions.  In most cases other than a bit of latency you will not notice any issues.  But some devices especially the IC-PW1 (Note 1) are known to be affected in a major way by those.  

Split your CI-V Bus into radio oriented segments; if two radios DO NOT need to talk to one another, split them up using separate CT17B hubs or simply pull the JP1 from under your CT17B-10 Series (10, 11Usb or 12 Dual USB) to split it up into two distinct hubs, by doing this the two or three separate hubs can operate on there own.
   
2- DON't use Tranceive mode unless you need it, and you may need it to make certain your non-ICOM CI-V devices be able to sniff the data from the targeted device on the CI-V Bus. but if not disable it.
   
3- Some Non-ICOM devices send a data request on the CI-V Bus to the targeted device to get needed info to operate, like Frequencies, mode, or Band...  If your device does adjust the latency to keep those requests as spaced apart as possible.


----WARNING--- this last suggestion WILL add latency to your device and may have a negative or even damaging effect to your station, know you devices properly before doing this!


4- if your radio offers USB CI-V access USE IT, the trick here is to echo your CI-V data on the CABLED CI-V Port (Remote) to your other devices using the CT17B Hubs if needed. This does help in managing your CI-V traffic on your CI-V Hub.

5- Use proper Mono 1/8 cables on your bus, using Stereo cables may work for now, but IT WILL make you eat your lunch after adding other CI-V devices that don't support Stereo cables, I know I DID

6- USE Ferrite cores on all your CI-V cables, even if all VE2DX CT17B and IAB series devices are RF filtered, you NEVER have enough RF filtration.

7- Bring your CI-V speed up as high as possible, this will help manage latency. 

When running off ICOM Radio USB port (7300, 9700, 7610, etc...) that is probably 115.2k.
When running off USB rs232 port or USB-based devices like CT17Bs, that will vary according to your port configuration.

---NOTE--- Keep in mind if this is via a CT17B hub you WILL need to make certain ALL your radios and NON-Icom devices on the hub are running the same speed.
---NOTE--- Newer ICOM radios like 7300, 9700, 7610, etc... have separate CI-V speed configurations for the USB CI-V and the CABED CI-B(Remote) Port, if echoing the data, the speed conversion will be done by the radio! NICE! :D

8- Know how to properly configure your Control or logging software.  improperly configured software can and WILL cause you problems with connections, latency, and other issues. KNOW YOUR SOFTWARE!

Hope this helps

--
73
 
Richard VE2DX, Jesus Island, 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/
 

Join CIV@groups.io to automatically receive all group messages.