Ch340 Driver For Mac Catalina

| 17-08-2021
[RAND-1-100] Comments

Demo Video download how to work with the camera without shutter cable in win system

If your controller is marked as FT232 in packing list,please download driver from FTDI’s website (All new controller since about 2019 Jan is FT232 type).Please choose the corresponding file for your system.

Please install winrar program first to open this rar file.If you do not have winrar,please use free software 7-zip orRAR File Open Knife

Ch340 Driver For Mac Catalina

Other format of control and driver 7Z format, Zip format.Please choose “still run”if windows 10 popup a notification after you double click the exe file.

It can work in Win XP，Win7,Win vista,Win 8,Win 10

Please install driver first,ch341ser.exe ,then extract the whole wemacro folder to your computer.Double click wemacro.exe to run.

I cannot even use High Sierra because of driver (and Java) issues. MacOS has become more restrictive about 3d party kernel extensions or kexts. 'They act as drivers — if you like a Windows analogy — and give access to your Mac’s hardware.' Something done on previous macOS that was inherited by Catalina update could be at issue. NEJE Master 2s max Laser Engraver / Cutter. Application:photo engraving, wood marking, paper cutting, leather cutting, plywood cutting(3-5mm). Bluetooth: Yes Software: NEJE Android APP, NEJE Scanner, NEJE Wireless APP for iOS, macOS, NEJE Software for windows,Benbox, LaserGRBL with GRBL1.1f, Lightburn, OFF-line.

Notice:Some firewall software may ban the installation of driver or control,you can add them into trust list. Press “F4” to swtich language.(chinese and english)

Bluetooth control on android phone and PC control by usb cable can not be operated in the same time.

Notice!Please enable location function(GPS) on Android 10 phone.Open bluetooth function on your phone and visible to all nearby bluetooth device,wait few seconds it will connect automatically.

Mac OS USB and Bluetooth control download (This program work with Mac’s USB port and Bluetooth connection. Please install USB driver first.Last updated in 2018 July 5，tested with MacOS 10.12, 10.13, 10.14, 10.15 and 11.0.1).The bluetooth on Mac should be 4.0 at least.About this mac—>system report—> HCI version at least 0X6

If you macOS is Mojave and later MacOS,please try directly use USB control program without install drive.Apple already build in drivers for CH340 and FT232 in macOS.It’s compatible with Catalina or BigSur system.

4,Controller Firmware Update:

Ch340 Driver Mac Catalina

If your controller is earlier than middle of 2017 May,and want to be compatible with Helicon Remote,please follow the guide as below
(The tools is windows only)
https://www.wemacro.com/wp/wp-content/uploads/updatefirmwareguidev14.pdf
Please send email to us if there is any problem about updating william@wemacro.com

Please notice all controllers after 2017 May,are all firmware version 14.There is no need to update it if your order is later than 2017 May 15th.

NanoVNA-Saver 0.1.3 MAC

Usb Ch340 Driver Windows 10

#5286

Colin, which version of macOS and how did you set up the USB ports?
Tried it here with Catalina but some problem finding the device on the USB…
Dana VE3DS
toggle quoted messageShow quoted text
On Oct 19, 2019, at 20:11, zl2arl <colin.larsen@gmail.com> wrote:
I've just done the MacOS install, went smoothly, all I had to do was adjust
the font size up a bit ;)
On Sun, 20 Oct 2019, 12:49 W5DXP, <w5dxp@arrl.net> wrote:
That sure does help, Rune. I was using it on my mobile system and my wifi
doesn't reach that far. It would have never occurred to me that Saver
needed the internet. Thanks very much. Do you have any idea how fast one
has to be to get that screen-capture while Saver is shutting down?
Displaying that screen for longer than one millisecond would help. :)
#5352

Hello Dana,
I have been running most of the recent releases of NanoVNA-Saver on my iMac under Mojave 10.14.6. I declined the upgrade to Catalina because several of my expensive software purchases would no longer work. The procedure I use is to plug the NanoVNA into my MAC, turn on the NanoVNA and then launch the Saver program V0.1.3. When the screen paints the USB port is already properly identified and I simply select 'Connect to nanoVNA'. It all works perfectly and has for every release of Saver that I tried starting back at about V0.0.6.
Again, this is all under Mojave, not Catalina. If you find the correct incantation for Catalina please let us all know.
Good luck,
Larry, AE5CZ
#5353

Hmmm, Larry, so it may be a Catalina issue as it doesn’t find the usb…
I’ll try it on Mojave and see if that works…thanks for the comments.
Oh by the way what version of Python are you using??
Dana Ve3DS
toggle quoted messageShow quoted text
On Oct 20, 2019, at 13:41, Larry Goga <lgoga@swcp.com> wrote:
Hello Dana,
I have been running most of the recent releases of NanoVNA-Saver on my iMac under Mojave 10.14.6. I declined the upgrade to Catalina because several of my expensive software purchases would no longer work. The procedure I use is to plug the NanoVNA into my MAC, turn on the NanoVNA and then launch the Saver program V0.1.3. When the screen paints the USB port is already properly identified and I simply select 'Connect to nanoVNA'. It all works perfectly and has for every release of Saver that I tried starting back at about V0.0.6.
Again, this is all under Mojave, not Catalina. If you find the correct incantation for Catalina please let us all know.
Good luck,
Larry, AE5CZ
#5354

