Rick Reynolds

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • December 7, 2012 at 5:38 pm in reply to: Identifying SocketModem Device type… #4358
    Rick Reynolds
    Participant

    Thanks Darrik. I am using ATI3 now and have response values that seem to be relaible. I have only tried this with the G2, C1 and H4 modems so far.

    November 8, 2012 at 3:43 pm in reply to: +GCAP response meanings #4363
    Rick Reynolds
    Participant

    Thanks Tim. Looking into it now.

    Also, I am working with MultiTech support on trying to identify a reliable method for determining the SocketMode product type from software. We use MTSMC-G2, MTSMC-C1 and MTSMC-H4 as well as the -IP versions of these devices. We are also going to implement the SocketEtherenet and SocketWiFi devices in our M2M embedded system. We need the ability to identify which device is in the socket in order to know how to deal with data connections, etc…

    November 6, 2012 at 5:46 pm in reply to: iCell – Any issues using Reset Pin on a regular basis… #4352
    Rick Reynolds
    Participant

    Thanks Darrik, that definitely answers my question.

    I will implement the AT#CFUN=0 to test for carrier updates in progress.

    On 3)… Any idea on a central repositroy of this kind of information? Or do I need to contact each carrier and inquire as to the nature of there timers, re-try thresholds and any other requirements?

    Seems like there should be something in place to receive at least an unsolicited message from the carrier before they send an update. Then it would be simple to catch that message and disable resets during that time.

    November 6, 2012 at 2:47 pm in reply to: iCell – Any issues using Reset Pin on a regular basis… #4350
    Rick Reynolds
    Participant

    Just for clarification… When I referenced SocketCell modems I’m refering to the SocketCell Cell products as opposed to the iCell products.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)