Keyboard Shortcuts
Likes
Search
I need your help
Hello all,
I tried to upgrade firmware using original xiegu cable and? following strictly the procedure? described by Radioddity. COM port was? correctly set on the PC .Also on Tera term everything was fine. Memory was? flash but no way? to send any data from PC to Xiegu 5105. It remained in awaiting? mode? for? hours. I disconnected the power cable and now the Xiegu is? switched? off? completely , no way? to power up again.? I 've read other topic in this forum but? didn't find a solution . is there anybody? that can kindly suggest a solution ?? many thanks ! bruno |
By pressing the volume buttons I was able to put again? 5105 in? waiting? connection mode.? I tried another version of Teraterm without? success. The COM port seems? to work correctly. Driver? FTDI? ?seem correctly installed. I tried with another PC but? same? story. Hope someone can suggest me what to try. many thanks in advance
|
Hi Bruno
The last time I flashed the firmware I had similar problems. I solved them by using an earlier version of Teraterm (might have been 96 but need to check my notes). Xiegu doesn't like the latest version for some reason. I also used a high quality USB/Serial bridge for the data connection. Used the Elektor BoB board which has low noise on the data lines compared to some of the other junk out there. Hope this helps. Jim ? G4EQX |
Hi Jim
unfortunately didn't? work? also with 4.96 version. Again it remains? in "? waiting? connection"? ?status? and? it? doesn't? receive anything. The cable? is the original bought from Xiegu Sweden (and paid a fortune) . Drivers? looks? ok . Com port? ?on the device manager looks? also ok. I'm sorry to bother you or anybody? else? if? you have? some? suggestion. It? should be a pity? to put into the bin the Xiegu . Thank you in advance to all . |
What version of Windows do you have?
In the past I used the Xiegu cable with Windows 8 and 10 - no problems. Windows 11 didn't like the Xiegu serial to USB cable. It looked installed but wouldn't work. I assume it is a Prolific driver clash. Tried a few from here but no luck So, I used this, and that worked Jim?? G4EQX |
Hi Jim
thank you for your interest into my problem. I appreciate. My PC is Windows 10. I tried also on an old Windows 8 with same result. The cable I bought? from Xiegu. Eu? (Pile up in Sweden) is? this one ? and it is a FTDI cable . It's recognized? by? Windows 10 and driver correctly installed. I also downloaded drivers from FTDI? ?and installed without any success. Therefore it's not Prolific type of cable. Regarding the elektre board you mention , may I ask you more about the connection ?? I suppose I need to connect a cable with audio jack somehow and on the other side to connect a usb cable to usb connector on the board and? USB plug to PC. Am I right ? power is given by USB port ? Sorry for so many questions but with your help I do hope to resurrect my X5105. Many thanks ! bruno |
Hi Bruno
The Elektor board is the same as the Xiegu cable in principle but requires a little work to hook up to the Xiegu X-5105 The COM port on the radio has three connections which are RX, TX, and ground. The Elektor board has a lot of pins but the ones that are needed are at the opposite end from the USB connector. The pins here are RTS, RXD, TXD, VCCIO, CTS and GND With the exception of VCCIO these are standard modem connectors. You need to patch up: RXD (Elektor) to TXD (X-5105) TXD (Elektor) to RXD (X-5105) GND (Elektor) to GND (X-5105) I used a spare Xiegu plug, wires from the Elektor to a breadboard and croc clips to the Xiegu plug rear pins. You could solder them on too but I decided to keep my plug clean for another use later. Everything worked and I got my Xiegu running again. I do wonder why there was a problem with the Xiegu lead but have not figured that out yet. Like you I tried different operating systems. Windows 11, Windows 10, and even Vista 32-bit. The chipset in your lead is probably FT232 which is similar to the Elektor which uses FT231XQ and the Elektor does have a lot of filtering on the I/O lines and this seemed to help. Shouldn't be much difference between them for this application. The FT231XQ is a newer device so perhaps the Windows driver is expecting that and FT232 is in a backwards compatible mode. I also noticed that Teraterm 96 seems to be what the Xiegu needs and Teraterm 106 causes problems. No idea why. Hope this helps. Jim?? G4EQX |
Bruno,
|
Thank you david for your interest in my? "trouble". The problem is that I didn't have tthe cable that came with the radio. I bought it second hand the owner told me that there was no cable. For this reason I bought from Xiegu.EU? in Sweden? the original Serial cable, even if it was? so expensive . Anyhow your suggestion remain valid . I? will keep it as last chance? after having tried other? cables.? Hope that simply the? cable I used? wis defective.??
Thanks again for your support. Bruno |
Hi Jim,
just to be sure that I've well understood. RXD,TXD,GND marks? on the board? are printed on the edge . Good.? ?Instead for? X5105? should I consider what is? shown in the instruction manual? for the CIV interface on the 3.5 mm Jack ?? practically RXD on the board connected to TXD on the 3.5 as shown ? many thanks Jim for a kind confirmation. Many thanks ! In the meantime I discovered why the Original Xiegu cable is not? working. They have utilized a FTDI clone. The? ?FTDI driver on windows is? disabling the chip .The Company? FTDI is? trying to defend itself in this way. I can understand them, I understand less Xiegu .? Apparently even with an old? driver it's not possible to disable this protection (I Tried). Reading the "driver events? register" on windows? ?, this situation is quite evident.?? |
¿ªÔÆÌåÓýHi Bruno Look at things this way: The X5105 is awaiting a signal on its RXD pin, so the Elektor will send a signal via its TXD pin. If the X5105 acknowledges a command it will send a signal to its TXD pin on the board, and the Elektor will be able to receive that on its RXD pin. If you accidentally wire it up wrong nothing bad will happen.
Just swap the RXD and TXD wires at the Elektor end. The chip in Elektor is definitely not a clone. Reckon you are nearly there. Jim?? G4EQX On 01/08/2023 15:50, Bruno wrote:
Hi Jim, |
Thank you Jim for the explanation. As soon as I have the board I will try .? In the meantime , after my? complaint? with Xiegu Europe, they are shipping me for free another "original" cable. I'm afraid that? also this cable will "react" in the same? way if? inside there is? still a clone. But since Xiegu? was? offerinng? me a new cable I? will try.? Not too many hopes. But Elektor board remains? the solution. I'll let all know.
|
Thank you Kevin for your? suggestion. No, I don't have other terminal software as long as I remember on the main PC. I've tested the cable? on 4? different PC with the same? result. But on all 4 PC's , now that you are telling me that, I've a software called VAC, Virtual audio cable, that I use? for connecting an SDR? to PC for FT8 purpose. May be is interfering with Virtual Com port ?
In particular on 1 PC, the oldest still with Windows 8,? I? have very few? programs inside, and VAC is there. I? think I? will try to uninstall it and see what happen. Never know. Thnaks? again. Bruno |