I-tek Usb 2.0 Ethernet Adapter Driver
Amatista Sheeley
i-tec USB 2.0 Fast Ethernet Adapter is an external 100/10Mbps network card for connecting via USB interface. Thanks to this adapter you can simply and elegantly add another network card to your computer, notebook or tablet. No external power supply is needed. The adapter supports a wide range of operating systems from Windows and Mac OS to Linux.
Question: Everything works fine, but it only shows the speed of 10 Mbps. Where is the problem?
Answer: Verify all the cabling between the PC/laptop and the active element and push the RJ-45 connectors. Sometimes can also help replacing the Ethernet cable between the adapter and the active network element (hub, switch, router) with a certified one. A solution can also be setting a specific value (instead of Auto Negotiation) in the properties of the network adapters, Speed & Duplex option.
Question: I have a MacBook with M1 chip and the adapter stopped working after the macOS Big Sur update.
Answer: Please install the latest Asix driver, which can be found in the Manuals, Drivers section.
To update your USB to Ethernet adapter driver manually, you need to go to the official website of Asus, find the driver corresponding with your specific flavor of Windows version (for example, Windows 7 of 64 bit) and download the driver manually.
There have been several threads such as this one more than a year ago and this one around the same time together with this most recently covering the topic over the years (I found a thread from 2016).
Therefore (as there has been repeated/concerted interest), I was wondering if Emlid could please confirm which particular USB to Ethernet wired adapter**(s)** (if there is indeed more than just one make/model) they currently have built-in firmware driver support for - and if so, is this from any particular date/firmware revision?
Just wanted to share our experience with the exact same issue. We have a set up where our Reach M2 are left in the field for a long period of time. There is Ethernet connection available but WiFi is either absent or impractical for our use case. It is important for us to be able to connect Reach M2 to internet using for instance an RJ45 cable. We power Reach through the JST-GH port.
Over the last months, we were unable to find any Ethernet adapter that would work with our recently purchased (Feb 2020) 4x Reach M2, which have had versions ranging from v22 to 26 over the duration of our tests.
While I primarily write this to save others some time and money, I also have a small hope that Emlid will take this (and the other posts on this topic listed by the OP) as a sign that some improvement in the support of Ethernet-based solutions would be most welcome
This is the actual Pro Signal branded adapter I bought. Having looked up the MAC address vendor, it appears that it is made under contract / white labelled by CE Link Limited. This is the OEM page for the adapter.
Perhaps having both power input and wired Ethernet is something you folks may wish to consider as a future feature, if it does not require major changes to the hardware. In my humble opinion it would be a very useful and market differentiating feature - especially if folks are using the receiver as a (semi) permanent base for corrections. I find wifi to bit a bit temperamental sometimes.
I have a Dell Dock WD15 and while it functions ok (all my ports work and charges my laptop - albeit not always), it seems to prevent the laptop from starting up properly. It just freezes on a screen and I have to manually turn it off and on again.
Even with the drivers installed, the Framework does not move beyond the BIOS splash screen when attempting to boot with the eGPU connected. The BIOS splash image appears stretched, so it seems to be affected by the eGPU somehow.
I am running Ubuntu 21.10 and 20.10, both make the same problem. Booting the same OS on my older Yoga (dd-copied the installation) works no problem, no display blinking.
I tried to test it with 2 different USB-C PD power sources - Aukey Omnia PA-B3 and some no-name chinese 65W adapter that was powering my Yoga for 1 year no problem (with the same USB-C hub).
Did someone else experienced similar problem?
I have my DIY Framework laptop (Batch 6) installed with Ubuntu 21.10. I maxed out the hardware available at the time of purchase (Processor, RAM, WiFi, and NVMe (2TB WD-Black 850). All laptop hardware worked after the installation except for the fingerprint sensor.
I tried two docking stations.
The first one I connected to the laptop was the StarTech USB-C docking station (TB3DK2DPPD). The unit was recognized and the monitor connected from the docking station via Display Port worked. I could not get a second monitor to be recognized via the docking station.
The second one I connected to the laptop was OWC Mercury Elite Pro Thunderbolt 3 Dock and Dual-Drive RAID 0GB Enclosure (NOTE: The unit is now called Gemini). The results were the same as the StarTeck docking station.
All I really wanted was something with a long cable that could do power and ethernet, such that I can leave this at my desk and only have one cable to plug into (and unplug when I leave); this one has a detachable cable and is pretty compact, if I ever want to take it with me or something.
To power it, I grabbed a beefy Nekteck 100W charger; you need more than 65W if you want to power the laptop through it, but 100W is probably overkill. I had guessed that the 400Hz problem was related to underpowered chargers, but that turned out not to be the case, so I probably could have gotten away with a 90W and been fine.
After using POP!_OS 21.10 for 1 day, I was not able to get the second monitor to be recognized via the two docking stations ( TB3DK2DPPD and OWC Mercury Elite Pro Thunderbolt 3 Dock and Dual-Drive RAID 0GB Enclosure ).
I tried to use one of my spare USB-C expansion cards to connect to my second monitor, but that was not successful (using Ubuntu 21.10 as well as POP!_OS 21.10). I am forced to use the HDMI expansion card to have a second monitor.
Unfortunately, the availability of Ethernet is not a given in all places. It would have been nice to see Wi-Fi being available, so that connected features (e.g. network storage, TekDrive, remote control) could be used in spite of this (e.g. via connecting to a mobile phone tethering hotspot).
This is perhaps not as user friendly as detection through mDNS and does result in some instances (after rebooting the computer) of the instrument not being automatically detected until the VISA layer is forced to refresh and rescan the instruments on the network.
After manually adding it to the system, it does function correctly. This remote control interface was used extensively in performing the input error and AWG error measurements as part of the Instrument Performance Tests chapter of this review.
This server proved useful in making some of the screenshots in this review. Its performance was quite good, reaching approximately 15fps (although this varies with the complexity of the displayed image). The performance is demonstrated in the below animated GIF image.
One downside of the VNC server is the lack of access to the front panel buttons and knobs. Some operations are difficult or impossible to do efficiently without this access (or knowing the relevant SCPI commands and issuing them directly to the socket server port).
Most Ethernet LAN-enabled instruments have a web-based interface of some sort that can be used to verify connection information and issue remote-control commands. Some even allow you to access and control the instrument remotely via a web browser.
I did a quick check of the open ports on the device using nmap. Nothing particularly noteworthy was found, although it is clear we are dealing with a Tektronix instrument (port 4000 instead of the more common 5025 for SCPI remote control). The ephemeral ports appear to change, while the MSO24 does seem to lock-up after hours of being scanned, thus isn't entirely robust to repeated malformed requests.
While the lack of a web interface was a bit of a downside, there was an unexpected find. The 2-series is capable of mounting network shares for storage of data (e.g. screenshots, settings and waveforms). This is a big convenience as it reduces the need to use physical USB storage media, although though the speed and reliability will depend on the network and the server at the other end.
ff7609af8f