K8097: USB connection failed message

Kits General
1

Hi,

trying to run the demo software for the 4 channel stepper board K8097 I get the message “Connection failed. Please verify your port name and that the port is not already open”. I checked the COM port which is 4. The device is recognized by the computer when connected to the USB port. Furthermore I checked the power supply for the PIC which is about 4.4V. The PIC’s oscillator is running fine at 12.1MHz. Soldering should be OK (I am used to soldering, but this shall not mean, that a bad soldering could be excluded).

Any hints?

Thanks and best regards

Urs

2

I presume that with “recognized by the computer” you mean that you can see the device in the Windows Device Manager or something like a USB descriptor dumper. I personally use the Thesycon USB Descriptor Dumper to find out initial details about USB devices.

thesycon.de/eng/usb_descriptordumper.shtml

If you can get that info it means that the device enumerates properly on the USB stack. If that is the case then the soldering shouldn’t be your current problem. It may become one later, but right now I would guess there is something wrong in between the program and the USB stack.

Regards,
Jan

3

Hi Jan,

wow, that was a quick answer, thank you very much! I have just run the progam, and this is what it “spits” out (I run it on my other computer, where the COM port number for the K8097 is read as 3).

Information for device K8097 - 4 Channel USB Stepper Card (VID=0x10CF PID=0x8097):

Connection Information:

Connection status: Device connected
Device actual bus speed: Full
Device is hub: No
Device adress: 0x0001
Current configuration value: 0x01
Number of open pipes: 3

Device Descriptor:

0x12 bLength
0x01 bDescriptorType
0x0200 bcdUSB
0x02 bDeviceClass (Communication Device Class)
0x00 bDeviceSubClass
0x00 bDeviceProtocol
0x08 bMaxPacketSize0 (8 Bytes)
0x10CF idVendor
0x8097 idProduct
0x0100 bcdDevice
0x01 iManufacturer “Velleman Projects”
0x02 iProduct “K8097 - 4 Channel USB Stepper Card”
0x00 iSerialNumber
0x01 bNumConfigurations

Configuration Descriptor:

0x09 bLength
0x02 bDescriptorType
0x0043 wTotalLength
0x02 bNumInterfaces
0x01 bConfigurationValue
0x00 iConfiguration
0xC0 bmAttributes (Self-powered Device)
0x32 bMaxPower (100 mA)

Interface Descriptor:

0x09 bLength
0x04 bDescriptorType
0x00 bInterfaceNumber
0x00 bAlternateSetting
0x01 bNumEndPoints
0x02 bInterfaceClass (Communication Device Class)
0x02 bInterfaceSubClass (Abstract Control Model)
0x01 bInterfaceProtocol (ITU-T V.250)
0x00 iInterface

CDC Header Functional Descriptor:

0x05 bFunctionalLength
0x24 bDescriptorType
0x00 bDescriptorSubtype
0x0110 bcdCDC

CDC Abstract Control Management Functional Descriptor:

0x04 bFunctionalLength
0x24 bDescriptorType
0x02 bDescriptorSubtype
0x02 bmCapabilities

CDC Union Functional Descriptor:

0x05 bFunctionalLength
0x24 bDescriptorType
0x06 bDescriptorSubtype
0x00 bControlInterface
0x01 bSubordinateInterface(0)

CDC Call Management Functional Descriptor:

0x05 bFunctionalLength
0x24 bDescriptorType
0x01 bDescriptorSubtype
0x00 bmCapabilities
0x01 bDataInterface

Endpoint Descriptor:

0x07 bLength
0x05 bDescriptorType
0x81 bEndpointAddress (IN Endpoint)
0x03 bmAttributes (Transfer: Interrupt / Synch: None / Usage: Data)
0x000A wMaxPacketSize (10 Bytes)
0x01 bInterval

Interface Descriptor:

0x09 bLength
0x04 bDescriptorType
0x01 bInterfaceNumber
0x00 bAlternateSetting
0x02 bNumEndPoints
0x0A bInterfaceClass (CDC Data)
0x00 bInterfaceSubClass
0x00 bInterfaceProtocol
0x00 iInterface

