Author Message

<  Device Information  ~  Dymo LabelManager Wireless PnP

PostPosted: Tue Feb 21, 2017 11:19 pm Reply with quote
Posts: 3Joined: Tue Feb 21, 2017 11:10 pm
Hi.

The Dymo LabelManager Wireless PnP is not properly supported by usb_modeswitch.

USB-ID: 0922:1007 --> 0922:1008

Only the second configuration provides a USB-Printer profile.

There is a config file already available in the configPack.tar.gz, but it seems incomplete, since Message/ResponseEndpoint are not specified. This is easy to fix though - they're both 0x01:

Code:
# Dymo LabelManager Wireless PnP
TargetVendor=0x0922
TargetProduct=0x1008
MessageEndpoint=0x01
ResponseEndpoint=0x01
MessageContent="1b5a01"


The same problem (missing Endpoint specification) probably applies to the Dymo LabelManager 420P (0922:1003 --> 0922:1004) as well, but I can't verify this since I don't own this printer.

I have adjusted configPack.tar.gz locally on my system and it works for my LabelManager Wireless PnP as expected.

Please incorporate this change into your package.

Thanks,
Simon


Offline Profile
PostPosted: Wed Feb 22, 2017 12:31 am Reply with quote
Site AdminPosts: 6360Joined: Sat Nov 03, 2007 12:30 am
Hmm, can you provide the output of "lsusb -v -d 0922:1007" when the device is still in the initial mode?


Offline Profile
PostPosted: Sat Feb 25, 2017 4:24 am Reply with quote
Posts: 3Joined: Tue Feb 21, 2017 11:10 pm
Josh wrote:
Hmm, can you provide the output of "lsusb -v -d 0922:1007" when the device is still in the initial mode?


Sure. Attached are lsusb output for both: 1007 and 1008 (serial number redacted).

Thanks,
Simon
Attachments:
File comment: after usb modeswitch
lsusb-0922-1008.txt [4.45 KiB]
Downloaded 57 times

File comment: before usb-modeswitch
lsusb-0922-1007.txt [3.38 KiB]
Downloaded 64 times

Offline Profile
PostPosted: Sat Feb 25, 2017 10:16 am Reply with quote
Site AdminPosts: 6360Joined: Sat Nov 03, 2007 12:30 am
Ah, I see - the message is directed to an interrupt endpoint. I will correct the configuration and try to find a confirmation that the same goes for the LabelManager 420P.

Furthermore, I just noticed that the whole response part might be totally unneeded in this case and probably others.
Are you working with a distribution package of usb_modeswitch or with the source code from this site? I might post a test version for you to try which skips the response code for non-storage transfers.


Offline Profile
PostPosted: Sat Feb 25, 2017 1:32 pm Reply with quote
Posts: 3Joined: Tue Feb 21, 2017 11:10 pm
Josh wrote:
Ah, I see - the message is directed to an interrupt endpoint. I will correct the configuration and try to find a confirmation that the same goes for the LabelManager 420P.

Furthermore, I just noticed that the whole response part might be totally unneeded in this case and probably others.
Are you working with a distribution package of usb_modeswitch or with the source code from this site? I might post a test version for you to try which skips the response code for non-storage transfers.


I am working with the debian unstable (sid) package:

Code:
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  usb-modeswitch 2.5.0+repack amd64        mode switching tool for controlli
ii  usb-modeswitch 20170120-1   all          mode switching data for usb-modes


Thanks,
Simon


Offline Profile
PostPosted: Thu Aug 03, 2017 10:03 pm Reply with quote
Site AdminPosts: 6360Joined: Sat Nov 03, 2007 12:30 am
The "0922:1001" configuration confirms that the same endpoint setting applies to annother model. I'll just take it for granted that all similar USB products from that maker share the same mode switch configuration.


Offline Profile
PostPosted: Thu Aug 03, 2017 11:01 pm Reply with quote
Site AdminPosts: 6360Joined: Sat Nov 03, 2007 12:30 am
simon,

in case you are still following this and still have access to the device - can you test the binary attached here in place of your's?
You can just rename or move your original package version, then put in the test version in its place. It's compiled for amd64.

The difference is that it does not try to read from the endpoint after writing to it. I would like to confirm that the read is unneeded in your case.
Attachments:
usb_modeswitch.zip [20.67 KiB]
Downloaded 38 times

Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 1
7 posts
Users browsing this forum: No registered users and 1 guest
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
cron