¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Confused RE: How to re-image the Quadra


 

Hey Y'all... this might be a stupid question, but I wasn't able to find out the process to do this on the Inovato website or the forum.? Hopefully someone can help me.? I have a Quadra that I initially set up with the Inovato image and it works dandy.? So I downloaded Dave's great HamPi for the Quadra. I unpacked it. I wrote it to an SD card. I unplugged the Quadra, put the SD card in and thought that it would write a new OS image from that card, but all I ever get is the same old Inovato image.? What's the secret sauce or handshake on this thing? Thanks ahead of time
73//KK0DJ


 

ARGGGHHHH... it was way too simple of a fix - just select the "pi" user instead of the "quadra" user and a different environment (HamPi for Quadra) comes up.? Sometimes the simplest things can confuse!? No help needed now!
THanks
73
Dennis
KK0DJ


 

I'm working on a more clear and intuitive login for the next version of HamIQ. I took a lot of shortcuts and accumulated a bunch of "technical debt" while rushing through the first image... That's why it's beta. :-)

73,

On Sat, Nov 26, 2022 at 1:37 PM KK0DJ <deejay52@...> wrote:
ARGGGHHHH... it was way too simple of a fix - just select the "pi" user instead of the "quadra" user and a different environment (HamPi for Quadra) comes up.? Sometimes the simplest things can confuse!? No help needed now!
THanks
73
Dennis
KK0DJ


--
-- Dave,?? ? ? ? ? ? ? ? ? ? ? ?Technical Specialist,??--
--?? Lifetime Member:?////?--
--??--


ve3ega
 

Dave, has Dennis pointed out its the simplest of things that confuse us!
My personal 'Gotchya' was exactly the same as Dennis's - I kept looking at the Quadra Log In Box and entering the password 'raspberry' many times and wondering what I had done wrong!
eventually, my mouse hovered above the letters Pi (which I thought was just background!) and "VOILA" a HamPi log in!!

"The rest, they say is history" (at least on my part - and I'm only 2 Days into this 'Ham's-dream' software suite!)

Thanks Dave for such a 'beautiful thing'..

73

Terry


 

Terry,

Glad you figured it out.

This initial image is only a beta. It comes with its own shortcomings and pitfalls.

I literally built it as an (almost) all-nighter. I'm surprised it functions as well as it does, actually, considering the amount of QA which went into it.

The next version will be much more polished.

73,

On Sat, Nov 26, 2022 at 8:53 PM ve3ega <ve3ega@...> wrote:
Dave, has Dennis pointed out its the simplest of things that confuse us!
My personal 'Gotchya' was exactly the same as Dennis's - I kept looking at the Quadra Log In Box and entering the password 'raspberry' many times and wondering what I had done wrong!
eventually, my mouse hovered above the letters Pi (which I thought was just background!) and "VOILA" a HamPi log in!!

"The rest, they say is history" (at least on my part - and I'm only 2 Days into this 'Ham's-dream' software suite!)

Thanks Dave for such a 'beautiful thing'..

73

Terry


--
-- Dave,?? ? ? ? ? ? ? ? ? ? ? ?Technical Specialist,??--
--?? Lifetime Member:?////?--
--??--


 

Don't worry, I had the same issue when I first loaded.?

73
Don Poaps
New Westminster, BC
VA7DGP DATA
VA7QU ? VOICE


Winlink:?va7dgp@...
Subject://wl2k ? ? ? ? ?

ALLSTAR ?530780
Hamshack Hotline
5971
Mid-Island Phone Mesh
2210
2232

? ? ? ? ? ? ? ? ? ?


On Sat, Nov 26, 2022 at 10:37 AM KK0DJ <deejay52@...> wrote:
ARGGGHHHH... it was way too simple of a fix - just select the "pi" user instead of the "quadra" user and a different environment (HamPi for Quadra) comes up.? Sometimes the simplest things can confuse!? No help needed now!
THanks
73
Dennis
KK0DJ


 

¿ªÔÆÌåÓý

As a suggestion, is it possible to include the FTDI drivers for CHIRP? ?

Have two HT (Baofeng and Yaesu FT-60). ?The cable for the Baofeng works without any issue, but being new to LINUX, I am having difficulty trying to get the FTDI cable for the Yaesu to work. ?Trying to install Linux D2XX drivers from the ?site but have not been successful. ?Maybe missing several steps in coding.

Andrew