Hi Dana,
In OSX the nanoVNA is shown as '/dev/cu.usbmodem4001'
Normally rescan will automatically connect. You could try however to manually enter the string above
Eric
#5358

Ok, I rescan isn’t finding anything, so I will try manual also
Thx
Dana
toggle quoted messageShow quoted text
On Oct 20, 2019, at 14:22, ericm@wxs.nl wrote:
Hi Dana,
In OSX the nanoVNA is shown as '/dev/cu.usbmodem4001'
Normally rescan will automatically connect. You could try however to manually enter the string above
Eric
#5421

I used the installation process as described on the GitHub nanovna-saver website for installation of nanovna-saver for the Mac OS. It is as follows:
Mac OS:
Homebrew
Install Homebrew From : https://brew.sh/
/usr/bin/ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)'
Python :
brew install python
NanoVNASaver Installation
git clone https://github.com/mihtjel/nanovna-saver
cd nanovna-saver
Change PyQt restriction in setup.py PyQt55.11.2 to PyQt5
Install local pip packages
python3 -m pip install .
NanoVNASaver
All of the above works for me and I believe the Python installation is v3.7.4 Hope this helps.
Larry
#5426

Thanks Larry - good summary
This all worked fine on my iMac under High Sierra, however something
didnt work properly under Catalina…still trying to trace the issue, something
to do with the serial ports… I’ll report back if I can figure it out.
Cheers
Dana VE3DS
toggle quoted messageShow quoted text
On Oct 21, 2019, at 12:23, Larry Goga <lgoga@swcp.com> wrote:
I used the installation process as described on the GitHub nanovna-saver website for installation of nanovna-saver for the Mac OS. It is as follows:
Mac OS:
Homebrew
Install Homebrew From : https://brew.sh/
/usr/bin/ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)'
Python :
brew install python
NanoVNASaver Installation
git clone https://github.com/mihtjel/nanovna-saver
cd nanovna-saver
Change PyQt restriction in setup.py PyQt55.11.2 to PyQt5
Install local pip packages
python3 -m pip install .
NanoVNASaver
All of the above works for me and I believe the Python installation is v3.7.4 Hope this helps.
Larry
#5427

something didnt work properly under Catalina…still trying to trace the issue,
something to do with the serial ports
I cannot even use High Sierra because of driver (and Java) issues.
macOS has become more restrictive about 3d party kernel extensions or kexts.
'They act as drivers — if you like a Windows analogy — and give access to your Mac’s hardware.'
Something done on previous macOS that was inherited by Catalina update
could be at issue. Check 'Security & Privacy' under 'System Preferences'
'If a user space driver quits unexpectedly or you restart your Mac,
you might need to unplug and reattach the accessory cable to enumerate the driver. (50042397)'
'Driver extensions might not launch on-demand after installation. (51229724)
Workaround: Disable System Integrity Protection'
https://forums.macrumors.com/threads/macos-catalina-10-15-bugs-and-bug-fixes.2183833/
CH340 driver
https://community.platformio.org/t/mac-usb-port-detected-but-wont-upload/8756
#5478

Hi,
mine is working fine under Catalina 10.15. NanoVNASaver found the USB port immediately when the VNA was connected and I just clicked to connect to it.
Good Luck -- John (VK2JON)
#5488

Hi John -
mine is working fine under Catalina 10.15.
Great! If you would try, in Terminal:
# with nanoVNA powered off, enter:
ioreg -p IOUSB -l -w 0 | grep 'USB Product Name' > without
# then power on nanoVNA and enter:
ioreg -p IOUSB -l -w 0 | grep 'USB Product Name' > nano
# finally
diff nano without
# the result on my Mac shows a 'ChibiOS/RT Virtual COM Port' driver used for nanoVNA
< | | 'USB Product Name' = 'IOUSBHostDevice'
< | | 'USB Product Name' = 'QUAD-CAPTURE'
< | 'USB Product Name' = 'Polar V800'
< 'USB Product Name' = 'ChibiOS/RT Virtual COM Port'
---
| 'USB Product Name' = 'IOUSBHostDevice'
| 'USB Product Name' = 'QUAD-CAPTURE'
'USB Product Name' = 'Polar V800'
#5548

Now this is interesting John…. it isn’t playing here on Catalina.
Glad to hear someone has it though!
73 Dana VE3DS
toggle quoted messageShow quoted text
On Oct 21, 2019, at 20:52, John Sharpe <johsharpe@gmail.com> wrote:
Hi,
mine is working fine under Catalina 10.15. NanoVNASaver found the USB port immediately when the VNA was connected and I just clicked to connect to it.
Good Luck -- John (VK2JON)
#12922

macOS Catalina
Version 10.15.4
Rebooted to Recovery Mode
Disabled SIP (csrutil disable)
Restarted in 'regular' mode
device shows up as /dev/cu.usbmodem4001
Used NANOVnA to scope out antenna
Rebooted to Recovery Mode
Enabled SIP (csrutil ebable)
Restarted in 'regular' mode
device still shows up as /dev/cu.usbmodem4001
Moral of the story is it worked even after re-enabling SIP. Now I have to get it to work using vmWare Fusion and Windows 7. Hope this is helpful...
73 Mark KG0RMS

Ch340 Driver For Mac Catalina

Mac

Ch340 Driver For Mac Catalina Island