Weatherlink We Did Not Receive an Acknowledge to Our Last Command. Please Try Again

Windows 10 is a major new Windows release from Microsoft. While Windows 10 offers many benefits, it does at present have the potential to be slightly more troublesome in ensuring Weatherlink compatibility. To be articulate, Weatherlink (as of v6.0.iii) remains fully uniform with Windows 10 merely there may occasionally be issues in getting a new or recently updated version of Windows ten to role correctly with Weatherlink. These issues can ordinarily be stock-still just will typically require a one-off adjustment to the Weatherlink installation or configuration.

First steps

If yous are experiencing whatever Windows 10 related bug then the commencement troubleshooting step is to ensure that you're definitely using the latest version of the Weatherlink programme – please meet the 'Reinstalling Weatherlink' section of the Migration and Update Problems topic for further details.

If the problem remains unresolved and then please read on:

Windows 10 updates

With Windows 10, Microsoft seem to have introduced a new updating strategy that could, at least in theory, impact on compatibility issues. Automatic updating of Windows has of class been the norm for all contempo Windows releases but, in the main, the updates have been either relatively pocket-size, typically security or problems-related, or well signposted as in Service Pack (SP1, SP2 etc) or east.g. v8.0, v8.1 etc releases. But with Windows x, MS seem to have started to roll out potentially significant changes to the Windows architecture as automatic updates but without really highlighting key features or version numbers of the latest updates.

In futurity, it looks like information technology will be more necessary to exist aware of the Build Number of the Windows x version in use and alarm to the possibility that one potential cause of a new USB communication issue could in theory be a recent Windows update. There are various ways of seeing the build number, but maybe the simplest is to open a command prompt window eg by correct clicking on the Win10 Start Button and choosing the Command Prompt item. The Build Number should be displayed on the top line of the window, ten.0.10240 for case on my PC right at present, giving a build number of 10240. Another easy option is to press the Windows and 'R' keys together to bring up the 'Run' window and then type in winver and OK, which should display the Windows 10 About box.

The lesser line is that information technology'south no longer rubber to offering a blanket balls that Windows x is compatible with Weatherlink because in principle an automatic update may be released at some point that does break compatibility. And in fact, after this page was originally written, in Dec 2015 exactly this issue appeared. We don't yet have an exact build number when this issue was introduced simply information technology is clearly later than 10240. It is relatively small-scale in that it affects only the USB Xpress driver. We believe that users will be unlucky ever to see this bug nowadays provided their Windows build is fully maintained and upwards to date. But a couple of potential fixes are described beneath.

Latest Silabs driver release

Silabs announced to have released an updated driver version (v6.vii.6 dated Sept iii, 2020) that may well fix the USBXpress commuter issues in sure versions of Windows 10 and which may exist downloaded from: https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers . We don't currently have access to a version of Windows 10 that exhibits this bug and so cannot confirm the bugfix, but very probably it cures the problem. It may well besides exist that current builds of Windows 10 now comprise the updated driver and therefore do non testify the bug.

But if you're withal seeing the problem and so the Rollback prepare is described below.

Windows 10 Rollback fix

This prepare is necessary considering in Dec 2015 SiLabs announced to have released a new USB Xpress commuter to Microsoft for inclusion in Windows 10 update that is non working correctly. The Rollback fix reverts the USBX driver to the previous version.

Two general points before describing the Rollback ready for affected PCs:

• The Windows 10 compatibility problem affects just the USB Xpress driver and not the VCP driver. The simplest set is therefore just to switch to using the VCP commuter – in other words, to switch to connecting to the logger as a serial device instead of as a USB device. If you lot don't understand what this means then please refer to the Agreement WL Comms & Issues topic and to the further topics linked to from at that place that explain how to switch logger modes;
• An updated USB driver is expected to be released by SiLabs fairly quickly. Once this is available and has been included in the Weatherlink and Windows 10 update distributions (and installed of form) so this outcome volition disappear again. In the acting we besides empathize that SiLabs are asking Microsoft to remove the faulty USBX driver from Windows 10 update until such time as a working and tested USBX driver is available (which means that the previous working driver will remain active). In principle, notwithstanding, this same generic type of issue could yet reappear at some future engagement if for example Microsoft opt to change the Windows driver specification further or a faulty driver is released again;

Rollback Fix

This fix can be tried by Windows 10 users seeing a 'Communications fault' in Weatherlink when attempting to connect to the USB logger in one of ii scenarios: either the connection was working correctly previously but is not at present, post-obit eg a Windows update; or the logger is beingness connected to a PC with a new Windows x installation. (NB No versions of Windows prior to v10 are affected by this specific issues)

Applying this ready is adequately straightforward just does require some knowledge of the Windows 'Device Director' settings manager. As mentioned in a higher place, it'due south also the instance that the simplest fix is to move the logger to VCP/serial mode as described elsewhere in these notes. Merely for anyone keen to go along using USB mode and then proceed every bit follows:

The offset step is to confirm that the USB Xpress commuter is indeed being used. This volition be the instance if the USB selection is selected in the 'Communications Port' dialogue of Weatherlink, but can exist confirmed past looking for a USBXpress entry in the 'Universal Serial Double-decker Controllers' section of Device Manager, equally shown in the picture right. Call up that the driver entry will simply show upwardly in Device Manager when the logger is really continued via USB to the PC.

If this USBXprinting entry cannot exist seen so either the USB port option has not in fact been selected in Weatherlink (i.e. maybe the serial option is actually in utilize) or the USB Xpress driver is non loading for another reason – further investigation volition exist needed.

If the USBXpress entry tin be seen then correct click on this entry and cull the Properties option to display the USBXprinting Device Properties Window.

Click the Driver tab and check the driver'south date and version number. If this shows as v6.7.ii.0 and so this is the faulty USB Xpress driver.

The remedy is to click the 'Roll Back Commuter' push button which should cause the previous commuter version to get active again. Once the version is no longer showing as v6.7.2.0 so it should be possible to connect to the logger via USB manner again. If this doesn't happen immediately and so information technology's possible that the logger's USB cable may need to be asunder and and then reconnected after a few seconds interruption.

Use of the previous driver version should exist retained after the PC has been rebooted, but information technology may be prudent to check this to be certain of reliable future functioning.

Final modified: Jun 04, 2021

hernandezmortan.blogspot.com

Source: https://www.manula.com/manuals/pws/davis-kb/1/en/topic/windows-10-issues

Share this post