On Nov 26, 2022, at 9:17 PM, Dave Slotter, W3DJS <slotter@...> wrote:

Terry,

Glad you figured it out.

This initial image is only a?beta. It comes with its own shortcomings and pitfalls.

I literally built it as an (almost) all-nighter. I'm surprised it functions as well as it does, actually, considering the amount of QA which went into it.

The next version will be much more polished.

73,

On Sat, Nov 26, 2022 at 8:53 PM ve3ega <ve3ega@...> wrote:
Dave, has Dennis pointed out its the simplest of things that confuse us!
My personal 'Gotchya' was exactly the same as Dennis's - I kept looking at the Quadra Log In Box and entering the password 'raspberry' many times and wondering what I had done wrong!
eventually, my mouse hovered above the letters Pi (which I thought was just background!) and "VOILA" a HamPi log in!!

"The rest, they say is history" (at least on my part - and I'm only 2 Days into this 'Ham's-dream' software suite!)

Thanks Dave for such a 'beautiful thing'..

73

Terry



--?
-- Dave,?? ? ? ? ? ? ? ? ? ? ? ?Technical Specialist,??--
--?? Lifetime Member:?////?--
--??--


 

Andrew,

I trust you are aware of the FTDI chip and cabe scandal / fiasco of
several years back. As I recall from those times of trouble, only
Kenwood-branded cables could be relied upon to work reliably. I have
my own personal story about this subject, but it's probably
inappropriate for this forum.

73
Jim N6OTQ

On Sun, Nov 27, 2022 at 10:25 AM Andrew <averacpa@...> wrote:

As a suggestion, is it possible to include the FTDI drivers for CHIRP?

Have two HT (Baofeng and Yaesu FT-60). The cable for the Baofeng works without any issue, but being new to LINUX, I am having difficulty trying to get the FTDI cable for the Yaesu to work. Trying to install Linux D2XX drivers from the www.ftdichip.com site but have not been successful. Maybe missing several steps in coding.

Andrew


 

I am afraid I am not aware of that.

I do know that my cable works with Chirp on Windows 10, so the issue is with finding the right driver (and proper install) to work.

On Nov 27, 2022, at 11:59, Jim Strohm <jim.strohm@...> wrote:

?Andrew,

I trust you are aware of the FTDI chip and cabe scandal / fiasco of
several years back. As I recall from those times of trouble, only
Kenwood-branded cables could be relied upon to work reliably. I have
my own personal story about this subject, but it's probably
inappropriate for this forum.

73
Jim N6OTQ


On Sun, Nov 27, 2022 at 10:25 AM Andrew <averacpa@...> wrote:

As a suggestion, is it possible to include the FTDI drivers for CHIRP?

Have two HT (Baofeng and Yaesu FT-60). The cable for the Baofeng works without any issue, but being new to LINUX, I am having difficulty trying to get the FTDI cable for the Yaesu to work. Trying to install Linux D2XX drivers from the www.ftdichip.com site but have not been successful. Maybe missing several steps in coding.

Andrew




 

The simplified and sanitized version is that some company in China
pirated the FTDI chipset in the cable, and flooded the market with
cheap counterfeit knock-offs, which were adopted by all the
beancounter-managed companies that used FTDI features. Predictably,
FTDI took umbrage and "bricked" the counterfeits. I'm not familiar
with the technical details of how this was done, but all the knockoff
cables suddenly became useful only as bungee cords, except that they
didn't stretch very well.

My personal stake in this -- I bought a cheap Chinese handi-talkie
intended as a new-ham freebie "welcome to our brotherhood" giveaway.
This was just after the bricking occurred but before it became common
knowledge. The HT came with a counterfeit-chip programming cable,
branded with the HT company logo. As it happens, this HT had a
"feature" that made programming it through the front panel nearly
impossible from a usability standpoint, but it didn't really matter
because it wouldn't save the programming when the HT was turned off.

The US vendor that supplied the HT was the sole authorized US
distributor for the brand, and I was in personal contact with the
owner, CEO, and chief bottle-washer about the fact that the original
cable wouldn't program my radio. His "fix"? He personally sent me a
new replacement cable with the company logo that was supposed to have
a genuine FTDI chip. He knew about the counterfeit FTDI chip problem
almost from Day One. The diabolic part for me was that the
counterfeit cables appeared to work perfectly until it was time to hit
"save".

