[chirp_devel] Initial Yaesu FT-857 testing

David Ranch
Thu Jan 26 15:04:40 PST 2012


Hello Macro, Dan,

Here are my initial results.  As you can see, a bit more work needs to 
be done.  If you need me to do some additional tests, please let me 
know.  Maybe running it with a

CHIRP_DEBUG=y ./chirpw 2>&1 | tee debug.log

--David


With a patched 0.1.13dev running on Centos 6.2 with an RT-Systems 
FTDI-based USB cable
  - GTK 2.18.9
  - PyGTK 2.16.0
  - Python 2.6.6

If I configured chirp and it sat there waiting for a while (30 seconds) 
without starting the Clone on the radio, it eventually throws an error:
--
CHIRP 0.1.13dev on Linux - CentOS release 6.2 (Final)Kernel \r on an \m 
(Python 2.6.6)
Clone thread started
-- Exception: --
Traceback (most recent call last):
  File "/usr/src/archive/Chirp/chirp-hg-c00282ce90f6/chirpui/clone.py", 
line 223, in run
    self.__radio.sync_in()
  File "/usr/src/archive/Chirp/chirp-hg-c00282ce90f6/chirp/ft817.py", 
line 180, in sync_in
    self._mmap = clone_in(self)
  File "/usr/src/archive/Chirp/chirp-hg-c00282ce90f6/chirp/ft817.py", 
line 59, in clone_in
    data += ft817_read(pipe, block, blocks)
  File "/usr/src/archive/Chirp/chirp-hg-c00282ce90f6/chirp/ft817.py", 
line 37, in ft817_read
    raise Exception("Unable to read block %02X expected %i got %i" % 
(blocknum, block+2, len(data)))
Exception: Unable to read block 00 expected 4 got 0
------
Clone failed: Unable to read block 00 expected 4 got 0
Clone thread ended
--- Exception Dialog: Unable to read block 00 expected 4 got 0 ---
None


A chirpw timeout was expected but the user dialog box on the GUI should 
be made to be less cryptic



----------------------------


If I tried again, with starting the Cloning on the radio,  the cloning 
image begins to go to
to Chirp but at the end, the radio says "Clone mode: ERROR" though Chirp 
seems to be happy:

Clone thread started
Clone completed in 12 seconds
Clone thread ended
Starting memedit
'NoneType' object has no attribute 'split'
Bank Index supported: False
Bank supported: False
DTCS Code supported: True
DTCS Pol supported: False
Mode supported: True
Offset supported: True
Name supported: True
Tune Step supported: True
Name supported: True
ToneSql supported: False
Cross Mode supported: True
Started

-------------------

Looking in the resulting Chirp GUI, the downloaded memories look ok except

no power levels were saved.  Maybe this isn't saved on a per-memory basis?

I don't see any of the HOME memories in the GUI

I don't see any Memory group support in the GUI: valid groups a "Ma" 
through "Mj"
  -- need to test more as I didn't have any

Did not try the split memory yet
  -- need to test as I didn't have any

------------------

Saving the download image to a file works.  Closing Chirp down, 
restarting it, and opening up the saved image works properly

------------------

Sending from Chirp to the radio

  Transfer starts and seems to run fine up until the 99% mark:

   Chirp completes yet the FT857 is stuck where the radio's LCD shows a 
"full download bar" saying "clone mode: Sending" yet it never completes

   Had to turn off radio to exit the "Sending" screen

Upon restart, all memories and FT857 system settings were lost
   --> Sure would be nice if the program could also handle the higher 
level menu settings at lease just as a binary blob and allow to be able 
to restore or not-restore that when uploading back to the radio

  This seems to be the same behavior that Kurt KC9LDH saw with his FT-817

-----------------
Misc

   In the Radio dialog, it's not remembering the last serial port I 
used.  Specifically, I have my port named via UDEV as /dev/ft857_prog

   Chirp About --> Credits doesn't show Marco


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20120126/1dd73f18/attachment-0001.html 


More information about the chirp_devel mailing list