Re: [chirp_users] vx-6r redux
On 11/07/2022 20:00, chirp_users-request@intrepid.danplanet.com wrote:
I don't really understand why windows with the latest version would not work or mac OS with the latest version would not work. But this old version on linux did.
What data lead were you using? If it uses a Prolific USB-Serial bridge, it may be an old type of chip, or a clone. Either way Windows (and many Mac systems) will not use them. (Without compromising the security of your system by blocking automatic updates and then manually installing an earlier driver suite.)
But Linux (even recent distro's) use them just fine, regardless. Had similar issues locally, with a group that uses dozens of Baofeng radios. All the interface leads used "hookey" chipsets. A Windows box and a Mac, both failed. My old Dell running Mint, "just worked"...
Counterfeit IC's are rife in that part of the gadget after market.
Take care.
Dave G0WBX(G8KBV)
Dave
That is possible. Windows and linux identified my chip as made by FTDI. I wasn't sure how to check on mac. I was/am using a CT-1 from ttl2usb dot com. Hard to tell if ttl2usb dot com sourced a bad chip or not. I have had this serial device for quite a few years. But the last time I used it I was using windows 7.
-Nic
On Mon, Jul 11, 2022 at 2:35 PM Dave B via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
On 11/07/2022 20:00, chirp_users-request@intrepid.danplanet.com wrote:
I don't really understand why windows with the latest version would not work or mac OS with the latest version would not work. But this old
version
on linux did.
What data lead were you using? If it uses a Prolific USB-Serial bridge, it may be an old type of chip, or a clone. Either way Windows (and many Mac systems) will not use them. (Without compromising the security of your system by blocking automatic updates and then manually installing an earlier driver suite.)
But Linux (even recent distro's) use them just fine, regardless. Had similar issues locally, with a group that uses dozens of Baofeng radios. All the interface leads used "hookey" chipsets. A Windows box and a Mac, both failed. My old Dell running Mint, "just worked"...
Counterfeit IC's are rife in that part of the gadget after market.
Take care.
Dave G0WBX(G8KBV)
-- Created on and sent from a Unix like PC running and using free and open source software:
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nic at nicheath@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
There were even some Fake FTDI chips about a few years ago.
In Windows, use the Device Manager to view the list of connected devices. Look under printer & serial devices, if a Serial device is marked with a yellow warning triangle with a ! in the middle, there is a problem between the driver and the device itself.
I've come across some fake IC's that were marked up as FTDI, but identified themselves to the OS as Prolific! So, obvious fakes. (Though on a Linux box, they did work OK as Prolific devices.) That was for a work project too, we got our refund though.
(I've given up with Windows for my own personal and Ham useage, no regrets...)
I wanted FTDI specifically, as you can program the behaviour of the status lines, and also the "sense" of the data lines. I needed the TX data line inverted from normal (to accommodate an Fibre Optic sender, but the RX line left as default, as the FO RX device doesn't invert the data, in that configuration, with the pre-existing TTL - Fibre interface boards I had to use.)
The Fake FTDI chips allowed me to do that without error, but did't actually make the changes, or "stick" the settings in their internal memory.
If I need any USB-Serial bridge products, I now only buy from FTDI direct, or from reputable sources (but of course, the cost is higher than the "other" sources.)
You get what you pay for.
73. Nic.
Dave G0WBX(G8KBV)
On 11/07/2022 20:47, Nic Heath wrote:
Dave
That is possible. Windows and linux identified my chip as made by FTDI. I wasn't sure how to check on mac. I was/am using a CT-1 from ttl2usb dot com. Hard to tell if ttl2usb dot com sourced a bad chip or not. I have had this serial device for quite a few years. But the last time I used it I was using windows 7.
-Nic
On Mon, Jul 11, 2022 at 2:35 PM Dave B via chirp_users chirp_users@intrepid.danplanet.com wrote:
On 11/07/2022 20:00, chirp_users-request@intrepid.danplanet.com wrote: > I don't really understand why windows with the latest version would not > work or mac OS with the latest version would not work. But this old version > on linux did. What data lead were you using? If it uses a Prolific USB-Serial bridge, it may be an old type of chip, or a clone. Either way Windows (and many Mac systems) will not use them. (Without compromising the security of your system by blocking automatic updates and then manually installing an earlier driver suite.) But Linux (even recent distro's) use them just fine, regardless. Had similar issues locally, with a group that uses dozens of Baofeng radios. All the interface leads used "hookey" chipsets. A Windows box and a Mac, both failed. My old Dell running Mint, "just worked"... Counterfeit IC's are rife in that part of the gadget after market. Take care. Dave G0WBX(G8KBV) -- Created on and sent from a Unix like PC running and using free and open source software: _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nic at nicheath@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Local hams around here that are avid MAC users all seem to have simple windows laptops/desktops just to run updates & other odd software that requires Windows. I have no issues w/ Windows, but I've used it for decades and supported it for a handful of years, so I do OK with it. I also run Mac & Linux (and Solaris), but it's hard for me to pick a favorite.
Ken, N2VIP
On Jul 11, 2022, at 16:21, Dave B via chirp_users chirp_users@intrepid.danplanet.com wrote:
(I've given up with Windows for my own personal and Ham useage, no regrets...)
Hi Nic - on any Linux system - and the Mac is Linux based - try typing in a terminal window.
dmesg
This might require root privilege
At the end of the of output in the terminal window will be the device and system port being used.
For example, in the case where you unplug the device and plug it back in, on my system it prints out
[755460.454330] ftdi_sio 1-1.3:1.0: FTDI USB Serial Device converter detected [755460.455664] usb 1-1.3: Detected FT232RL [755460.459439] usb 1-1.3: Number of endpoints 2 [755460.463865] usb 1-1.3: Endpoint 1 MaxPacketSize 64 [755460.468770] usb 1-1.3: Endpoint 2 MaxPacketSize 64 [755460.473483] usb 1-1.3: Setting MaxPacketSize 64 [755460.478739] usb 1-1.3: FTDI USB Serial Device converter now attached to ttyUSB0
See https://krypted.com/mac-security/troubleshooting-mac-os-x-kernels-w-dmesg/
-- Cinaed
On 7/11/22 12:47, Nic Heath wrote:
Dave
That is possible. Windows and linux identified my chip as made by FTDI. I wasn't sure how to check on mac. I was/am using a CT-1 from ttl2usb dot com. Hard to tell if ttl2usb dot com sourced a bad chip or not. I have had this serial device for quite a few years. But the last time I used it I was using windows 7.
-Nic
On Mon, Jul 11, 2022 at 2:35 PM Dave B via chirp_users chirp_users@intrepid.danplanet.com wrote:
On 11/07/2022 20:00, chirp_users-request@intrepid.danplanet.com wrote: > I don't really understand why windows with the latest version would not > work or mac OS with the latest version would not work. But this old version > on linux did. What data lead were you using? If it uses a Prolific USB-Serial bridge, it may be an old type of chip, or a clone. Either way Windows (and many Mac systems) will not use them. (Without compromising the security of your system by blocking automatic updates and then manually installing an earlier driver suite.) But Linux (even recent distro's) use them just fine, regardless. Had similar issues locally, with a group that uses dozens of Baofeng radios. All the interface leads used "hookey" chipsets. A Windows box and a Mac, both failed. My old Dell running Mint, "just worked"... Counterfeit IC's are rife in that part of the gadget after market. Take care. Dave G0WBX(G8KBV) -- Created on and sent from a Unix like PC running and using free and open source software: _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nic at nicheath@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to cinaed smson atcinaed.simson@gmail.com To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please emailchirp_users-owner@intrepid.danplanet.com
Just for the record, Mac OS X is BSD based, not Linux. Two different beasts.
On Mon, Jul 11, 2022 at 8:27 PM Cinaed Simson cinaed.simson@gmail.com wrote:
Hi Nic - on any Linux system - and the Mac is Linux based - try typing in a terminal window.
Still part of the *nix family, I can deal with the command line of a mac, windows.... Don't ask...
But yes Mac is based on BSD, so it is a rock solid (the BSD part) foundation.
On Mon, Jul 11, 2022 at 9:43 PM Scott Lopez scottjl@gmail.com wrote:
Just for the record, Mac OS X is BSD based, not Linux. Two different beasts.
On Mon, Jul 11, 2022 at 8:27 PM Cinaed Simson cinaed.simson@gmail.com wrote:
Hi Nic - on any Linux system - and the Mac is Linux based - try typing in a terminal window.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
All
So I believe I have discovered the issue. I used my other FTDI USB to serial adapter which just has a simple pin header on it. I wired it up using a spare diode and 10k resistor for a pull up for single wire comm and it consistently works even in windows with the latest version of CHIRP.
I took apart the ttl2usb dot com device and took a look at what I had been sold. It looks as though best I can tell is that I'm only getting 2.8V on what I expect to be a 3.3.V pull up on both the TX and RX while in idle. So something is definitely amiss with the ttl2usb dot com supposed Yaesu interface. Must have been sheer luck getting it to work at all on my linux machine.
Does anyone have a link to a canonical (way it should actually be done) to turn serial into a one wire comm for the vx6-r a specific pull up resistor/diode combination?
It's pretty annoying that this ttl2usb dot com device I bought ages ago either broke with age (doubtful) was wrong the whole time and I just got lucky the levels worked every once in a great while.
-Nic
On Tue, Jul 12, 2022 at 4:24 PM Chuck Hast kp4djt@gmail.com wrote:
Still part of the *nix family, I can deal with the command line of a mac, windows.... Don't ask...
But yes Mac is based on BSD, so it is a rock solid (the BSD part) foundation.
On Mon, Jul 11, 2022 at 9:43 PM Scott Lopez scottjl@gmail.com wrote:
Just for the record, Mac OS X is BSD based, not Linux. Two different beasts.
On Mon, Jul 11, 2022 at 8:27 PM Cinaed Simson cinaed.simson@gmail.com wrote:
Hi Nic - on any Linux system - and the Mac is Linux based - try typing in a terminal window.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
--
Chuck -- KP4DJT HamHotline # 11259 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nic at nicheath@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Oh there also seems to be an unrecognized function named "pring" on line 826 of the vx6.py driver tarball I downloaded had hg hash f681fdfb94dd in the name. My other emails never came through from before but I did want to put that out there that that was in the logs.
def get_settings(self): try: return self._get_settings() except: import traceback pring(traceback.format_exc()) return None
On Tue, Jul 12, 2022 at 8:15 PM Nic Heath nicheath@gmail.com wrote:
All
So I believe I have discovered the issue. I used my other FTDI USB to serial adapter which just has a simple pin header on it. I wired it up using a spare diode and 10k resistor for a pull up for single wire comm and it consistently works even in windows with the latest version of CHIRP.
I took apart the ttl2usb dot com device and took a look at what I had been sold. It looks as though best I can tell is that I'm only getting 2.8V on what I expect to be a 3.3.V pull up on both the TX and RX while in idle. So something is definitely amiss with the ttl2usb dot com supposed Yaesu interface. Must have been sheer luck getting it to work at all on my linux machine.
Does anyone have a link to a canonical (way it should actually be done) to turn serial into a one wire comm for the vx6-r a specific pull up resistor/diode combination?
It's pretty annoying that this ttl2usb dot com device I bought ages ago either broke with age (doubtful) was wrong the whole time and I just got lucky the levels worked every once in a great while.
-Nic
On Tue, Jul 12, 2022 at 4:24 PM Chuck Hast kp4djt@gmail.com wrote:
Still part of the *nix family, I can deal with the command line of a mac, windows.... Don't ask...
But yes Mac is based on BSD, so it is a rock solid (the BSD part) foundation.
On Mon, Jul 11, 2022 at 9:43 PM Scott Lopez scottjl@gmail.com wrote:
Just for the record, Mac OS X is BSD based, not Linux. Two different beasts.
On Mon, Jul 11, 2022 at 8:27 PM Cinaed Simson cinaed.simson@gmail.com wrote:
Hi Nic - on any Linux system - and the Mac is Linux based - try typing in a terminal window.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
--
Chuck -- KP4DJT HamHotline # 11259 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nic at nicheath@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
participants (6)
-
Chuck Hast -
Cinaed Simson -
Dave B -
Ken Hansen -
Nic Heath -
Scott Lopez