Just upgraded my computer to loggernet 4.0 from 3.4.1.
When I try to connect to the logger (CR1000) via the com port as usual, I get the error "read failed".
The connection worked in 3.4.1 and PC200... Any ideas?
The communication log is:
Communication Log
"2009-11-15 9:51:05 AM","COM11","S","opening comm port","COM11","115200"
"2009-11-15 9:51:05 AM","COM11","S","Provider opened","115200"
"2009-11-15 9:51:05 AM","COM11","S","Device dialed"
"2009-11-15 9:51:05 AM","CR1000","F","transaction failure","unreachable destination","Get Logger Program Status"
"2009-11-15 9:51:05 AM","CR1000","F","transaction failure","unreachable destination","check/set clock"
"2009-11-15 9:51:05 AM","COM11","F","read failed"
Hello Geometrikal,
I am betting you are using some type of USB to serial cable (maybe even ours?) on Vista. We have seen a few incompatibilities. Contact me on Monday dana at campbellsci dot com and I will get a file to you that should help.
Dana W.
Problem: Device Config Utility can't connect to CR3000 (neither can 'Setup' or 'Connect' from the LoggerNet suite)
Could not locate PakBus devices
15:09:52.752 Fault
"read failed"
Computer:
Microsoft Windows Vista Home Premium 64Bit SP2
LoggerNet 4.0.0.10; devconfig.exe 1.14.5.0; ConnectScreen.exe 4.0.1.0
Prolific USB-to-Serial Comm Port (drivers up-to-date according to windows)
HW-Connection:
USB>USBtoSerialAdapter(Com4)>RS232-extention-cable>RS232-Port@CR3000
tested so far:
> USBtoSerialAdapter works on 2 other machines with WinXP Pro 32Bit SP2 which have LoggerNet 3.4.1 installed; CR3000 responds flawless there
> PakBus Adress for CR3000 is '1' in LoggerNet and the CR3000
> BaudrateRS232 in CR3000 is set to '0' = auto and it shows > '-9600' which is the setup in CDU and also in the properties for the USBtoSerialAdapter
> settings for the USBtoSerialAdapter are the same on the WinXP and WinVista machines (Data Bits '8'; Parity 'None'; Stop Bits '1'; Flow Control 'None')
There is a known issue with some USB devices with the current shipping version of Loggernet 4.0, on some platforms. If you can email me directly I will send a new DLL file directly to you that will fix that known problem. Email me at: andrew dot sandford at campbellsci dot co dot uk
Problem: Device Config Utility can't connect to CR3000 (neither can 'Setup' or 'Connect' from the device configuration utility 1.18.. The following error is displayed;
Could not locate PakBus devices
20:09:51.434
Fault
"serial open failed","2","The system cannot find the file specified."
Any solution to this...
vincent
That error often occurs when the selected COM port does not exist or is in use.
My solution would be:
1. Open Device Manager and check what serial ports are available (Start -> Control Panel -> System -> Hardware ->Device Manager -> Ports (COM & LPT) )
2. Check no other programs are open using those port(s)
3. Make sure the Campbell software is set up to use the correct port.
Hope this helps :)
Hello,
Have the same problem, while trying to connect, returns error "Could not locate PakBus devices"
16:40:56.575 Fault
"open failed","failed to set the comm state","31","A device attached to the system is not functioning."
Com port working properly, and before didn't have any problem with connection.
Any ideas or solutions.
Best,
Refer to this blog article:
https://www.campbellsci.com/blog/communication-problems-serial-connections
Error code 31, "A device attached to the system is not functioning", is an error returned by the Windows operating system. LoggerNet is just reporting the error that is being passed to it by Windows. If you are using some sort of USB to serial cable or other device for your COM port connection, my guess is that the device is the root of the problem. Some initial steps would be to shut down the computer, remove the device, reboot the computer, and reattach the device and see if that gets it working. If not, try reinstalling/updating the driver for the device.
If you go into Windows Device Manager, the COM port causing the problem should have an error indicator beside it. You can right click the device and choose update, or uninstall/reinstall.
Dana W.
Dear Jdavis and Dana,
I tried to fix bound rate of com ports over usb, but then it returned error "2" like invalid com port, but everithing are match, port number and data transfer speed.
About error "31", yes it happens when windows doesn't recognizing the cable, but when it works it appaers in device manager correctly, stiil returnes error "31" or "2".
Could be cable problem? cos I don't have device with integrated com port.
Thanks,
Zura
Try using a different USB to RS232 cable. We very highly recommend only using cables which use FTDI chips. Prolific USB to RS232 chips have compatibility problems with a lot of equipment.
I don't know where you are located at, but in the US, cables like our part 17394 sell for less than $20 plus shipping. Only purchase a cable if you are certain it uses an FTDI chip.
Ok thanks, I'll try with that cable.