# AwUsbApi connect to specific group with Driver API **URL:** \ **Category:** Edgeport\ **Tags:** anywhereusb14, api\ **Created:** [May 9, 2016, 12:15pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732 "2016-05-09T12:15:05Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Zurvarian](https://avatars.discourse-cdn.com/v4/letter/z/9fc348/32.png) [@Zurvarian](https://forums.digi.com/u/Zurvarian)\ **Post date:** [May 9, 2016, 12:15pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/1 "2016-05-09T12:15:05Z")
We are trying to configure remote connections to a AnywhereUSB/14 hub using the C++ API library under “Advance” directory. At the moment we have been able to connect to the Hub successfully, but, and this is the problem, we were only able to do it to Group 1 (Marked as default in the UI Admin console). We need to be able to select which group we want to connect, as we will have each port mapped to a single group and in each of those ports we will have different devices. According to the headers file in the same directory “AwUsbApi.h” this is done by appending the group number as a port to the remote IP (e.g. 192.168.1.10:3 where 3 stands for Group number 3) But in the PDF under the same directory, this configuration is missing, which makes me think that is something experimental that somebody forgot to remove from the Code Documentation. Funny is that the UI utility is able to do it, I mean to connect to a particular group as opposite to the C++ API. Did someone knows how to do it? Driver version: 3.80.200 C++ API revision: “Revision: 2 Date: 2009-10-07 22:01:17Z” ?? This comes from the headers file, but in it also is listed a 3 revision? Difficult to say… SO: Virtual Box running a Windows 7 32 bits. ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [May 9, 2016, 4:11pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/2 "2016-05-09T16:11:42Z")
The documentation may need to be updated. Are you saying this does actually work though? ---
**Author:** ![Zurvarian](https://avatars.discourse-cdn.com/v4/letter/z/9fc348/32.png) [@Zurvarian](https://forums.digi.com/u/Zurvarian)\ **Post date:** [May 10, 2016, 8:14am UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/3 "2016-05-10T08:14:03Z")
No, it is the opposite. Let me put an example to clarify the question: When using the C++ API if I pass “10.0.0.1:2” as the Hub IP address (IP is not real, just an example) I expect it to connect to group number 2, but what I saw when testing it is that it connects to group number 1 instead. I guess that the reason is that the C++ API is not parsing the group number properly and then it uses the Default Group as defined in the Web UI, I cannot verify if this is true, though, as the Default Group is disabled in the Web UI. Using the desktop application, I was able to connect to group 2 without problems, though. ---
**Author:** ![jaxpod](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jaxpod](https://forums.digi.com/u/jaxpod)\ **Post date:** [May 27, 2016, 8:37am UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/4 "2016-05-27T08:37:34Z")
I can also confirm that setting a group as per the DLL export definitions/instructions in the included header file does not work. Is there a newer DLL version that supports group? ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [May 27, 2016, 6:08pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/5 "2016-05-27T18:08:11Z")
I’ll discuss this with the AnywhereUSB developer and see when he can get this fixed. ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [June 9, 2016, 11:08am UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/6 "2016-06-09T11:08:34Z")
To answer your question, no, not yet. I’m working with the AnywhereUSB developer to get an updated version. ---
**Author:** ![jaxpod](https://avatars.discourse-cdn.com/v4/letter/j/34f0e0/32.png) [@jaxpod](https://forums.digi.com/u/jaxpod)\ **Post date:** [June 19, 2016, 9:44pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/7 "2016-06-19T21:44:06Z")
Any chance to provide an expected timeline for a fix? This is a blocker on a project so we need to know if we can rely on a fix or take another path. Thanks! ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [June 21, 2016, 2:28pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/8 "2016-06-21T14:28:56Z")
Sure, I’ve started looking into this and will post a response here when I have more info. ---
**Author:** ![dudi](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@dudi](https://forums.digi.com/u/dudi)\ **Post date:** [July 5, 2016, 6:12pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/9 "2016-07-05T18:12:58Z")
When will the bug be fixed ? ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [July 12, 2016, 10:38am UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/10 "2016-07-12T10:38:44Z")
I’m afraid I’m not yet sure and have started investigating this. ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [July 22, 2016, 2:24pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/11 "2016-07-22T14:24:29Z")
I have good news, everyone. I expect to get an updated AWUSB API .dll very soon, hopefully sometime today, otherwise this coming Monday. Once I have it, I’ll provide a link for you to download then test it. Thanks so much for your continued patience! ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [July 22, 2016, 5:11pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/12 "2016-07-22T17:11:51Z")
The updated AWUSB API .dll can be downloaded here: [https://na14.salesforce.com/sfc/p/d0000000eJxP/a/d0000001Lv6H/ThyqmQx94a6fxfPap5J20drI9uEyjoJqrqwyat1kWFc](https://na14.salesforce.com/sfc/p/d0000000eJxP/a/d0000001Lv6H/ThyqmQx94a6fxfPap5J20drI9uEyjoJqrqwyat1kWFc) Please note: Both the 32-bit and 64-bit versions of the .dll should be included in the .zip file The release version is 3.82.207 and this should be considered BETA. This link will expire in a few months, in October 2016. I’m very interested to hear feedback from you all, so please respond and let me know how your testing goes. And thanks so much for your patience! ---
**Author:** ![bigcat](https://avatars.discourse-cdn.com/v4/letter/b/9fc348/32.png) [@bigcat](https://forums.digi.com/u/bigcat)\ **Post date:** [November 21, 2018, 8:13am UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/13 "2018-11-21T08:13:02Z")
hi can you re-upload the dll? the link is not working ---
**Author:** ![jeremym](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@jeremym](https://forums.digi.com/u/jeremym)\ **Post date:** [May 9, 2019, 8:04pm UTC](https://forums.digi.com/t/awusbapi-connect-to-specific-group-with-driver-api/16732/14 "2019-05-09T20:04:22Z")
Hi, I know I am very late to replying to this, but “better late than never”, I hope. I want to let you (and everyone else) know that this issue should be fixed in the .dll that is bundled with the latest AWUSB driver.