RNDIS Support Via USB

  • Hi,


    Has anyone tried to use the RNDIS support vi USB as I am a bit confused on how to configure the USB Driver. I know that RNDIS is not currently operating as I have no virtual network device appearing on my desktop PC when I connect the PicoCOM4 device with the ip 192.168.55.101. If I try to resolve the host name "ppp_peer" is comes back as unresolvable.


    Looking on the web it is suggested that only USB Serial or USB RNDIS are possible at any instant and ActiveSync is operating correctly! How does ActiveSync connect?
    Should I loose ActiveSync once the PicoCom4 has been correctly configured?


    If anyone can help I would be very grateful.


    Regards
    Rick

  • Hello,


    PicoCOM4 kernel does not support RNDIS (SYSGEN_USBFN_ETHERNET) at the time.
    It may work when you order a custom kernel, contact <!-- e --><a href="mailto:sales@fs-net.de">sales@fs-net.de</a><!-- e -->.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Thanks for the reply ZU,


    I have looked at your web page literature at <!-- m --><a class="postlink" href="http://www.fs-net.de/cms/index.php?id=picocom4&L=1">http://www.fs-net.de/cms/index.php?id=picocom4&L=1</a><!-- m -->
    and under the heading Windows Embedded 6 R3 a list of drivers includes the following with no indication that its an extra??


    Drivers:
    UART (COM1, COM2)
    I²C
    Digital I/ O (DIO)
    USB Host
    USB Device (Mass Storage, RNDIS, Serial)
    SD/ SD-HC/ MMC
    Display (2D, DirectDRAW)
    Ethernet
    CAN 2.0
    Audio incl. Mixer


    As you can see USB Device supports RNDIS out of the box??


    Please can you confirm and if required update your web site.


    Regards
    Rick

  • Hello,


    ok your argument is unbeatable!
    I dont know why the SYSGEN was not set in the very first version, nevertheless i will update the kernel within this week.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • ZU,


    Just seen your change log entry, I hope you have entered a typo :-


    PicoCOM4 - V1.14 (Released 2014-11-20)
    ======================================
    - 0001939: [General] Add RNDIS - resolved
    [1 issue]


    Released 2014??? ; )


    Cheers
    Rick

  • ZU,


    Installed V1.14 kernel and change the registry setting:-


    HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers


    to a value of "RNDIS"


    rebooted pico and was promted to install new USB device as expected, if I let it install automatically no driver is found. I also tried to redirect to the folder:-


    C:\Program Files\Microsoft ActiveSync\Drivers


    But still the drivers could not be installed, can you help I am running Win XP SP3

    Cheers
    Rick

  • Hello,


    it did not use RNDIS at all, so i have no experience. But i will try ... :
    Microsoft provides a driver for host side (Rndismp.sys). This driver should be already availabel on your PC (W7, XP -> search for it). Here http://msdn.microsoft.com/en-u…re/ff569967(v=vs.85).aspx you will find some templates for the inf-files.


    Hope this helps (?)

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • ZU


    These are the steps I have completed to install the driver from ActiveSync when using NDIS.


    Change the registry values on PicoCOM4 as detailed below:-


    1) This will change the USB client driver on PicoCOM4 to be RNDIS


    [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers
    DefaultClientDriver = "RNDIS"


    2) This will allow ActiveSync to recognise the device and install the RNDIS host driver on PC


    [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]


    UseActiveSyncIds = 1


    Save these settings


    Reboot PicoCOM4 and plug in USB cable to PC, automatically install new driver.


    Open a terminal window and type ipconfig, you should now see a new LAN device


    ActiveSync will have recognised the device and will attempt to connect, on my PC this fails and trouble shooter does not find any issues.


    I can ping the LAN but not connect to the device web server through it.


    Can anyone test this facility on there PC setup and give feed back to me on the success or failures.


    ZU - I have seen an issue reported on WinCE6 R3 for Host RNDIS which drops the activesync connection and requires a hotfix to platformbuilder, do you apply hotfixes via a set procedure as routine?? Could you find out if there are any more fixes required for RNDIS as it does appear to have some issues on WinCE6.


    Regards
    Rick

  • Hi,
    - hotfix concerning RNDIS (110803) is installed.
    - When i follow your steps above, without set HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]\UseActiveSyncIds = DWORD: 1 everything works fine. Means i can connect telnet, ftp, and http via RNDIS.
    - But i am not able to connect via ActiveSync, i dont know why until now. Did you checked http://msdn.microsoft.com/en-u…76(v=winembedded.60).aspx?

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • Hm,
    i the meanwhile i checked several threads in the www. Seems that nobody get ActiveSync work over RNDIS under WCE only under WM!

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • ZU


    Are you able to ping hostname/ip define in the rndisfn1\param\tcpip registry keys??


    When I try they are not available, event turned off firewall. This is my network setup:-



    H:\>ipconfig /all


    Windows IP Configuration


    Host Name . . . . . . . . . . . . : xxxxxx
    Primary Dns Suffix . . . . . . . : xxxx
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : xxxxx


    Ethernet adapter Local Area Connection:


    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Con
    nection
    Physical Address. . . . . . . . . : xxxxxxxx
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.0.51
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.254
    DHCP Server . . . . . . . . . . . : 192.168.0.2
    DNS Servers . . . . . . . . . . . : 192.168.0.2
    Primary WINS Server . . . . . . . : 192.168.0.2
    Lease Obtained. . . . . . . . . . : 26 November 2013 16:43:12
    Lease Expires . . . . . . . . . . : 04 December 2013 16:43:12


    Ethernet adapter VirtualBox Host-Only Network:


    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapte
    r
    Physical Address. . . . . . . . . : xxxxxxxxxx
    Dhcp Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.56.1
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :


    Ethernet adapter Local Area Connection 8:


    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Windows Mobile-based Device #2
    Physical Address. . . . . . . . . : xxxxxxxxxxx
    Dhcp Enabled. . . . . . . . . . . : No
    IP Address. . . . . . . . . . . . : 192.168.0.201
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.0.2


    H:\>ping 192.168.0.200


    Pinging 192.168.0.200 with 32 bytes of data:


    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.


    Ping statistics for 192.168.0.200:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


    What OS are you on, this is XP SP3


    Regards
    Rick

  • Hi Rick,

    Code
    1. Are you able to ping hostname/ip define in the rndisfn1\param\tcpip registry keys??

    Yes,


    i download kerel contains RNDIS feature and modify only:


    Then i get following


    and can ping from host


    also i can connect "169.254.254.70" via telnet, ftp and http. So everything works, without ActiveSync:-(.


    Note, auto configuration of IP may take a while (at my system about 20s).

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

  • ZU


    Thanks for your support on this, I still cannot get my system to connect as the IP addresses are on different sub nets, I may need to remove the driver loaded on my PC to the PicoCOM Vid Pid values and retest but I have run out of time on this so will work round with wired Ethernet device for now. I still need Activesync capability when using RNDIS as I use RAPI calls over the USB connection for some of my applications so cannot run a system without ActiveSync.


    Regards
    Rick