January 2012 - Developers - lists.chirpmyradio.com

[chirp_devel] [PATCH 0 of 4] Make ft857 survive to run_tests
by IZ3GME Marco 03 Feb '12

03 Feb '12

The following patches has to be applied on top of 857 ones I sent, here is also included the merge with Dan's changes in the repository. After all this ft857 can pass the run_test. 73 de IZ3GME Marco P.s. Hope all this work as this is my first try sending patch directly via email ...

4 29

[chirp_devel] [PATCH 0 of 1] Correction of a typo
by Marco Filippi IZ3GME 31 Jan '12

31 Jan '12

The following patch correct a stupid typo that causes detection failure on ft857-us image load

1 1

[chirp_devel] [PATCH 0 of 1] Add support for FT817ND and FT857 US versions
by Marco Filippi IZ3GME 30 Jan '12

30 Jan '12

The following patch add support for US versions of FT817ND and FT857 and should than resolve the clone problems raised by David and Kurt.

1 1

[chirp_devel] FT857 pre alpha
by Marco Filippi IZ3GME 19 Jan '12

19 Jan '12

Hi all you people there! Because I'll be far from my radio in the weekend I decided to anticipate the publish time of ft857 support sources. Please try it, stress test it and report any bug or success detail. This is the work that is to be done: - check if is_cwdig_narrow is working (i suppose that radio accept it only with optional filter installed) - check if ipo and att bits are really where they are supposed to be (even if not supported in chirp is good to know them and set them correctly) - test ssb_step, am_step, fm_step - try to figure out the meaning of all unknown bits (unknown6 and unknown8 are probably tone and dcs for asimmetric tone modes) all other bits are supposed to be working. I know it fails the run_tests, I'll work on this during the we. The attached patch has been obtained on top of the changeset 1260:df1ee5859394 from the repository. ... and don't forget to test the 817s also! ;) 73 de IZ3GME Marco

1 0

[chirp_devel] debugging Yaesu VX-8DR transfers
by Hisashi T Fujinaka 19 Jan '12

19 Jan '12

I just got a cable from someone in China and started trying Chirp on my MacOSX 10.7 system with the Python runtime. After a bunch of tries I finally got it to read the memories from the radio (you have to put it in tx mode several times to hit the window correctly) but now I'm not having any luck writing to the radio. I put it in clone "wait" mode, hit the "go" button, and it immediately finishes. So, where's the debug console? Or is there a description of the transfer waveforms so I can look at it on a 'scope (which I don't want to do unless I have to). I'm not sure how I should be debugging this, or what code snapshot I should be running, so I though I'd ask here. -- Hisashi T Fujinaka - htodd(a)twofifty.com BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte

2 2

[chirp_devel] Supporting Yaesu FT857 radios with Chirp
by David Ranch 19 Jan '12

19 Jan '12

Hello Chrip-devel, I've been recently emailing Dan Smith and he recommended to join this group about this: I've heard that code is being developed for supporting the FT817 and FT857. This is something I asked for some time ago and it seems like it's about to happen! I'll be happy to do testing here. Before I go there, I have a related question I need to get answers before I can do any testing. Specifically, I have an RT Systems CT-62B cable here that came with their Windows software for a FT857 but Linux 2.6.32 doesn't recognize it: usb 2-1.3: new full speed USB device using ehci_hcd and address 12 usb 2-1.3: New USB device found, idVendor=2100, idProduct=9e56 usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 2-1.3: Product: CT-62B Radio Cable usb 2-1.3: Manufacturer: RT Systems usb 2-1.3: SerialNumber: RTTFPERY usb 2-1.3: configuration #1 chosen from 1 choice Question #1 - Does anyone know if these RT System USB cables Prolific or FTDI based? Question #2 - If FTDI based, it seems it's only a matter of getting it initially supported with a "/sbin/modprobe ftdi_sio vendor=0x2100 product=0x9e56". If Prolifici based, the pl2303 module doesn't support this syntax. Instead, the Prolific driver seems to want this at the higher level with "/sbin/modprobe usbserial vendor=0x2100 product=0x9e56". What I don't understand is if the RT Systems cable is Prolific based, how will the USB system know to associate the device with the Prolific vs. FTDI driver? Why? Because I already have other FDTI and Prolific USB devices on the machine! Statement #1 - I've successfully submitted Linux kernel for the FTDI driver to support the US Interface Navigator USB IDs (think of it as a big brother to a Signalink device). So, once I have this tested and working, I'll submit the patch to the kernel folk. If other people have RT Systems device IDs (shown in "lsusb -v"), I'll add that into my patch. Anyway... please let me know when the FT897 code is ready for testing and I'll give it a try! --David KI6ZHD -------- Original Message -------- Subject: Re: [Fwd: [chirp_users] New Daily Build] Date: Wed, 18 Jan 2012 09:18:38 -0800 From: Dan Smith <dsmith(a)danplanet.com> To: David A. Ranch References: <4F159FBD.4000904(a)trinnet.net> <4F15A065.3070802(a)danplanet.com> <4F16FE33.7020604(a)trinnet.net> > Ok.. I'll try to add myself to that list. Marco says he does in fact have an 857, and that we should expect support for it to show up soon. Being on the devel list would let you help test that ahead of time, which would be good. > Quick question.. I have an official RT-Systems USB cable for the > FT857 but it's not recognized by the Linux 2.6.32 kernel. I want to > say these are Prolific based devices but maybe they are FTDI? I > already submitted kernel patches that were accepted to add US > Interface Navigator support so maybe I can do the same for these > serial devices. Yeah, these devices are not setup to provide a VCP by default, and I think they are in fact FTDI. I don't have any, so I haven't gone through the process of trying to fix the vendor IDs, but Robert Terzi has. Ask on the devel list and I think he can get you set right up. -- Dan Smith www.danplanet.com KK7DS

4 4

[chirp_devel] [PATCH 0 of 2] Add has_nostep_tuning feature flag
by Dan Smith 17 Jan '12

17 Jan '12

The following two patches should resolve Marco's issue with setting fine-tuned frequencies (such as pretty much everything on HF)

1 2

[chirp_devel] FT817ND
by IZ3GME Marco 16 Jan '12

16 Jan '12

Hi all for your info last night I started working on support for FT817ND in chirp. Even though this is my first time with Python I was able to start a new module, write and test the "clone receive" and checksum routines before to go to bed ;) Today I'll finish beautify the receive code and probably will also write the send routine. At a first look memories in the dump seams to be in the same format as described in http://www.ka7oei.com/ft817_meow.html but i'll start working on this later on. If some one has more info please notify me: every bit of information can help. ... and naturally if there are volunteer betatesters I'll be happy to send the source and share the effort best 73 de IZ3GME Marco

5 24

[chirp_devel] Hello
by Andrew Errington 13 Jan '12

13 Jan '12

Hi everyone, I just became interested in Chirp, but I have a Yaesu VX-2R, which does not seem to be supported. What do I have to do to add support for the VX-2R? I suspect I could edit the VX-3 code, or could somebody tell me if it Just Works anyway? I have read the list archives (and most of the main chirp_users list) but no mention is made of this radio. Google doesn't tell me much either. I generally use Linux, and I am comfortable with Python. I have one VX-2R, and I don't want to break it..., but having said that I am building my own interface cable by hacking an FTDI-based USB->serial adaptor. All I have to do is remove the RS232 level shifter chip and connect VCCIO on the FTDI chip to 3V3 instead of 5V. Naturally I am doing all of this in my copious free time, so who knows when it will be finished. Thanks in advance for anything about the VX-2R, 73, Andrew ZL3AME

5 10