|
|
Post by Andrea IU4APC on Jul 22, 2014 16:26:09 GMT
Hi everyone, on the Google Store is available the new version of the KX3 Companion app. What's new in this version: - QRZ.com XML integration. If you are subscribed to QRZ.com XML service, fill in username/password in the settings and enable the automatic lookup - eQSL.cc integration. If you are subscribed to eQSL.cc, fill in username/password in the settings and enable it to automatically send an eQSL every time a new QSO is logged - DX Cluster integration. It is available in the Tools menu. The features are: - simple press QSY: click the spot line you are interested to, and the KX3 moves to the spot frequency - band filter: select which band you want spots for - list filter: enter a string, and it'll be used to filter spots. For example: "/P" will show only portable calls, "QRP" only QRP, "Japan" only those coming from Japan, etc - spot alert filter: enter a string used to filter spots. When a spot satisfying the alert filter is found, the app shows a popup alert and plays a sound. Alerting works only when the DXCluster is the open tool. Note: the list filter and the alert filter are independent, so you can enable/disable them with different string filters. Also: - Display keep alive option (enabled by default) - Text correction disabled option (enabled by default) - A long press on Name/QTH/Locator, quickly deletes all not logged QSO values (Call included) - Log time is now UTC based - Smaller Font Size for Macro buttons on smaller displays I decided to move the TUNE Helper feature to next version as I want to re-write the whole SWR sweeping and tuning features. Great thanks to all the people writing me and supporting me in developing what I'd like to be the best ham radio app, for the best ham radio!  One more thing... I created a page with a list of "known to be working" and "known to be not working" devices (phones and tablets). Please help me keeping it up to date with your information. The link to the page is: kx3companion.com/working-devices/72/73, Andrea IU4APC |
|
n5rwk
New Member
Posts: 11 
|
Post by n5rwk on Jul 23, 2014 1:46:04 GMT
Andrea,
I just installed the new (full) version and have been getting familiar with it. However, after about 30 seconds after connecting to the KX3, KX3 Companion becomes unresponsive. After some fruitless tapping I eventually I get a popup from the Android O/S stating "KX3Companion isn't responding. Do you want to close it?"
Here are some additional details:
- Samsung Galaxy Note 10.1 tablet (GT-N8013 is the specific model) running Android version 4.1.2
- I'm using a piglet to connect to my KX3, via a wireless connection to KX3 to the Piglet running in Infrastructure mode (I am connected to my cell phone running as a hotspot)
- Serial port speed on the piglet and KX3 is 4800. Same setting in KX3 Companion.
- The hang occurs about 30 after connecting to the KX3. It doesn't seem to matter what activity is going on, within 30 seconds it hangs. It is reproducible.
I checked the stability of my piglet connection to my KX3 with some other applications (specifically the Hamlog and Piglet apps). No hangs occur, so it doesn't appear the problem is with the Piglet.
Any idea what is going on?
Thanks,
Roger
|
|
|
|
Post by Andrea IU4APC on Jul 23, 2014 6:01:16 GMT
You can try two things.
First try rising the serial port speed.
Second try without the Piglet.
This should help me understand where's the problem.
Thanks!
Andrea IU4APC
|
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 23, 2014 15:13:50 GMT
Andrea,
I set up my tablet without the piglet, and kept the baud rate at 4800. Result: hanged as before after about 20 seconds.
Next, I changed the baud rate to 9600. No hangs at all, either with or without the piglet it worked fine.
So, I will avoid using 4800 baud, and use 9600 instead, even though the faster speed may be too much for me to handle :-)
The frequency updates more smoothly at 9600 anyhow.
Thanks for the guidance!
73,
Roger
|
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 23, 2014 15:25:56 GMT
Andrea,
I noticed that the QRZ lookup fields seem incomplete. It shows the first name and middle initial of the person, but their surname is not displayed. Also, I don't see state or country displayed either, which would be useful info to have. I realize space is tight on the interface, but could these fields be added somehow (or could the fields be made customizable)?
All in all I really like KX3 Companion and especially the new lookup feature. I used an old Windows netbook at field day this year, but with KX3 Companion and my tablet with a bluetooth keyboard it will be a big improvement in bulk, weight and screen real estate.
73,
Roger
|
|
|
|
Post by Andrea IU4APC on Jul 23, 2014 15:59:57 GMT
Andrea, I set up my tablet without the piglet, and kept the baud rate at 4800. Result: hanged as before after about 20 seconds. Next, I changed the baud rate to 9600. No hangs at all, either with or without the piglet it worked fine. So, I will avoid using 4800 baud, and use 9600 instead, even though the faster speed may be too much for me to handle :-) The frequency updates more smoothly at 9600 anyhow. Thanks for the guidance! 73, Roger Great news! I'm happy that you solved. I personally use 38400 and have no issues. You should start from higher frequencies and the lower the values if you see problems. Higher baudrate are preferred usually. Let me know  73, Andrea IU4APC |
|
|
|
Post by Andrea IU4APC on Jul 23, 2014 16:08:44 GMT
Andrea, I noticed that the QRZ lookup fields seem incomplete. It shows the first name and middle initial of the person, but their surname is not displayed. Also, I don't see state or country displayed either, which would be useful info to have. I realize space is tight on the interface, but could these fields be added somehow (or could the fields be made customizable)? All in all I really like KX3 Companion and especially the new lookup feature. I used an old Windows netbook at field day this year, but with KX3 Companion and my tablet with a bluetooth keyboard it will be a big improvement in bulk, weight and screen real estate. 73, Roger You're right Roger, but as you know, space is an issue. Much depends on how the name & surname are recorded on QRZ.com I can try to add the two name fields to have all in one field but then it'll be a problem to read them (it is already) unless I use smaller fonts or sacrifice part of the RX lines. Same applies to adding the country to the QTH. I'll try to find out some clever way to have everything shown somehow. Like a long press of the name temporarily show complete info... only showing it's not that difficult Next version will surely see an improvement in that. I'm happy that a part from those thing missing, you like it and plan to use it for future FD. 73, Andrea IU4APC |
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 27, 2014 0:10:48 GMT
Andrea,
Today I worked with my KX3, Samsung Galaxy Note 10.1 (GT-N2013) tablet and piglet some more. Unfortunately I'm still experiencing random KX3 Companion hangs (stops responding). I'm running at 38,400 baud rate connecting via piglet to the KX3. Over a two hour period, I experienced about a dozen hangs.
I'm unable to discern any pattern to the application hanging. It does seem that if I play with the controls on the KX3 itself that tends to trigger program hangs more frequently. But it is pretty random. I did have a good run, probably 15 minutes or so in CW mode before it hung.
I'm guessing there is something funny going on with the serial interface. I will try eliminating the piglet and going to a wired connection via OTG cable. I also have a Galaxy S4 phone that I can try using to see if it the application hangs on that device. Any other suggestions?
Thanks,
Roger
|
|
|
|
Post by Andrea IU4APC on Jul 27, 2014 13:14:42 GMT
Hi Roger,
I would have suggested to use it without the Piglet. You also have another device to test to it's perfect.
Let me know if using without the Piglet and/or with the S4 makes the difference.
I suspect that it maybe something related to the Wifi/Piglet.
72/73, Andrea IU4APC
|
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 27, 2014 20:31:14 GMT
Andrea,
I spent some more time working with my setup. I went back to using the OTG cable, everything at 38400 and things seemed to be stable. I then switched to the piglet, and experienced a couple of hangs. But I noticed these happened when I was messing with the actual KX3 controls (not from within KX3 companion). For example, spinning the main tuning dial across a band, or changing bands quickly both seemed to cause KX3 companion to hang. I hadn't done that when I was using the OTG cable.
So I went back to the OTG cable and spun the frequency knob on the KX3 a bit, and got it to hang with that setup too. Also, by hitting the band+ or band- buttons successively on the KX3 this will cause a hang. I did this a few times, and found that I can hang the application at will with either of these actions. So it looks like this is related to activity on the KX3 somehow messing up KX3 Companion (or the connection). I wonder if the stream of commands being sent to KX3 Companion are getting garbled somehow, or a buffer somewhere is overflowing?
BTW, the reason I'm changing the frequency on the KX3 itself is because it's more convenient. For example, when tuning in a CW station I can watch the zero-beat indicator on the KX3. If I tune or change bands s-l-o-w-l-y it seems less likely to hang.
On a plus side, I was able to make a successful CW contact with W1AW/1 using KX3 Companion and a couple of macros.
Regards,
Roger
|
|
|
|
Post by Andrea IU4APC on Jul 27, 2014 20:46:04 GMT
Good info.
I'll try to replicate the issue.
Did you try reducing the baudrate?
Thanks,
Andrea IU4APC
|
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 28, 2014 20:24:41 GMT
Andrea,
I just tested at 38400, 19200, 9600 and 4800 baud, using the OTG cable. In every case I can make the app hang by working on certain controls on the KX3 itself. Either changing bands (usually takes 4+ successive key presses) or by changing frequency quickly (8+ turns of the tuning knob).
I have not yet tested on my Galaxy S4 phone, as I discovered it needs a different OTG cable. It should arrive tomorrow, and I'll give it a whirl with that device.
Regards,
Roger
|
|
|
|
Post by Andrea IU4APC on Jul 29, 2014 6:58:19 GMT
Hi Roger,
thanks for the testing.
I'll try to replicate them and see what happens on my devices.
73,
Andrea iU4APC
|
|
n5rwk
New Member
Posts: 11
|
Post by n5rwk on Jul 30, 2014 16:09:45 GMT
Hi Andrea,
Got the OTG cable in for my Galaxy S4 phone, and tested this morning. Same result as with my Galaxy Note 10.1 tablet. I tested at 9600 baud, and got the app to hang by successive band changes, as well as changing frequency on the KX3 itself.
73,
Roger
|
|
|
|
Post by IZ4MJP on Aug 3, 2014 7:10:57 GMT
I experienced the same problem on an Asus MemoPad 7 (ME176CX - 1B035A). The KX3 Companion hang up frequently (often every time i move the VFO more than 10 Khz) and i was forced to quit the application.
After some try i resolved the problem in this way:
1) Unistalled the app
2) Reinstalled again
3) Cleared the cache of the App
4) Changed the "Polling Time" from 100ms (default) to 200ms. The Serial is still at 38.400 Baud.
After the new setup all seems work fine now.
I'd like to thank you Andrea for his work on this project.
Vy 73
Franco, IZ4MJP - HB9EIH
|
|