Endpoint Descriptor:

0x07 bLength
0x05 bDescriptorType
0x02 bEndpointAddress (OUT Endpoint)
0x02 bmAttributes (Transfer: Bulk / Synch: None / Usage: Data)
0x0040 wMaxPacketSize (64 Bytes)
0x00 bInterval

Endpoint Descriptor:

0x07 bLength
0x05 bDescriptorType
0x82 bEndpointAddress (IN Endpoint)
0x02 bmAttributes (Transfer: Bulk / Synch: None / Usage: Data)
0x0040 wMaxPacketSize (64 Bytes)
0x00 bInterval

String Descriptor Table

Index LANGID String
0x00 0x0000 0x0409
0x01 0x0409 “Velleman Projects”
0x02 0x0409 “K8097 - 4 Channel USB Stepper Card”

Connection path for device:
USB-xHCI-kompatibler Hostcontroller
Root Hub
K8097 - 4 Channel USB Stepper Card (VID=0x10CF PID=0x8097)

Brought to you by TDD v1.82.0, Aug 20 2013, 17:17:20

The information does not give me a help, because do not understand it enough.

Best regards
Urs

N.B. current consumption of thre K8097 is about 40mA.

4

Very welcome,

note that I don’t have one of those K8097. However, what this confirms is that the PIC is OK and that it perfectly fine enumerates with the USB stack. So the error leading to the failed connection is definitely somewhere between the demo software and the USB stack. Try reinstalling the drivers and if on a 64bit version of Windows, make sure that the DLLs are in the SysWOW64 folder.

Regards,
Jan

5

Well, on my Windows 8.1 system the file was found under
C:\Program Files (x86)\Velleman\Stepper Motor Cards\Native DLL
C:\Windows\SysWOW64

and on my old portable XP system it was found under
C:\Program\Velleman\Stepper Motor Cards\Native DLL
C:\Windows\system32

after the search scan was completed. So, the installation it should be alright.
I have reinstalled the program too, the problem remains, i.e. same error message pops up.

I think Velleman has to fix the demo software, I am right?

Best reagards
Urs

6

That looks as if it all installed in the right places. Is there anything in the event log that would give you a clue?

EDIT: This might be the problem: viewtopic.php?f=3&t=9681

Regards,
Jan

7

I know that post (i.e. viewtopic.php?f=3&t=9681). I used it to install the driver for Windows 8.1, however for XP it was not necessary (however I had to “kill” the svchost.exe for XP because it slowed down the system in such a way, that installation would have been postpone to an infinit time).
Remember, I get the failed message for both systems, XP and Windows 8.1.
Could be the NET Framework? I have seen a version 2.XY for the demo, on both computer I have the newest one NET 4.5?

Regards
Urs

8

Ah … the good old svchost slow down. I was fighting that myself lately in connection with automatic updates (wuauserv). But that’s a different story.

Unfortunately this is as far as I can help you diagnose the problem. As said, I don’t have a K8097. Hopefully someone from Velleman staff will chime in shortly.

Mit freundlichen Grüßen
Jan

9

Thank you very much for helping Jan! I wish you a nice Sunday.
I will try to solve the problem tomorrow with the Velleman stuff.
Best regards
Urs

10

To Velleman Stuff,

on my computers the MotorDemo.exe does not work (see above), however, the SMC Project.vb does (using Visual Studio Express 2013 Desktop).

What is the Demo for? It has no effect.

Best regards
Urs

11

In the demo application, what do you enter under “Port:”?

12

Hi,

sorry for late answering, I was away.
I solved the problem just now: I wrote the only port number, e.g. 3 or 4 and so on, what is wrong. By adding COM as prefix to the port number it works fine; so, correct is COM3 (or COM4 and so on).

Thanks to all for helping!

Urs

13

In general, the names of serial ports are always “COMx”, where the x is a number.

Have fun

14

Same problem with my software. If there is any issue with port number then please suggest me best way to fix this problem.