supercal.blogg.se

1. MAC DRIVER FOR ICOM FOR MAC
2. MAC DRIVER FOR ICOM SERIAL
3. MAC DRIVER FOR ICOM DRIVERS
4. MAC DRIVER FOR ICOM PATCH

MAC DRIVER FOR ICOM PATCH

so everyone (including Apple) runs for cover, and that leaves us end-users in the real world to fend for ourselves and patch together something that 'sort-of works'.

MAC DRIVER FOR ICOM FOR MAC

For example, the release of WSJT for mac is a volunteer effort with Zero cash flow, as far as Icom is concerned they have never represented that a IC7100 will talk to a mac OS so that lets them 'off-the-hook', and SL is saying 'hey we just make the chips we can not possibly track every use that it is put to as the numbers of eventual implementations are huge'. In all fairness to them, I understand that there is no budget ($$) for this. There is something off center about that.

MAC DRIVER FOR ICOM DRIVERS

The details of necessary drivers and end user configuration details is just not documented at the release point of a final product intended to be run by end users.

On Mon, at 03:31 PM, Bill, W8BC wrote: I wish we had a very definitive word on this situation with the Mac I think you have hit on the core of this issue for us end users, that is that the developers of the software and makers of the hardware that incorporates the product from the chip manufacturers, all of them are just not documenting how the end user should correctly approach configuring their release versions. I see that some folks are having problems figuring out what to do. I wish we had a very definitive word on this situation with the Mac.

FTDI: Most devices tested so far with standard VID/PID including.Big Sur DriverKit currently supports the following devices without any 3rd party driver:

MAC DRIVER FOR ICOM SERIAL

Here is what the MacLoggerDX site says: Native DriverKit Support: Apple released Big Sur with built-in support for many (but not all) serial devices. I got this from DL2RUM, of RumLog software and others. When I first started using WSJT-X back in December I was looking to load the Silicon Labs driver, but was told my numerous folks that both Catalina and Big Sur had drivers built in for my 705 and other Icom rigs. I bow to your expertise on this since all this is beyond me. I am not aware that I have installed any special programs beyond MS Office, a database called FileMaker and a Bible software program called Accordance. I am using /dev/cu.usbmodem143201 for both WSJT-X and MacLoggerDX, a Mac logging program. On Mon, at 12:47 PM, wrote: I assume you are talking about "/dev/cu.usbserial-141410" I may have to get a junker HP laptop on eBay and dedicate it to run WSJT. ~ To reset the SL Chip and destroy the stack on the IC7100 you have to ~fully remove~ the power cable (or cut the power supply off), just turning off the radio will not do it !!! So it is a mess. So I think Icom is a little over their head with that type of low level programming and screwed it up on the IC7100.

when you try to bring the total system back up then WSJT sees that stack and gets very confused. Also a bad side efffect is that the Icom lets the SL Chip show all the now stacked up open USP ports / chanels from each previous use, so you get this huge' stack of active open USB ports. Icom never should have implemented it in that manner. It is sort of nice becase if your start the WSJT software with a turned off radio it will WAKE the radio and return it to service. The radio will still respond like a "Wake-On-LAN" even if the radio is OFF. On that radio Icom has designed / implemented it to remain the status of the chip "live" even if you turn off the radios front panel power switch to the radio, even when the front panel switch is in the OFF physical position. There is also some sort of issue with the way Icom intergrated that SL Chip. I think we are in bleeding edge territory here.

I downloaded the 6.1 and will give it a try.