Dear Wim,
This message: MCU ErrorCode: 4.
means that the utility could not correctly detect the WinKey and
FSK ports.
But importantly, this error does not always mean that these two
ports are not working.
The fact is that the utility determines the port numbers by their
unique name (this name is in the port driver).
The drivers for the ports of CAT, PTT and WinKey, FSK are
different.
Sometimes the OS independently installs standard drivers for all
ports (apparently, Windows thinks that these drivers are more
secure).
In those drivers that were installed by the operating system,
there is no unique identifier and for this reason the utility
cannot correctly determine the ports and issues an MCU error.
But at the same time, the ports can work without any problems.
It is possible to reinstall the driver manually. Then the error
will disappear.
Sincerely, Alex
17.12.2020 17:37, Wim via groups.io
пише:
toggle quoted message
Show quoted text
?
Dear Alex
?
Thanks for your reply.
?
I installed the latest FW (RigExpert Flash Tool v1.5.13),
Device FW is now 1.12.
But still MCU ErrorCode: 4.
?
Anyway I found out I can use MMTTY on COM 5, I also can key
WINKEY on COM 4.
It's just TI5000xPort program that generates fault code.
?
Program works ok on another laptop here (Lenovo core i5 and
Win 10).
Just curious what this MCU code is on my station computer.
?
73, Wim pa0wrs
?
|
?
Dear Alex
?
Thanks for your reply.
?
I installed the latest FW (RigExpert Flash Tool v1.5.13), Device FW is now 1.12.
But still MCU ErrorCode: 4.
?
Anyway I found out I can use MMTTY on COM 5, I also can key WINKEY on COM 4.
It's just TI5000xPort program that generates fault code.
?
Program works ok on another laptop here (Lenovo core i5 and Win 10).
Just curious what this MCU code is on my station computer.
?
73, Wim pa0wrs
?
|
Dear Wim,
First of all, check if there is a FW update available for your
interface.
Use the FlashTool utility:
If a new FW update is available, then update? interface.
Regards, Alex UR4MCB
17.12.2020 14:28, Wim via groups.io
пишет:
toggle quoted message
Show quoted text
Hello Group
TI-5000 driver issue:
Computer is an Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz??
2.11 GHz
OS is Windows 10 Home ver. 20H2.
I am having problems running TI5000xPort.exe for quite some
time.
I installed drivers (Drivers_TI_5000_x64.exe) again after
disabling secure boot.
TI5000xPort.exe generates following error: MCU ErrorCode: 4
(see attachment); not showing FSK and WINKEY ports.
I ran Driver Store Explorer (RAPR.EXE) and it looks like the
drivers have been installed OK (See attachment).
Any advise is appreciated
Wim pa0wrs
|
Hello Group
TI-5000 driver issue:
Computer is an Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz?? 2.11 GHz
OS is Windows 10 Home ver. 20H2.
I am having problems running TI5000xPort.exe for quite some time.
I installed drivers (Drivers_TI_5000_x64.exe) again after disabling secure boot.
TI5000xPort.exe generates following error: MCU ErrorCode: 4 (see attachment); not showing FSK and WINKEY ports.
I ran Driver Store Explorer (RAPR.EXE) and it looks like the drivers have been installed OK (See attachment).
Any advise is appreciated
Wim pa0wrs
|
Yes???? I learned how to take shape shots? I am trying to keep current with my New Toy. Love it over my MFJ ? Chummy is a Ringo ranger VHF,? J pole is VHF, ?Mobil on the tower ? ? ? ? ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of Alex RigExpert via groups.io
Sent: Monday, December 14, 2020 4:19 PM
To: [email protected]
Subject: Re: [RigExpert Family] Whats New? Dear Richard,
Please, specify what kind of information you are interested in?
You wrote about Stick and AntScope for PC.
Stick 230 does not connect via Bluetooth to a PC with AntScope2. Only Android and iOS now.
Work on this issue is planned for next year.
Sincerely, Alex 14.12.2020 22:57, Richard Lenker KB3YRC пише: Hi?? Rig Expert Family ? I joined to hear about my Rig Stick 230 And nothing for two weeks I updated it to 1.8 Ver? and have it to the PC with antscope ? Richard? KB3YRC Pennsylvania? USA ?
|
Re: Bluetooth problems AA-55 Zoom
Doug and Alex,
I've now testing my AA-55 Zoom BT with Doug's suggestions. I've made the Ingoing/Outgoing BT changes on the com ports on another Lenovo Thinkpad (Carbon X1) with Win 10 x64 (latest updates). I can get the AA-55 Zoom BT to make a BT connection with AS 2. However, a single sweep of a dummy load connected to the Zoom just puts the large red dot up in the top left corner and the blue circle working "forever" (10 minutes).?
There IS a BT issue or issues, Alex, as you've acknowledged. Doug has helped you identify the core matters in your interim fix. I hope your technicians will communicate with him and utilize his considerable BT expertise to help you successfully address the problem.
I've worked with many, many businesses in my career, been in a position to fund 50 startups in the tech industry, and consult for some amateur radio companies in the U.S. and abroad. Here's my assessment of RigExpert on the Bluetooth product line.
It's good to get innovative products into the marketplace. But it's worse to have them in an ongoing buggy situation. Xiegu's X5105 QRP rig, for instance, was almost killed off due to firmware issues that were pushing beta-testing on the mass market for their products. Their GSOC video controller device for both the X5105 and their more successful G90 rigs is patently unusable due to a rush to the marketplace. It will kill their brand unless they get things fixed.?
This is relevant to RigExpert because you now enjoy a good brand for AAs (my only experience). But open-sourcing AS can be both good and bad. The market place of open source programmers will not have the info to fix things in the code when they're outside of your development team inside the company. The market will think you're not trustworthy in buying what is *not* a discounted product as your AAs are seen as "pricey." If the BT AAs do not work or take the amount of fiddling that Doug (especially) and I have put in, the reviews will pass RE over. Now, in addition, the AS 2 is not truly all BT products across all OS platforms right now, is it? That's a warm fuzzy thing to say but the reality is that it is not.
So, like Doug, please don't take my honest comments as being rude. They are meant to help you make a better product...just as I've helped a number of companies over the years. I have both the AA-55 Zoom BT and the 230 Stick. They work great via USB. But they were marketed and I bought them on the marginal comparison to other candidates because of the bluetooth capability that RE said they had.
I hope your development team can bet this worked out soon, Alex!
Sincerely,
Frank
K4FMH
|
Dear Richard,
Please, specify what kind of information you are interested in?
You wrote about Stick and AntScope for PC.
Stick 230 does not connect via Bluetooth to a PC with AntScope2.
Only Android and iOS now.
Work on this issue is planned for next year.
Sincerely, Alex
14.12.2020 22:57, Richard Lenker KB3YRC
пише:
toggle quoted message
Show quoted text
Hi?? Rig Expert Family
?
I joined to hear about my Rig Stick 230
And nothing for two weeks
I updated it to 1.8 Ver? and have it to the
PC with antscope
?
Richard? KB3YRC
Pennsylvania? USA
?
|
Hi?? Rig Expert Family ? I joined to hear about my Rig Stick 230 And nothing for two weeks I updated it to 1.8 Ver? and have it to the PC with antscope ? Richard? KB3YRC Pennsylvania? USA ?
|
This is a good idea.
Thanks Christian!
toggle quoted message
Show quoted text
Thanks for the immediate response. After installing the drivers
I've got it working immediately! I saw the mention in the
documentation for the drivers on Windows 7. Maybe you can add a
disclaimer to the documentation referring to the drivers in case
installation isn't complete.
Good job!
Thanks,
Christian
|
Re: Bluetooth problems AA-55 Zoom
On Mon, Dec 14, 2020 at 06:21 AM, Alex RigExpert wrote:
Yes indeed. The developers informed me that they have set delays in packet exchange in order to avoid data loss.
Of course, this is not the most efficient solution. But this was done to solve the problem at the moment.
In the future, a different, more optimal solution will be used (for example, a binary protocol, no buffering, etc.)
?
That is unfortunate that they have chosen to set delays in the packet exchange as a "quick fix". There is no need to change the data exchange format to a binary protocol.? The problem is not with the ASCII serial protocol but a buffering problem in the AA-55 Zoom in Bluetooth mode.? Your serial protocol works fine at 9600 bits per second which is the default speed of most Bluetooth hardware modules in serial mode.?? I know this to be true because I took an AA-55 Zoom data file of 500 points and recorded it.? I then played it back by connecting a PC com port to a low-cost HC-05 Bluetooth module with a 9600 bps serial input.? It transferred the 500 points without any errors to AntScope 2 in the Android? and Windows programs. It took 10 seconds for the transfer which is reasonable compared to the 30 seconds it takes with your "quick fix" software.? The buffering could fixed with a simple first-in first-out (FIFO) buffer with input and output pointers.? That way the sweep algorithm could fill the buffer at one rate and the output routine could pull data from the buffer at a rate equal to the Bluetooth serial transmission speed.? This would ensure that the buffer would not overflow or underflow. The other issue which has not been fixed is that AntScope2 for Windows program has problems.? As I noted in my previous report if you don't send a sweep request within a few seconds of starting AntScope2 the program freezes and no data is transferred.? Also AntScope 2 for Windows takes a long time to find the AA-55 in Bluetooth mode on my computer and Frank Howell has reported that it never connects. Alex - I am sorry if I come across as unfriendly in my posts.? I guess I am disappointed and frustrated that I have not been able to reliably use the Bluetooth feature in my AA-55 since I bought it a year ago.? Bluetooth was the main reason I purchased your product. Doug VE7DXK
|
Thanks for the immediate response. After installing the drivers I've got it working immediately! I saw the mention in the documentation for the drivers on Windows 7. Maybe you can add a disclaimer to the documentation referring to the drivers in case installation isn't complete.
Good job!
Thanks,
Christian
|
Re: Bluetooth problems AA-55 Zoom
Dear Doug,
?
Yes indeed. The developers informed me that they have set delays in packet exchange in order to avoid data loss.
Of course, this is not the most efficient solution. But this was done to solve the problem at the moment.
In the future, a different, more optimal solution will be used (for example, a binary protocol, no buffering, etc.)
?
We do not ignore your messages. As this case has shown, it takes more time not to make hasty conclusions and offer a better solution.
?
Thank you again for your assistance.
?
Sincerely yours, Alex
|
Dear Christian,
The TI-3000 interface uses an FTDI chip for which there are
drivers inside the OS or OS installs these drivers automatically.
But sometimes crashes happens, drivers may be missing.
You can install the drivers yourself.
Download here:
Best Regards, Alex
toggle quoted message
Show quoted text
Hi all.
I've got a TI-3000 Audio interface for my Yaesu FT-857. I've a set
it up on Windows 10 (latest updates) and it got recognized.
However when I'm trying to use it with WSJT-X I'm getting an
error. When I look into the Computer Management, I see that there
are drivers missing. According to the product description, it
should not need a driver at all and the initial installation went
through successfully, but there seems to be something missing.
Any suggestions on what I'm doing wrong?
Thanks,
Christian
|
Hi all.
I've got a TI-3000 Audio interface for my Yaesu FT-857. I've a set it up on Windows 10 (latest updates) and it got recognized. However when I'm trying to use it with WSJT-X I'm getting an error. When I look into the Computer Management, I see that there are drivers missing. According to the product description, it should not need a driver at all and the initial installation went through successfully, but there seems to be something missing.
Any suggestions on what I'm doing wrong?
Thanks,
Christian
|
Re: Bluetooth problems AA-55 Zoom
Doug,
I’ll try this weekend. Plus, I’m going to use my more recent Thinkpad Carbon X1 with newer BT as a second variability test. More when I have it!
Frank
---
Frank M. Howell, PhD
Ridgeland, MS
frankmhowell (at) hotmail.com
---
toggle quoted message
Show quoted text
On Dec 11, 2020, at 2:10 PM, Doug VE7DXK <ve7dxk@...> wrote:
?Frank,
I find that the beta AntScope2 program takes a long time to connect to the Zoom when using BTooth. It is almost instantaneous with USB but I have waited 6 or 7 seconds when connecting with Bluetooth. Sometimes it won't connect at all. Make sure you have fresh batteries installed or use a USB power pack.
Try this...
- set up AntScope2 for manual and the desired COM port
- exit AntScope 2
- turn off you AA-55 Zoom if on, wait 20 seconds or so and turn it on
- wait at least 20 seconds for a BT connection
- start Antscope 2 and hopefully it will connect in 10 seconds or so.
You can see that RigExpert has gone quiet again. The only reason they responded to this BT problem is because I contacted the Canadian supplier who sold me the unit and complained about the lack of support and how my emails and groups.io posts were being ignored. He contacted the president of the company and that is why Alex started to respond to the problem. But I have heard nothing from their developers or tech support..
Some time ago they posted with great fanfare on the NanoVNA groups.io that AntScope 2 would support the NanoVNA. They had a buggy release and it was fixed somewhat with promises for a new release. Months went by and they were never heard from again.
I don't hold out much hope for ever getting this BT problem fixed to users satisfaction. We will have to see.
I appreciate you supporting me on this problem.
Doug
On 2020-12-08 13:06 p.m., Frank Howell wrote:
Hi Alex,
Like Doug, I downloaded the 1.1.5 version of AS 2 on my Win 10 laptop. It installs fine. But even using the suggested modifications of the BT settings here () regarding the default ingoing/outgoing BT com ports, I now cannot get my AA-55 Zoom BT to successfully connect to AS 2. It shows being paired in my BT manager in Win 10 but AS 2 does not connect whether under Auto or Manual with the Outgoing com port selected. So, I'm stuck regarding BT connections it seems. USB works fine.
73,
Frank
K4FMH
|
Re: Bluetooth problems AA-55 Zoom
Frank,
I find that the beta AntScope2 program takes a long time to connect to the Zoom when using BTooth. It is almost instantaneous with USB but I have waited 6 or 7 seconds when connecting with Bluetooth. Sometimes it won't connect at all. Make sure you have fresh batteries installed or use a USB power pack.
Try this...
- set up AntScope2 for manual and the desired COM port
- exit AntScope 2
- turn off you AA-55 Zoom if on, wait 20 seconds or so and turn it on
- wait at least 20 seconds for a BT connection
- start Antscope 2 and hopefully it will connect in 10 seconds or so.
You can see that RigExpert has gone quiet again. The only reason they responded to this BT problem is because I contacted the Canadian supplier who sold me the unit and complained about the lack of support and how my emails and groups.io posts were being ignored. He contacted the president of the company and that is why Alex started to respond to the problem. But I have heard nothing from their developers or tech support..
Some time ago they posted with great fanfare on the NanoVNA groups.io that AntScope 2 would support the NanoVNA. They had a buggy release and it was fixed somewhat with promises for a new release. Months went by and they were never heard from again.
I don't hold out much hope for ever getting this BT problem fixed to users satisfaction. We will have to see.
I appreciate you supporting me on this problem.
Doug
toggle quoted message
Show quoted text
On 2020-12-08 13:06 p.m., Frank Howell wrote: Hi Alex,
Like Doug, I downloaded the 1.1.5 version of AS 2 on my Win 10 laptop. It installs fine. But even using the suggested modifications of the BT settings here () regarding the default ingoing/outgoing BT com ports, I now cannot get my AA-55 Zoom BT to successfully connect to AS 2. It shows being paired in my BT manager in Win 10 but AS 2 does not connect whether under Auto or Manual with the Outgoing com port selected. So, I'm stuck regarding BT connections it seems. USB works fine.
73,
Frank
K4FMH
|
Re: Bluetooth problems AA-55 Zoom
|
Re: Bluetooth problems AA-55 Zoom
On Wed, Dec 9, 2020 at 06:14 AM, Alex RigExpert wrote:
Doug, I'd appreciate any help you can give us.
Best regards, Alex
Alex you have my email address and I would be happy to share with your developers what I know? about Bluetooth and the lost data when making AA55-Zomm BT transfers.
?
Here are some comments I hope you find useful.
?
? ? The AA- 55 Zoom is transferring serial data using Standard Bluetooth (not BLE).? Bluetooth serial? mode is a protocol that transfers using the underlying BT RFCOMM protocol? which ensures that the serial data is transferred error-free across the BT link.? The default serial speed into the BT hardware is usually 9600 bits per second but between BT devices is much, much faster.? In fact the serial link can be run at 115,000 bps in some cases if the microprocessor, PC or Android device can buffer data at this speed.
?
? ? I did a 500 frequency point BT transfer from the AA-55 Zoom to an Android protocol analyzer in my tablet.? Each point is one line with approximately 21 characters (depends on frequency value). The total number of characters transferred was 10,296. Characters are sent in serial ASCII with 8 bits plus one stop bit and one start bit. The total time to transfer was 29.12 seconds.? The transfer speed was (10,296 characters*10 bits)/29.12 equals 3535 bits per second.? This is very slow for a Bluetooth connection.
?
? ? A small BT HC-05 module was connected to my PC using a USB to TTL converter.? The BT module has a default serial port input speed of 9600 bits per second (baud).? The 500 data points that were sent by the AA-55 Zoom to the Android tablet in the test above were stored in a test file.? This 500 point data file was then sent across BT to the Android tablet and recorded in the serial BT protocol analyzer.? The transfer ran without errors at the full 9600 bps transfer speed.? This is 3 times faster than the AA-55 Zoom and proves that the Android tablet and software can transfer at this speed.? Similar results occur on a Windows PC and it should be easily possible to go much faster although this was not tested.
?
? ? The original BT transfer problem reported here and in emails to your support group was that data was being lost in bursts.? These bursts were 10 or 11 lines of data or approximately 200 to 250 ASCII characters.? This could be happening in the BT module itself or in the character buffers used by the microprocessor.? ?9600 bps is a pretty slow input rate? for a BT module so I don't suspect a buffering problem inside the module. I suspect it is in the microprocessor code.? Why the problem with Bluetooth and not USB?? The microprocessor is usually sending the data over a high speed USB link and the link is faster than the sweep rate of the analyzer so buffering requirements are minimal.? However when using a slow serial BT link it is possible that the firmware buffers are periodically overflowing with larger transfers (>50 points I found).
In the current 1.25 firmware it is my guess that the RigExpert developers just delay transmission after every character sent or after every line of data to avoid buffer overflow.? This is a simple fix but it slows down the transfer speed considerably.? A better buffer management scheme would permit much faster transfers.? It could be almost as fast as USB with higher BT serial speeds like 38,400.?
?
Alex this is just some input to help resolve the problem.? I look forward to testing your next software and firmware release.
Doug VE7DXK
?
|
Re: Bluetooth problems AA-55 Zoom
Doug, Frank,
Thank you very much for your feedback!
I gave the information to developers for analysis.
Doug, I'd appreciate any help you can give us.
Best regards, Alex
09.12.2020 2:37, Frank Howell пишет:
toggle quoted message
Show quoted text
Alex & Doug,
I got a Samsung Galaxy Tab A tablet today...upgraded to Android 10
upon setup. I downloaded the apk file and installed AS 2. I swept
a couple of antennas, varying the number of points by bandwidth of
the sweep. I can confirm Doug's results about the "slow" data
transfer. At times, very slow. My FW on the AA-55 is 1.25 as per
Alex's recommendation above.
Hope this helps...
Frank
K4FMH
|
Re: Bluetooth problems AA-55 Zoom
Alex & Doug,
I got a Samsung Galaxy Tab A tablet today...upgraded to Android 10 upon setup. I downloaded the apk file and installed AS 2. I swept a couple of antennas, varying the number of points by bandwidth of the sweep. I can confirm Doug's results about the "slow" data transfer. At times, very slow. My FW on the AA-55 is 1.25 as per Alex's recommendation above.
Hope this helps...
Frank
K4FMH
|
Alex RigExpert
K4FMH
Frank K4FMH