His fix? Well, not so much of a fix. The new cable worked exactly
like the old fix.

Ultimately I bought a Kenwood cable, which worked perfectly and solved
the problem instantly. It cost almost as much as the cheap Chinese
HT, NOT counting the months of my wasted time that I'll never get
back.

Now I'm left with an HT I've never used and never will use, because
the affair was too distasteful in too many respects. I also have two
cables with counterfeit FTDI chips. The sole bright side is that I
have a cable with a genuine FTDI chip -- that works with the old
drivers as well as with the new drivers, as do all the genuine FTDI
cables, as far as I've seen.

So as far as I can tell, this never was a driver issue, except that
perhaps the drivers were part of the highly successful "bricking"
exploit, or else now somebody has implemented an FTDI client that's
not fully compliant with all of FTDI's API.

If I've got any of this wrong, or if anybody can add information to
the party (especially how FTDI bricked the counterfeit chips), please
speak up promptly.

73
Jim N6OTQ

On Sun, Nov 27, 2022 at 11:54 AM Andrew <averacpa@...> wrote:

I am afraid I am not aware of that.

I do know that my cable works with Chirp on Windows 10, so the issue is with finding the right driver (and proper install) to work.


 

Hi JIm,

Thanks for the information on the FTDI history.

I got into Ham Radio around September of 2019 going the cheap Baofeng route. After a couple of months I upgraded to the Yaesu FT-60. I run CHIRP on Windows 10 on a Mac Intel machine using VMware. Been doing this for quite a few years without any issues. Originally, I did have an issues with the cable which was ultimately resolved when I bought a better one that supposedly had the right chipset. During the last couple of years, my interest in Ham Radio has been minor although I eventually got my Extra license.

Although I can run most of the PC programs on my Mac, Apple has switched to their silicon M series chips which make running Windows a much harder going forward. CHIRP does not work well in Mac OS and my Intel based Mac computer is getting quite old and new ones are getting quite expensive let alone not fully compatible with Ham Radio related software. When the Inovato machine came out, I thought that this is a great inexpensive solution for my Ham Radio needs as now being retired my interest has perked up to do long distance low power communications (still sorting out the details).

So, are you suggesting that a Kenwood cable would work without any additional coding or drivers with the Inovato? Trying to find an easy solution to at least be able to program the radios with a computer.

As I previously mentioned, my Baofeng UV-82HP brand cable works perfectly with Inovato. The cable I have for the Yaesu FT-60 does not work even though it works perfectly using Windows. (Don¡¯t know the brand but the device manager in Windows defines it as a FT232R USB UART). I removed Brltty as suggested by another member and that resulted in the cable appearing to work, but giving this error message: Failed to communicate with radio: can only concanate str (not "bytes") to str.

So that is where I stand for now.

Thanks,

Andrew

On Nov 27, 2022, at 1:59 PM, Jim Strohm <jim.strohm@...> wrote:

The simplified and sanitized version is that some company in China
pirated the FTDI chipset in the cable, and flooded the market with
cheap counterfeit knock-offs, which were adopted by all the
beancounter-managed companies that used FTDI features. Predictably,
FTDI took umbrage and "bricked" the counterfeits. I'm not familiar
with the technical details of how this was done, but all the knockoff
cables suddenly became useful only as bungee cords, except that they
didn't stretch very well.

My personal stake in this -- I bought a cheap Chinese handi-talkie
intended as a new-ham freebie "welcome to our brotherhood" giveaway.
This was just after the bricking occurred but before it became common
knowledge. The HT came with a counterfeit-chip programming cable,
branded with the HT company logo. As it happens, this HT had a
"feature" that made programming it through the front panel nearly
impossible from a usability standpoint, but it didn't really matter
because it wouldn't save the programming when the HT was turned off.

The US vendor that supplied the HT was the sole authorized US
distributor for the brand, and I was in personal contact with the
owner, CEO, and chief bottle-washer about the fact that the original
cable wouldn't program my radio. His "fix"? He personally sent me a
new replacement cable with the company logo that was supposed to have
a genuine FTDI chip. He knew about the counterfeit FTDI chip problem
almost from Day One. The diabolic part for me was that the
counterfeit cables appeared to work perfectly until it was time to hit
"save".

His fix? Well, not so much of a fix. The new cable worked exactly
like the old fix.

