are 32-bit components, which run in 32-bit mode on 64-bit Windows. (59601)
12.12 OpenLDV 3.4 Example Failure
After installing the OpenLDV 4.0 runtime, the OpenLDV 3.4 example may fail with the “This application has
failed to start because MFC71.dll was not found. Reinstalling the application may fix this problem” error.
This occurs because the OpenLDV 4.0 runtime update caused OpenLDV 3.4 and its components to be
removed from the system. If no other application on the PC has installed the MFC71.dll component, it will
no longer be present. Workaround: Install the OpenLDV 4.0 SDK to get updated examples that work with
OpenLDV 4.0. (58688)
12.13 Missing U10/U20 Network Interface
If an Echelon U10 or U20 USB device is plugged in before the OpenLDV 4.0 software is installed on a
computer, the driver installation could partially fail in a way that makes the device invisible to the LonWorks
Interfaces control panel applet. Workaround: Unplug the U10/U20 USB device. Uninstall the OpenLDV 4.0
runtime. Go to the Windows Device Manager and remove the USB device there. Re-install the OpenLDV
4.0 runtime. Plug the USB device back in. (59851)
12.14 PCC/PCLTA Image Not Reported Correctly by Test
When changing a PCC-10 or PCLTA’s “NI Application” image, the updated driver information is not shown
on a subsequent Test command. Updated driver information will not be shown until the Test command is run
two times or more. Workaround: Run the Test command again if the driver information seems out of date.
(62182)
12.15 PCC-10 and PCLTA Interface Name Limit
PCC-10 and PCLTA devices may only use device names in the range LON1 through LON9. If the “Starting
Interface Name” for these types of devices is set to LON9, the system may only support one device of this
type. Workaround: Set the Starting Interface Name to LON1 to support 9 LON interface devices. (62136)
12.16 Confusing Error Message
When adding RNI and LonScanner interfaces, some invalid hostnames may be accepted, but later cause the
“A non-recoverable error occurred during a database lookup” error message. Workaround: Enter a valid IP
address or hostname in this field. (61672)
12.17 RNI Re-connect Problem with Restrictive Firewall Settings
If the IP connection is disrupted between a computer running OpenLDV and an RNI and the OpenLDV
computer is behind a firewall that only permits outbound connections based on the source-side port number,
the reconnection may fail. Most firewalls are not this restrictive and will normally be configured to permit
outbound connections based only on the target-side port number, allowing the source-side port number to be
any value. Workaround: To communicate with RNI network interfaces in this scenario, modify the xDriver
Profile on the client computer to specify a non-zero “TCP Local Port” on the “Downlink Sessions” tab.
With this configuration, if a session is closed or fails, it is not possible to re-connect to the same RNI for four
minutes (until the connection leaves the TIME_WAIT state). Workaround: Either ensure that you won’t need
to reconnect to the same RNI within four minutes; or create multiple xDriver Profiles (and duplicate RNI
entries), each using a different permitted Local Port, and cycle among the profiles when connecting to the
same RNI. (26579)
OpenLDV Network Driver ReadMe http://www.echelon.com/support/downloads/software/networkinterfaces/...
8 of 9 8/14/2012 12:53 P
(2 paginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales