"Sniffing" a protocol is one of the steps for developing a new driver, which means becoming a new CHIRP developer. It's fun but may be time consuming. Project leader Dan Smith has a page for new developers at : https://chirp.danplanet.com/projects/chirp/wiki/Developers I think I'm probably still the newest developer. I added a page on sniffing at:
https://chirp.danplanet.com/projects/chirp/wiki/DevelopersUSB_Sniffing_in_Li... This particular method works if you are using a USB serial cable. Other approaches are required for a "real" serial port cable or for any protocol that is not a real or pseudo async serial protocol. There are also alternatives if you prefer to use Windows. Another CHIRP user was able to use my sniffing page's instructions to sniff a Yaesu FT-25, so the page must not be completely incomprehensible.
After you successfully capture a full protocol interaction, the next step is to stare at the result to see if it looks like any of the protocols CHIRP uses in any of the hundreds of radios already supported. CHIRP code does not formally subdivide the radios based on the protocols, but there are several obvious informal "families" of protocols. If you see a match, look at the actual contents of the memory as conveyed by the protocol to see if it looks like one of the radios that use that protocol, then find that driver and see if you can tweak it to handle the new radio.
On Wed, May 8, 2019 at 1:21 PM Gary Craig gcraig@webcoindustries.com wrote:
Dan,
How would one go about learning how to "sniff" the protocol and then modify or build a module for it?
Be blessed!
May 2019 be our year of change & growth!
Gary Craig KI5CCD
Maintenance
Webco Industries
Texas Distribution
750 Martin Luther King Jr Dr
Orange, TX 77630-3094
409-886-0807 ext. 107
Fax 918-246-7045
gcraig@webcotube.com
*From:* chirp_users-bounces@intrepid.danplanet.com < chirp_users-bounces@intrepid.danplanet.com> *On Behalf Of *Dan Clemmensen *Sent:* Wednesday, May 8, 2019 1:44 PM *To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Subject:* Re: [chirp_users] Kenwood TH-K40E
*This email originated from an external sender. Use caution when following links or opening attachments as they could be malicious *
The list on the CHIRP homepage is (apparently) generated automatically from the daily CHIRP build, so if the radio is not here, then the CHIRP code does not know about it. Within the CHIRP code, there is (supposed of be) an "alias" defined for any radio that has the IDENTICAL programming interface with another radio. "identical" means completely indistinguishable, including any internal version or ID string.
If a radio is "almost" identical, then the CHIRP code needs to be updated so it knows the differences. If the radio is truly identical, then you can program it using the original name or any of the aliases. If you think you radio might be identical and you are very brave, you can try it: please report the result here. If you think it may be a variant, please consider learning how to "sniff" the protocol, and report the result here. Please do not try any of this unless you are willing to risk temporary or permanent problems with your radio up to and including totally bricking it. (very unlikely but you must take assume the responsibility for this.)
On Wed, May 8, 2019 at 11:33 AM Ernesto Xload xload.es@gmail.com wrote:
A lot of thanks Dan, I asked because I think that would be compatible with other Kenwood model.
73
El mié., 8 may. 2019 a las 20:29, Dan Clemmensen (danclemmensen@gmail.com) escribió:
Please look at the CHIRP Home Page:
https://chirp.danplanet.com/projects/chirp/wiki/HomeNo, it's not supported. Also look at the FAQ (second FAQ question)
https://chirp.danplanet.com/projects/chirp/wiki/FAQ
On Wed, May 8, 2019 at 11:21 AM Ernesto Xload xload.es@gmail.com wrote:
Hello,
Is Chirp capable of programming Kenwood TH-K40E?
Best Regards.
Ernesto Xload
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ernesto Xload at xload.es@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dan Clemmensen at danclemmensen@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com