Ultimately I bought a Kenwood cable, which worked perfectly and solved
the problem instantly. It cost almost as much as the cheap Chinese
HT, NOT counting the months of my wasted time that I'll never get
back.

Now I'm left with an HT I've never used and never will use, because
the affair was too distasteful in too many respects. I also have two
cables with counterfeit FTDI chips. The sole bright side is that I
have a cable with a genuine FTDI chip -- that works with the old
drivers as well as with the new drivers, as do all the genuine FTDI
cables, as far as I've seen.

So as far as I can tell, this never was a driver issue, except that
perhaps the drivers were part of the highly successful "bricking"
exploit, or else now somebody has implemented an FTDI client that's
not fully compliant with all of FTDI's API.

If I've got any of this wrong, or if anybody can add information to
the party (especially how FTDI bricked the counterfeit chips), please
speak up promptly.

73
Jim N6OTQ


On Sun, Nov 27, 2022 at 11:54 AM Andrew <averacpa@...> wrote:

I am afraid I am not aware of that.

I do know that my cable works with Chirp on Windows 10, so the issue is with finding the right driver (and proper install) to work.




 

I'm obviously missing something.? I flashed the card, put it in the USB drive and booted the Quadra.? I don't see a pi user, or any way to login as anything other than the quadra user.?


 

David,

How did you flash the card?

On Sat, Dec 3, 2022 at 10:57 AM David Empey, VE3KVR <david@...> wrote:
I'm obviously missing something.? I flashed the card, put it in the USB drive and booted the Quadra.? I don't see a pi user, or any way to login as anything other than the quadra user.?


--
-- Dave,?? ? ? ? ? ? ? ? ? ? ? ?Technical Specialist,??--
--?? Lifetime Member:?////?--
--??--


Don--AE4DW
 

On Sat, Dec 3, 2022 at 10:57 AM, David Empey, VE3KVR wrote:
I'm obviously missing something.? I flashed the card, put it in the USB drive and booted the Quadra.? I don't see a pi user, or any way to login as anything other than the quadra user.?
USB drive? I'm assuming you mean you put it in the SD card slot...?


 

¿ªÔÆÌåÓý

I¡¯ve been using the Pi too long.? I was putting the card in a reader and into the USB drive, not using the card slot.? Thanks AE4DW for pointing that out!? In my defence, I¡¯m monkeying with this while off sick to keep busy.? I¡¯m not usually this dense!

?

Now that its working¡­? Cool little device, and it frees up a Pi for other uses.? Thanks for porting it, Dave.

?

Dave

?

From: [email protected] <[email protected]> On Behalf Of Dave Slotter, W3DJS
Sent: December 3, 2022 12:28 PM
To: [email protected]
Subject: Re: [Inovato-Quadra-4-HamRadio] Confused RE: How to re-image the Quadra

?

David,

?

How did you flash the card?

?

On Sat, Dec 3, 2022 at 10:57 AM David Empey, VE3KVR <david@...> wrote:

I'm obviously missing something.? I flashed the card, put it in the USB drive and booted the Quadra.? I don't see a pi user, or any way to login as anything other than the quadra user.?


--
-- Dave,?? ? ? ? ? ? ? ? ? ? ? ?Technical Specialist,??--
--?? Lifetime Member:?////?--
--??--


 

When I boot Ham-Pi from the sd card, it looks like I have two separate linux boxes available -- the one with Ham-Pi installed and the one with the standard Quadra software installed. Is that right?

I installed RealVNC on the Quadra machine, and that worked well. Then I booted off the Ham-Pi card and my VNC client couldn't find either the Quadra box or the Ham-Pi box. So I guessed that I needed to install RealVNC on the Ham-Pi box, but the install failed. (See attached file.) Can anybody clue me in on what's going on here or what mistake I'm making.

BTW, flashing the Ham-Pi image has been a problem for me. Win32DiskImager goes through the whole process, including a successful validation, in about ten minutes. But the cards don't seem to boot at all. Balena Etcher takes much longer (about 40 minutes including validation),? and then at the very end it says the flash failed . Nonetheless the cards work; i.e., Ham-Pi loads.

In all cases, I have been booting with the video monitor attached.


 

I forgot to attach the log of the failed RealVNC install.


 

What size card are you trying to flash HamPi on?? It requires a minimum of 15.6gb...I use a 32gb card. And for the recod, HamPi/Hamclock is incredible!!
?
73,
Danny? NF4J

--
73,
Danny Bush NF4J