LAVA: Forums - All Forums

Unable to open 1 com port on 2 port esl

Fri, 06 Jan 2023 00:08:09 +0000

We have a 2-port esl that has been working fine with 3 different computers sharing the 2 ports. The ports are connected to scale indicators that send continuous streams of weight data to our software. Today, while installing a new software package to read the scales we were having issues with unexpected characters in the data string (ascii 63). Then, the port that was exhibiting that issue stopped communicating completely. We can no longer access that port in hyper terminal, although the other port is working fine. I have tried deactivating and reactivating the port and rebooting the computer. The esl web page shows both ports are inactive. The other 2 computers are having no issue connecting to both ports on the esl. This has been working without any issue since 2014. The o/s is Windows 7 pro.

[FAQ] Power Role Swap with some USB-C Devices at 100% Charge

Fri, 04 Dec 2020 21:11:19 +0000

There has been an observed issue where certain USB-C Mobile Devices are unable to successfully negotiate a Power Role Swap when fully charged (i.e. Battery is at 100%).

When fully charged the Mobile Device will briefly disconnect during the transition from Charge to Discharge instead of renegotiating a Power Role Swap. This results in all peripherals being dropped before attempting to reconnect. Upon reconnection the Charging Cycle is restarted and the renegotiation attempt repeats over and over again.

This is particularly problematic for a Device during recalibrating (i.e. setting the Tablet to 100% after every x cycles).

Sometimes, though not always, the Mobile Device will break out of this loop on its own, but the only way to break this cycle is either to discharge the Tablet below 100%, or prevent the Tablet from every reaching 100%.

If you find yourself experiencing this issue please connect LAVA Support in order to resolve this issue.

- LAVA Engineering

Getting it to work

Wed, 22 Jul 2020 05:27:02 +0000

Hi,

I've purchased the simulcharge usb device and I wish to connect it to the Samsung Galaxy Tab A 8.0" to a Zebra ZD420 printer via USB.
Communication is working when i plugged in both the tablet and the printer. However, im unable to communicate to the printer after i plugged in the power cable.

Please advise.
Regards,
Tok

Ethernet to 2 RS232

Wed, 28 Feb 2018 23:31:26 +0000

I cannot connect to the device. I connect it on to my switch and ping 192.168.0.35 and nothing. I have reset the device by shorting out pins on J15 as per instructions.

I have connected the device directly to my computer with a cross cable but nothing.
The power red light is on (12v) and one yellow light on the cat5 connector. I cannot ping the device on this setup.

I have looked on my router and it is not on there.
What else can I do?
Denis

Connection Issue

Tue, 18 Apr 2017 11:52:42 +0000

Hi,

