-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VHCI failure for OMRON PLC #56
Comments
@halimselim : I tried your usbip server several times. All results were same that vhci failed after selecting configuration. In the window kernel log, IRP_MN_REMOVE_DEVICE was shown after selecting configuration. Maybe ORMON plc driver removed it. There were no warning or error in logs of usbip-win. By the way, your server cannot be attached any more because your device was not detached by mistake before my client was to be reset. If a usbip connection is lost without detach, a stub server should seem to be reset manually. |
Thank you for testing, I rebinded the device. What do you suggest me to do ? Device driver works fine when connected to usb directly, but fails with usbip. And usbip shows no error as you say. Is there anything we could do ? |
I try again to attach to your server.. and never forget to detach it. We should check if usb compatible ids are same for both cases(via usbip-win or directly). Can you compare usb identifiers? For more details, please refer to |
Here's are logs from my testing: usbip_log.txt, debug_pdu.log Your server returned -EPIPE(-32) for selecting configuration. Your server log may contain useful information. Can you share it? |
filtered server log (/var/log/syslog) is attached I can give ssh access to the server if anyone needs. |
@halimselim : The server log also said that selecting conf failed with -EPIPE. Control port may be stalled. I need to check further that vhci handles correctly the result code. |
@halimselim : Is PLC_NS driver correct ? The driver removes the usbip device after selecting configuration even if a vhci forcefully returns success code. |
If you connect to my local pc, I will plug in omron plc to the physical usb port. Then you will be able to compare the difference. Driver loads successfully. |
@halimselim : I do not suspect the correctness of a PLC driver. I asked you that driver files to be installed are located in CXOne-Drivers2017/drivers/USB/8/PLC_NS/64bit folder of driver zip. |
Yes that's correct. I reinstalled to confirm. |
@halimselim : When a plc is directly attached without usbip-win, what are driver file details and compatible ids of the device? They can be found from device properties in the device manager. |
Here is lsusb -v result: lsusb_v.txt |
omrondriver.txt |
@halimselim : Sadly, compatible ids are same between a real device and a virtual device via usbip-win. I had asked also driver file details. Which drivers are loaded for a plc device ? That information resides in a driver tab of a properties window. |
@halimselim : Loaded drivers are also same.. |
@halimselim : Was ws2.pcapng in the zip file generated with a plc driver directly attached without usbip-win? But the wireshark log you've sent is exactly same with usbip-win log. Weird!! |
Yes it is the log of direct attach |
I know that eltima software works well with this plc. When it is installed it creates its own branch (Eltima Usb Stub) under Device Manager tree. But usbip is listed under System Devices branch. Could it be related ? |
This means that device classes of both case are different: Eltima Usb Stub(custom device class) and System(usbip-win). In my opinion, such a difference does not matter. By the way, is it USB class(not system class) for usbip-win and directly attached case ? Now, I should look into the beginning parts of usbip-win logs such as IRP_MN_QUERY_XXX related stuff. In fact, many bus queries have not been handled properly in usbip-win because there's no problem with unhandled queries. It can be a long journey. It may be better to use eltima.. 😢 |
Yes Omron PLC appears under "Universal Serial Bus Controllers" in both cases. We will be watching the developments, thanks for your time. |
VHCI fails for OMRON PLC. Detailed description is here: #52 (comment)
The text was updated successfully, but these errors were encountered: