Frequently Asked Questions - The five questions posted most recently:

Connectors: Manufacturers and Part Numbers

Thu, 29 Feb 2024 15:21:00 GMT

Sometimes external pluggable connectors and adapters get lost. Here is information on Manufacturers and Part Numbers, to find a suitable supply shop.

1. Power supply 3-pin w/o fixing screws (Used on NetCom+ 1/2 ports, Net-CAN+, Baltos, SER-485, and other)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : 5ESDVM-03P
Manufacturer: Phoenix Contact
Part number : MSTB 2,5 HC/ 2-ST

2. Power supply 3-pin w/h fixing screws (Used for CAN on Baltos, VS-860, power for USB-4/8COM Plus, NetCom Plus 4/8 ports)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : 5ESDV-03P

3. Power supply 3-pin (Used on NetCom/Net-CAN, Alekto/Alena, SER-485 and other)
Manufacturer: HOW DER ELECTRIC CO., LTD.
Part number : HD-515H-3P

4. Digital-I/O Alekto 13-pin (Used on Alekto)
Manufacturer: HOW DER ELECTRIC CO., LTD.
Part number : HD-516H-13P

5. Digital-Output 12-pin (Used on NetCon II, Alena)
Manufacturer: Phoenix Contact.
Part number : MC1,5/12-ST-3,81(1803675)

6. Digital-Input 8-pin (Used on NetCon II)
Manufacturer: Phoenix Contact.
Part number : MC1,5/8-ST-3,81(1803633)

7. Power supply 2-pin (Used on RISE)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : 5ESDVM-02P

8. Power supply 3-pin (Used on TruckHUB)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : 5ESDVM-03P

9. Digital-I/O 12-pin (Used on RISE)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : EC350RLM-12P

10. Power supply 14-pin (Used on TruckHUB)
Manufacturer: DINKLE ENTERPRISE CO., LTD
Part number : 5ESDVM-14P

I need a clean removal of the NetCom Plus drivers

Tue, 16 May 2023 14:08:00 GMT

Of course the first step of driver removal is the uninstall process as described in the User Manual. Please check about this there.

But even after that removal some data may stay in the Windows Registry. Here is a list of items to remove from there.
The usual regulations about caution apply, it is easy to render your system useless by wrong changes in the registry. So have a backup ready to avoid any data loss.

The following description applies to older models of NetCom in a similar way as to the NetCom Plus series. So below we only use "NetCom" to refer to all models.

The NetCom Plus Manager keeps a list of all NetCom devices it had detected in the past. And also the manually added NetCom for that matter. It is kept in the registry keys
[HKEY_LOCAL_MACHINE\SOFTWARE\Vision Systems GmbH\VScomNet]
[HKEY_LOCAL_MACHINE\SOFTWARE\Vision Systems GmbH\VScomNetPlus]

Also it keeps a list of all Com Ports related to the NetCom devices, this is kept in
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\VSNETCOM]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\VSNETCOMPLUS]

If the driver is removed from the system it is safe to completely remove those keys.

Also some keys are generated and managed by Windows itself, not controlled be the NetCom Plus Manager. These are
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vsns2k]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vsnsplus2k]
for the NetCom servers, and
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vscnp2k]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vscnplusp2k]
for the Com Ports. It should be safe to remove these entries as well.

Again be warned, be very careful when tempering with the Windows Registry.

Windows Driver for the Phased out NetCom Lite and PRO Devices

Thu, 19 Aug 2021 10:36:00 GMT

Both device types won't be manufactured and sold for many years now. Hence the software support has stopped and the new driver supports NetCom Plus devices only.

You can try to use the old signed driver or this one . If it doesn't work with the newer Windows versions, we cannot help you further.

The best way to install the old drivers on Windows 10 is to install Windows 7 and the old signed driver and then to upgrade to Windows 10.

Another workaround would be to use TCP or UDP modes directly. This will make your application operating system independent as you don't have to install the NetCom driver.

I am using your Netcom 111 for a faxing program. I have an issue with fax operation, what to do?

Mon, 03 May 2021 13:21:00 GMT

A typical serial Modem understands two different sets of commands for operating in Fax mode. These sets are named Fax Class 1 and Class 2. Naturally Fax Class 1 has been specified first.

Fax Class 1 provides detailed information on the current status of the transmission, and also detailed commands to control the operation. At the downside the responses to events on the Modem have to be sent in a strict timely manner.
Back in time when the Class 1 command set was defined Windows 3.1 has been a modern operating system. Serial ports did not operate very fast then, and further the required strict timing was not possible in all conditions in Windows.
To provide Fax mode operation even in such systems the Fax command set Class 2 has been defined. Many critical operations are handled by the Modem in autonomous mode, the software just provides more general supervising functions. The requirement for strict timing was removed this way.

Today computers are very fast, and they can control a Fax Modem in the required timely manner. Typical software uses Class 1 commands as default to control the Modem, just to give detailed and realtime feedback to the user interface.
However using NetCom the network adds delays between received data on the serial port, and arrival of these data in the application software. These are some Milliseconds at least, which often is to long for Class 1 commands.

So even when the fax application identifies the Modem as Class 1 capable, such can cause problems when the Modem is connected to the serial port of a NetCom. Simply configure the application software to use the Class 2 command set, and the problems will vanish.

Why does RS485 (and RS422) require to connect the logic Ground?

Wed, 15 Jul 2020 09:13:00 GMT

With RS485 serial interfaces you have to connect the logic Ground between all connected devices. This is necessary because the specifications of RS485 require this. Unfortunately many demonstration graphics focus on the data lines, and omit the ground line for simplicity.

The ground connection is not written explicitly in the specifications. Instead a so called Common Voltage Range (CVR) is defined. The specification -7V to +12V for the CVR allows to design and manufacture less complex and hence low-cost circuits. Without somehow connecting the logic Ground an installation can not ensure this requirement is met on all stations. A device without such an option is possibly not conforming to RS485 specifications.

The transmission happens in a balanced fashion. Two wires are used to carry one logic signal. A positive differential voltage represents a logic 1, a negative differential voltage represents a logic 0.
The transmitting device produces voltages within the CVR, typical +5V for high and 0V for low level. These voltages of course are generated with respect to the logic ground of the transmitter. Any measurement must check the voltage between the signal line and logic Ground. When the signals connect to a device, it must evaluate the voltages with respect to the logic Ground of the receiver. If both Ground levels differ by more than +7V, on the receiver side one or both voltages may be not within the CVR. If the levels are not within the defined CVR, the logic value may not be understood, causing errors on receiving.

Basically this is also discussed on Wikipedia, and for example in application notes from manufacturers like Maxim and Analog Devices. The connection of ground may happen implicit, because the logic ground of all devices is connected to some global protective ground level. If this is nearly the same on all devices, an extra wire is not required.
If the ground levels are different, without an explicit connection all equalising currents run on the data lines, hence pass the logic circuits for transmit and receive. This can damage the devices, and often does over time.

When the serial interface is galvanically isolated, sometimes there is no contact for the isolated logic ground. In such networks it may be possible to make a simulated connection. On the receiver side one resistor connects the positive signal line with ground, and another resistor connects the negative signal line with ground. As a net effect now the logic ground of the receiver is in the middle of the positive and negative voltages. So both data lines are in the CVR with respect to the receiver. It is difficult to give reasonable values for these resistors. If there are only two devices connected, resistors in the range of 2k Ohm should do the job. But in any installations this requires explicit calculations.