I am trying to use an ESL 4 port device using Windows10. The device manager looks fine, I am seeing all ports (green) and I can access the device from the browser as well. However I cannot access the ports. I tried to send data using code (simple application in c# that threw an exception when I tried to open the port) and also tried accessing the port using putty (again did not manage to open port).

Any ideas please?

How to determine IRQ assignment in IP Extender

Tue, 29 Nov 2016 22:28:11 +0000

I think that I have an IRQ conflict with virtual COM4. I would like to reassign IRQ to test theory.

Minidump reports Interrupt storm as source of fatal.

Trying to set the Parallel Port speed

Wed, 25 May 2016 16:45:00 +0000

I have a very old BOCA printer that I want to get working on my Windows 7 64bit machine.
I have installed and verified that the printer is installed and working through Windows Device manager.

On the machine that I previously used I had to set the parallel port to PS/2 mode. ECP and EPP didn't work with the printer.

My Lava Card is:

PN - MOKO L72.2A
It also has:
TS-04
94V-0
4302

on the card.

I used this driver: http://lavalink.com/support-drivers/pci-...-port-epp/

The description says EPP but I am hoping that I can use a different mode.

I did go to this link: http://lavalink.com/support-drivers/lava...utilities/
but non of the utilities seem to work with a fully patched Windows 7 64bit machine.

DSerial-PCIe/LP Port lockup/unresponsive

Fri, 13 May 2016 02:47:26 +0000

Hi all,

I've got a bit of an issue with a pair of DSerial-PCIe/LP cards i have installed in a Dell OptiPlex 7020 SFF with Windows 7 x64 Pro. In a bit of a pinch i had to put something together that could work as a bit of a console server on short notice. LAVALink and Memory Express to the rescue . I had no issue installing the cards and connecting them up to the switches and routers i needed to console into. I am using PuTTY as a terminal emulator as Windows 7 is devoid of the good 'ol handy HyperTerminal.

Here's the problem:

After a short period of time following boot and logon (sometimes as short as 5 minutes), I run into one of two issues on some or all of the COM ports - assigned COM11,12,13,14. (I had the same issues when the ports were assigned their default assignments of COM4-7)
1. I am able to 'connect' or open the serial port, but i can't get anything to echo back, even after pounding the enter key many times (which should bring up a new command prompt line on Cisco iOS). The first time i noticed this was after first boot up after installation and driver load for both ports on one of the cards (at first i was thinking a hardware issue, but managed to get 'er to go after a reboot.
2. I get an "unable to open port COM#" from PuTTY when trying to open a line to the ports, i just had this happen on all four ports (both ports on both cards). Changing the COM port assignment (to something like COM4,5,6,7 for example) does not correct this behavior, i just get the new port number/name in the error message.

DSerial_WDM.png (Size: 41 KB / Downloads: 0)

For troubleshooting purposes, i have managed to temporarily correct this through one of the two following actions:
1. Reboot the computer and log back in.
2. Delete the device from Device Manager and do a "Scan for hardware changes" to reload the devices and the driver assignment.

I am using the driver package available on 05/11/2016, file name "Lava_2014_07_15.zip". I've switched the cards between slots (board has 2 x16 slots) and the issue doesn't follow a single card or slot consistently, but it is always two or four ports at a time, when only two, they are both on the same card. I have no issues with the on board port, which is assigned COM1. I can't find anything about device power management in Device Manager to rule out some sort of bus shutdown for the cards, so i am at a bit of a loss.

Any help would be greatly appreciated.

Thanks,

Trouble in Windows x64

Fri, 01 Apr 2016 19:30:38 +0000

I'm trying to upgrade a system that communicates to a Casio register via Casio's CV-22 software from Windows XP. Everything works in XP using either a generic USB adapter or an ESL4-DB9.

First attempted upgrade was to Windows 10 x64 using the Windows 8 Lava ESL WESL 2015_01_13a setup. The CV-22 software works in Windows 10 x64 using the generic USB/RS-232 adapter, but we can not get it to work using the ESL4-DB9. When we try initiating communications the register sees the attempt and locks the keyboard, the lights flash a few times on the ESL4-DB9, and then we eventually get an error "4506 - Protocol or communication packet error" in the CV-22 software. We've tried every configuration and driver option we can find to no avail. The ports activate and install fine in Windows, communications start up, and then fail with the same error every time using the ESL4-DB9

We put a Hyper-V Windows XP virtual machine on the Windows 10 x64 computer, and installed the old manager/drivers and CV-22 software, and once again, everything works as expected inside the virtual machine.

We next tried Windows 7 x64 concluding that the Windows 8.1 drivers may not work for Windows 10. We get the same results in Windows 7 x64 as we do in Windows 10 x64. Communications are initiated, the register sees communications and locks the keyboard, we wait, we get the same error "4506 - Protocol or communication packet error".

Any ideas on getting the ESL4-DB9 to work in the CV-22 application on something newer than Windows XP? USB/RS-232 works fine, but we sometimes need access at longer distances than that will accommodate, and a virtual XP machine almost defeats the purpose of upgrading Windows.

The ESL4-DB9 firmware is 6.1.0 2007/03/29

Lava Dserial that show random letters

Sat, 06 Feb 2016 22:31:50 +0000

I have a PCI card Lava Dserial that show random letters and symbols when i write a command using the hyperterminal in Windows XP, i am using drivers from Lava web site (this web site). What can cause that and how can i fix this issue.

Thank you in advanced for your help.

STS-P2UE vs STS-P2UE+

Fri, 01 Jan 2016 21:11:33 +0000

Hello,
What is the hardware difference between STS-P2UE and STS-P2UE+.
One is for Galaxy Tab 4 and the other for Galaxy Tab S/PRO, but what changes on hardware ?
best regards

Firmware for Startech

Wed, 02 Dec 2015 03:12:32 +0000

I assume your firmware will work fine on Startech branded boxes? I have one of their NETRS232_1 that is most certainly made by Lava. Any way to update firmware without Windows? Thanks.

Device Manager cannot find ESL.

Fri, 27 Nov 2015 02:36:05 +0000

Hello, the current device I am using is an Ethernet to RS-232 Quad Serial Controller,

I am using a crossover cable connecting the RS-232 to my PC, a Windows 7 (x64 bit) computer, yet when I install the latest driver/firmware, and open the WIN7_2008_XP_2000 folder, then open setup.exe, it installs as supposed to, etc.

However when the install finishes and the software opens up, it does not show the RS232 under "Ether-Links near me", in fact, you cant even expand "Ether-links near me".

As to some solution I read that didn't work:
Disable your firewall: I have already done that, no significant results.

Please answer back onto some possible solutions.

STS on Nexus 5

Wed, 18 Nov 2015 08:28:49 +0000

Hello,
I would like to test the Lava STS PoE adapter on Nexus 5 smartphones.
Nexus 5 works with a simple USB/Ethernet dongle, but we would also like to power by PoE.
Which adapter is most likely the best for Nexus 5?
STS-PE, STS-P2UE or STS-P2UE+ ?
best regards
boris

"The system cannot find the path specified" (Windows 8.1 64 bit)

Sun, 01 Nov 2015 21:05:57 +0000

Quick background: I'm setting up a new Windows 8.1 (64 bit) system for a client who has an old HP LaserJet 4 that's still doing excellent work. The new computer doesn't have a parallel port, so I purchased Lava single Parallel port PCIe card. I've confirmed the card works by getting it to run on a different computer under Linux:

Code:
[root@testing ~] modprobe parport_pc io=0xcc00 irq=10

[root@testing ~] modprobe lp

[root@testing ~] dmesg | tail

parport0: PC-style at 0xcc00, irq 10 [PCSPP,EPP]

parport0: Printer, Brother HL-1250 series

lp0: using parport0 (interrupt-driven).

When I attempt to install the card on the Windows 8.1 computer, the Device Manager finds the card and says it needs drivers. I start a manual setup process and point it to the root of the directory where I've extracted the Lava_2014_07_15.zip file. Windows the says "The system cannot find the path specified."

The card's properties match the following description in PCIePorts_CC.inf:
%PCIe.ParallelPort%=LptCard,PCI\VEN_1407&DEV_A000&SUBSYS_2000A000&REV_00

That INF file contains references to StnPPort.sys and PCIePorts.dll. A search of the file system turned up the PCIePorts.dll, which appears to be a Microsoft file because its Properties tab incluides a Microsoft copyright statement. The StnPPort.sys file is not found on the system.

Following a tip from a web search, I tired staging the driver:

Code:
cd C:\Users\\Downloads\Lava Computer Mfg\Windows

pnputil.exe -a PCIePorts_CC.inf

I got a message the copy/installation was successful, but another attempt to install the driver failed.

I also tried the following, based on another web search:

Code:
pnputil.exe -i -a PCIePorts_CC.inf

Processing inf :            PCIePorts_CC.inf

Failed to install the driver on any of the devices on the system : No more data is available.

Total attempted:              1   

Number successfully imported: 0

Ideally I'd like to be able to install the device driver by following the proper Windows procedure. However, if all the installation does is copy a couple of files and update the registry, I suspect I could get the card going by knowing where to copy the StnPPort.sys file and importing the appropriate registry entries.

Any insights and assistance you can provide would be greatly appreciated, and I'd have a happy customer.

Regards,
Brad