[chirp_users] Copying data from one rig to another (of the same model)
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
On Tue, Mar 18, 2014 at 11:31 AM, YT9TP - Pedja yt9tp@uzice.net wrote:
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
Cloning means different things for different manufacturers. I'll use the two I am most familiar with as examples:
Yaesu's clone operation does as you suggest: dumps the entire memory and settings to the other radio, including region codes and anything else the radio stores. I believe the firmware is designed to reject the clone if the region code differs. Chirp emulates Yaesu's clone operation, so between like-model Yaesu's, sharing .img files should be fine.
Motorola's clone operation is internally very similar to Chirp's import/export. It takes just the channels and settings of one radio image and sends them to another radio, not touching the rest of the radio's flash. It does it this way because Motorola stores radio-specific data like calibration values and these should not be copied from one radio to another. What they call "cloning" is more complex than simply uploading a .img file.
Due to the nature of Chirp, we don't really know what is contained in the .img file other than channels and settings. All radios in Chirp have been reverse engineered, not written to a manufacturer's specification. Some radios we have nearly the whole memory map decoded, so we are reasonably sure nothing will go wrong when writing an .img from one radio to another. For other radios, all we know is where the channels are stored.
When you export/import or copy/paste from one radio to another, you are copying only channel data. There are no unknowns. We can recommend this with full confidence. Besides, this is the only way to do it from differing model radios.
Tom KD7LXL
Hi Pedja
I've known a number of people who thought they could "clone" one radio from another. And failed.
And you can't just write the programming for one radio straight onto another. You'll get an error message.
What you have to do is download the programming from the donor radio. Download the programming from the receiving radio and then "Copy" the data from the first radio's "table" and "paste" it into the second radio's "table", overwriting the previous contents. Then you can write the amended second radio's "table" back into the radio without the error message.
Bob M0TMT
On 18/03/2014 18:31, YT9TP - Pedja wrote:
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
There is a way to clone but it requires a cloning cable, not a programming cable. Or does comes with its own set of issues. This is covered at
http://www.miklor.com/uv5r/UV5R-Clone.php
Hope this helps ... John
Sent via iPhone6
On Mar 18, 2014, at 2:31 PM, YT9TP - Pedja yt9tp@uzice.net wrote:
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
The issue would be the firmware changes if any. But if you bought a dozen radios for your business all with the same firmware and you have the cable, it would be quicker just to clone the 11 others from the first radio you set up manually or via software.
________________________________ From: John LaMartina JohnLa@usa.net To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Tuesday, March 18, 2014 3:48 PM Subject: Re: [chirp_users] Copying data from one rig to another (of the same model)
There is a way to clone but it requires a cloning cable, not a programming cable. Or does comes with its own set of issues. This is covered at
http://www.miklor.com/uv5r/UV5R-Clone.php
Hope this helps ... John
Sent via iPhone6
On Mar 18, 2014, at 2:31 PM, YT9TP - Pedja yt9tp@uzice.net wrote:
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
I've cross-rig imported the .img file from say Baofeng to Anytone to Wouxun to Yaesu without any harm. Sure there are some columns and program properties that don't apply between radios. This is NOT cloning. As Tom says cloning is copying the contents of the rig to another identical rig. So chirp doesn't clone as far as I'm concerned but it handle cross brand importing of the .img file pretty well as long as you use the IMPORT function. Don't just open the img file it must be imported. I think I would still import even if I had ten identical radios. It's easy enough to do.
________________________________ From: YT9TP - Pedja yt9tp@uzice.net To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Tuesday, March 18, 2014 2:31 PM Subject: [chirp_users] Copying data from one rig to another (of the same model)
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
On Tue, Mar 18, 2014 at 2:31 PM, YT9TP - Pedja yt9tp@uzice.net wrote:
First, I want to emphasize that I know that it is recommended not to copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
Like Tom, I will use radios I am familiar with.
UV-5R (and variants)
You must not transfer the AUX block of a radio with BFB291 or newer firmware with a radio with pre-BFB291 firmware. The reverse is also true. The "old" and "new" firmware have different layouts. Other differences have been noticed in the AUX block between many firmware versions, so CHIRP will not transfer the AUX block if the firmware version in the current tab of CHIRP is different from the firmware version of the radio.
UV-B5/UV-B6
The image file (both CHIRP and the OEM software) contains the radio "test data". By uploading an image to a radio that was downloaded from a different radio, will change settings that were configured in the factory when the radio was manufactured. The VHF squelch thresholds, the UHF squelch thresholds, the VHF high and low power levels and the UHF high and low power levels.
I know someone that accidentally changed all of their UHF high power settings to 255 and damaged the radio's UHF power output in short order. If a CHIRP image from this radio was uploaded into another one, the same would happen if the PTT was press on a UHF frequency. Or if someone wanted to run QRP and set all of the low power settings to something less that the 1 watt factory setting, loading the image saved from that radio into another would set it to QRP as well.
Someone could maliciously set all of the high power settings to the max and post it in a forum just to see how many radios could be damaged. Remember, that this isn't a CHIRP problem. The same can be done with the Baofeng software.
Wouxun KG-UV-6D
I'm not certain, but I believe that the image from this radio also contains settings that were configured at the factory. Directly uploading an image that was saved from another radio can affect your radio in undesirable ways.
The bottom line is that it is not a good idea to directly upload images from other radios into your radio without knowing the risks. When in doubt, cut-and-paste between tabs or use the Import .img feature that Milton suggests.
Jim KC9HI
One disturbing thing I have heard from a Wouxun dealer (former) is that all Wouxun radios has a QC issue with the manufacture of a working memory chip. During bootstrap All data is uploaded from NVRAM. While the write cycles for this chip are supposed to be in the millions some have failed way too prematurely. This results in a bricked radio. Wouxun knows about it but has supposedly done nothing to correct the problem. However you will probably buy a KG-UV6D that will outlive you. This was enough to end one dealer who had sold tens of thousands of Wouxun radios a month to dropping them from his menu. Also Wouxun was made he didn't want to sell their new dual band mobile which he gave 5 thumbs down. I own two KG-UV6D radios and a lot of accessories like several battery packs, alkaline cases and the radios really work well for me. So I don't want to give anyone the feeling their Wouxun is going belly up anytime soon I just though this might be the time to give this one time PSA to owners. Especially those contemplating their mobile.
________________________________ From: Jim Unroe rock.unroe@gmail.com To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Sent: Tuesday, March 18, 2014 7:13 PM Subject: Re: [chirp_users] Copying data from one rig to another (of the same model)
On Tue, Mar 18, 2014 at 2:31 PM, YT9TP - Pedja yt9tp@uzice.net wrote:
First, I want to emphasize that I know that it is recommended not to
copy image saved from one rig to another.
There is just one thing I would like to clarify.
As I understand, Chirp uses clone function of a rig to copy settings from a rig and store them and also restore settings back to that rig.
Clone function is actually meant to be used to directly copy settings from one rig to another using direct cloning cable.
If direct cloning is harmless, why copying image from one rig to another using Chirp is not advisable? Isn't it the same as direct cloning except image is intermediately saved on computer?
YT9TP, Pedja http://www.yt9tp.iz.rs
Like Tom, I will use radios I am familiar with.
UV-5R (and variants)
You must not transfer the AUX block of a radio with BFB291 or newer firmware with a radio with pre-BFB291 firmware. The reverse is also true. The "old" and "new" firmware have different layouts. Other differences have been noticed in the AUX block between many firmware versions, so CHIRP will not transfer the AUX block if the firmware version in the current tab of CHIRP is different from the firmware version of the radio.
UV-B5/UV-B6
The image file (both CHIRP and the OEM software) contains the radio "test data". By uploading an image to a radio that was downloaded from a different radio, will change settings that were configured in the factory when the radio was manufactured. The VHF squelch thresholds, the UHF squelch thresholds, the VHF high and low power levels and the UHF high and low power levels.
I know someone that accidentally changed all of their UHF high power settings to 255 and damaged the radio's UHF power output in short order. If a CHIRP image from this radio was uploaded into another one, the same would happen if the PTT was press on a UHF frequency. Or if someone wanted to run QRP and set all of the low power settings to something less that the 1 watt factory setting, loading the image saved from that radio into another would set it to QRP as well.
Someone could maliciously set all of the high power settings to the max and post it in a forum just to see how many radios could be damaged. Remember, that this isn't a CHIRP problem. The same can be done with the Baofeng software.
Wouxun KG-UV-6D
I'm not certain, but I believe that the image from this radio also contains settings that were configured at the factory. Directly uploading an image that was saved from another radio can affect your radio in undesirable ways.
The bottom line is that it is not a good idea to directly upload images from other radios into your radio without knowing the risks. When in doubt, cut-and-paste between tabs or use the Import .img feature that Milton suggests.
Jim KC9HI
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
participants (6)
-
Bob Aldridge -
Jim Unroe -
John LaMartina -
Milton Hywatt -
Tom Hayward -
YT9TP - Pedja