Posts by Hüseyin

    Hi All,


    After 6/ April 2019 (GPS roll over event) customers using modules based on Sirf4 GSD4E-9333 chipset, noticed issues related to Satellite tracking. Touching base with Qualcomm Leads into a firmware patch that is mandatory to be upload into the modules.

    Qualcomm® Technologies International Ltd. (QTIL) have advised OriginGPS that they do not support operating and using GSD4e-9333 and GSD4e-9510 based devices in ROM mode without applying following software patch: GSD4e_4.1.2-P1_RPATCH_10.

    Customers must update this release to obtain the latest feature improvements and issue resolutions. Please be aware that patch uploads need to be implemented after every power cycle since these units are Rom based.

    This affects the following OriginGPS devices:

    • ORG1410 (all versions)
    • ORG1411 (all versions)
    • ORG1415 (all versions)
    • ORG1418 (all versions)
    • ORG1408 (all versions)
    • ORG4402 (all versions)
    • ORG4472 (all versions)
    • ORG4400 (all versions)
    • ORG4475 (all versions)

    Attached a zip file that contains all relevant info, please forward to various customers that are using these modules. Kindly let us know if you have any question related to this issue.


    Patchfile


    Regards,


    Round Solutions Support Team

    Telit have received several requests regarding "2019 GPS Week Rollover Notification" and we need to tell our customers what will happen and which products are affected.


    In the appendix you will find a letter to all who are affected giving you an explanation about the "2019 GPS Week Rollover Notification" which has implications for some old Telit mobile modules with GPS.

    Download 2019 GPS Week Rollover Notification

    The affected modules are:

    HE910-xxG

    DE910-xxG

    LE910-xxG


    Telit internally distributes application notes so that all Telit technical support teams and application developers are prepared to answer questions from customers:

    This problem can be solved with a simple workaround.


    Download Workaround Tutorial


    Many greetings

    The Round Solutions Team

    Hi,


    firmware is not public, you have to request from your distributor/seller.

    If you bought from Round Solutions, please send mail to ts(at)roundsolutions.com with customer or invoice number.

    Please send also answers to following AT commands:

    AT+CGMM

    AT+CGMR


    Please let me know if you have further questions.


    Regards,

    Hüseyin

    Hi Albillia,


    GPRS is for transmitting data only in 2G networks.

    Of course you could send data, in your case tranfer your serial data, to your FTP server via LTE/4G, AT commands are very similar, you could check folowing documents:

    Telit_LE910-V2_Modules_AT_Commands_Reference_Guide_r5

    Telit_Modules_Software_User_Guide_2G_3G_4G_r21


    Please let me know if you have further questions.


    Regards,

    Hüseyin

    Hi,


    Each line of the http header should be terminated with \r\n

    senddata = "POST /test0/post.php?mode=save&key=somekey&imei=someimei HTTP/1.1\r\n"

    senddata = senddata + "Host: www.xyx.com\r\n"

    senddata = senddata + "Content-Length: 45\r\n"

    senddata = senddata + "\r\n"

    senddata = senddata + "data=29/03/2019T15:42:00Z;22.20;1023.88;0.00;"

    Also it might be that the customer might need to do this:

    senddata = "POST /test0/post.php HTTP/1.1\r\n"

    senddata = senddata + "Host: www.xyx.com\r\n"

    senddata = senddata + "Content-Length: 81\r\n"

    senddata = senddata + "\r\n"

    senddata = senddata + "mode=save&key=somekey&imei=someimei&data=29/03/2019T15:42:00Z;22.20;1023.88;0.00;"

    This depends on the web server if it can interpret the HTTP headers in the first case.

    I would also recommend testing the HTTP headers using a TCP terminal like Hercules.

    the following product family announced EoL:


    Item P/N Last Time Buy Webshop EN Webshop DE
    LE910-EUG LE910EUG703R002 08/31th/2018 please call bitte anrufen
    LE910EUG703T001 08/31th/2018 Link Link
    LE910EUG712T001 08/31th/2018 Link Link
    LE910EUG703T007000 08/31th/2018 please call bitte anrufen
    Interfaceboard-EVK2 PCB-LE910EUG 08/31th/2018 Link Link
    PCIe LEPCIEUG703T001 08/31th/2018 Link Link
    PCIe LEPCHEUG712T001 08/31th/2018 Link Link
    Replacement Module R-UC864-L9EUG 08/31th/2018 Link Link
    AarLogic Modem TER-LN910-EUG 08/31th/2018 Link Link
    AarLogic Modem TER-EZ910_LE-EUG 08/31th/2018 Link Link
    AarLogic Extension EXT-RPI-4G-EUG 08/31th/2018 Link Link
    LE910-SKG LE910SKG703T004 08/31th/2018 Link Link


    Your next steps:

    1. Determine your last-time buy needs for the part numbers listed above to prepare orders before the Last Time Buy deadline.

    2. Look for the right replacement options listed below or talk to our experts here in the forum.

    3. Review, consider and select a module to succeed your EoL product from the portfolio of possible Telit IoT modules.

    If you have any questions or need more information please contact us and request an appointment with one of our IoT experts.

    REQUEST AN APPOINTMENT


    As replacement for the above parts, and for applications not requiring the GNSS functionality, Telit offers the LE910-EU V2, LTE Cat 4, which supports also the additional LTE bands 900 and 2100 MHz, required in some countries, due to 2G/3G spectrum refarming.

    As second variant you can use LE910-EU1, LTE Cat.1.


    LE910-EU V2 webshop link

    LE910-EU1 webshop link


    If you require GNSS please have a look at Telit GNSS Bundle Solutions:


    The Telit Bundle Solution represents an alternative way to integrate such Cellular + GNSS applications.



    This solution requires that the main UART of the GNSS receiver has to be connected directly to the 2nd UART of the Cellular module (often it is the TRACE UART).

    Some cellular GPIOs need to be connected to the GNSS receiver to manage some key pins (power control, boot, ..., etc.).

    This implementation has pros and cons. Some pros of the Telit Bundle Solution are:

    · only one UART is used by the application processor;

    · no effort is required to integrate and manage the GNSS protocol, since the GNSS receiver is managed by the Cellular module through AT commands;

    · the A-GPS Downloader/Manager is already embedded into the Cellular module’s SW;

    · the Patcher SW engine (for GNSS ROM receivers only) is already embedded in the Cellular module’s SW;

    · the Application microprocessor could be removed and the whole application managed by the Python or AppZone engines running into the Telit cellular module.

    Some cons of this solution are that:

    · the cellular module has to be in power-on status every time the microprocessor needs to send, update or exchange data with the GNSS receiver. This results in a more complex power management in order to match a power consumption comparable with standard solution;

    · not all the features of the GNSS receiver can be driven through the cellular module (see the Telit AT Commands User guide [1]).

    The Telit Bundle solution’s advantage is to combine multiple technologies and manage the whole set through a single dedicated communication port.

    In the Telit Bundle solution, the cellular module is the master while the GNSS receiver is the slave.

    The GNSS receiver is managed through the cellular module using dedicated AT commands; in this case, customers do not need to know or use any other protocol to manage the external GNSS receiver.

    Moreover, this solution does not require to include any A-GPS Download Manager or Patching SW engine in the external Application Microprocessor to manage A-GPS aiding and ROM Patcher SW engine.

    In fact, the Telit Bundle solution is composed by different SW blocks that allow customers to manage, keep up-to-date and assist the GNSS receiver.


    For more information please look: 80000NT11300A_Telit_GNSS_Bundle_Application_Note_r7.pdf


    If you have further question, please fell free to contact our technical support: ts (at) roundsolutions.com

    Hello,


    first you should update your Firmware, this will fix some errors and you will have a base to get better support.
    Newest Version is 10.01.151


    Please get in contact with your distributor for Firmwarefiles.


    Regards,


    Hüseyin

    Dear Prashanth K,
    The most common reasons for SSL handshake error are due to:


    • incorrect CA certificate (not the true root)
    • During the handshake process, the server is sending a certificate that is higher as SHA-256 signature algorithm, but the GL865 SSL client only supports up to SHA-256, if I remember right, so the handshake will fail.


    Please check this points and report.


    Regards,
    Hüseyin

    Hi sebastiaan,


    please can you send me following AT command answers:


    AT+CGMM
    AT+CGMR


    Is anything different in your configuration, like location or antenna?


    Regards,


    Hüseyin

    Hi Nimesh,


    here Taj explained me before how to get right certificate:


    "Google is a more complex organization and getting
    the right CA certificate is a bit more complicated.


    The certificate that you are getting with the procedure described in the guide
    was an intermediate certificate in the past,


    -> one of the intermediate certificates was changed to Root CA and
    the browser on your PC already has this "new" Root CA, so it doesn't
    show you the "true" old Root CA.




    When you connect to Google's server, it sends you a complete chain, which still
    has the old chain.




    To view this chain you can use "openssl" tools:


    openssl s_client -showcerts -connect www.google.com:443 "


    Regards,


    Hüseyin

    Dear CloudGate user,


    Our latest CloudGate LuvitRED version 2.12.0 has been released and is now available on CloudGate Universe.


    Minimum firmware: 2.76.1


    Nodes:
    • new schedule node
    Features:
    • bacnet: schedule support
    Improvements:
    • mbus: improved scan procedure
    • zigbee: new firmware 0x0112000E
    Editor:
    • disable tabs in a flow
    • bacnet schedule example
    • fix duplicate examples


    Take me to the CloudGate Universe
    http://cloudgateuniverse.us9.l…d=413db29c32&e=bfae90c8c7