Posts by uli

    These providers showed the effect:


      Vodafone (D)
      T-Mobile (D)
      A1 (A)


    The communication related commands before AT+CMGL="ALL" are:


    ATE0
    AT+CMEE=2
    AT#STARTMODESCR=1,10
    AT#CMUXSCR=0,115200
    AT#SELINT=2


    AT&K3
    AT+ICF=3
    AT+CSDH=0
    AT+CNMI=0,0,0,0,0


    AT+CPIN= ...
    AT+CREG?' ...
    AT+COPS ...


    AT+CGDCONT="%s"
    AT+CGQREQ="%s"

    Among other commands for GPRS / email GPIO ...

    Q: Type of module? A: ter110
    Q: Firmware version? A: 7.3.501


    the issue was already discussed but not answerde in the thread Unreliable SMS reception


    SMS are sent to the module but not delivered or mayby very late after one or two days.


    A check for new SMS is done with AT+CMGL="ALL" i.e. list all SMS stored on the SIM card. The SMS are process and delete afterwards, therefore the SIM card memory ought to be emty. Besides the effect shows on new SIM cards too.


    The same SIM card in a mobile phone does receive a SMS almost at once.


    It appears the SMS are delivered in short time if a call has been made or an SMS has been sent but not if an email has been sent.


    Sending an SMS to the module has been working fine for the last years thus I assume the condition for delivering SMS was changed by the network providers (like the prepaid credit call *100# which suddenly was not furthermore supported).


    Is there a command to query the network for pending SMS instead of checking the SIM card memory?


    Do I have to order different phone contract with a guaranteed immeditate SMS delivery?

    ter gx 110s


    the GPIO 4 didn't show any function. Comparison with other devices had shown that the two jumper next to the RJ11 jack were missing.


    Curiously enough the GPIOs 5,6 and 7 did work.


    The Software and the GM862 did also work, I chekct the levels at the labled soldering pads on the PCB, while I was accessing the GPIOS.



    Please provide information about the jumper settings.


    I'm also interestet about the colour dots on the bottom side of the housing, what do they say. By now I've spotted blue, yellow and purple. If it's your Quality control, it's been two "purple" devices with missing jumper.

    it's already some time ago when I had the same problem but it was limited to 512 byte but that was with older hardware (TER110 FW: 6.4.604). I didn't try to send more than 512 bytes since than. Have things changed?

    I had already noticed that I was missing emails, but I couldn't find out why. Thats why I send an SMS to the providers email gateway in case I have not successfully send my email. The SMS contains the GPRS status, CGATT status and the result of AT#MONI. I sent the email about every half hour over the last night. Well look for yourself.


    (newest message from 2:00)
    GPRS: 1 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-99dbm TA:1
    GPRS: 1 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-99dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-100dbm TA:0
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:1 LAC:0325 Id:1027 ARFCN:826 PWR:-105dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:1 LAC:0325 Id:1027 ARFCN:826 PWR:-106dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-105dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-101dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-103dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-103dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-101dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-101dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-103dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-100dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-101dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-103dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-103dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-106dbm TA:0
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:2 LAC:0325 Id:1027 ARFCN:826 PWR:-107dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-104dbm TA:0
    GPRS: 0 CGATT: 0 (e-plus) T-Mobile D BSIC:35 RxQual:0 LAC:690B Id:72F6 ARFCN:42 PWR:-53dbm TA:1
    GPRS: 0 CGATT: 0 (e-plus) E-Plus BSIC:33 RxQual:1 LAC:0325 Id:1027 ARFCN:826 PWR:-105dbm TA:1
    GPRS: 0 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-100dbm TA:1
    GPRS: 0 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-97dbm TA:1
    GPRS: 0 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-95dbm TA:0
    GPRS: 0 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-96dbm TA:1
    GPRS: 1 CGATT: 1 (e-plus) E-Plus BSIC:33 RxQual:0 LAC:0325 Id:1027 ARFCN:826 PWR:-95dbm TA:1
    (oldest message from 18:00)


    (1) the rradio power is decreasing overnight. Has anybody an explanation for this? Typical power during the day would be -75dbm. Could it be the the provider is reducing the power e.g. to save energy? It's very hot these days the transmitter might have heated up during the day and cooled down in the evening this would fit pretty good to the time and the gradually de- and increasing power.


    (2) at very low radio power (< -105dbm) the quality decreases too.


    (3) loosing the ability to connect to GPRS and I'm trying hard to connect with long timeouts and several retries.


    (4) same with CGATT.


    (5) At one occaison it even cannot recognise its own netwoork! How can that be, because it was still able to send an SMS?


    You see me puzzled: what can I do?



    Q: Type of module? A:ter110
    Q: Firmware version? A: 7.3.5

    Quote

    Originally posted by Wilhelm
    No will not come.


    If you leave everything as is, would be OK by me.


    Quote

    Originally posted by Wilhelm
    For more ports you can use our Aarlogig C05 for example.


    Even the blank module costs more than double and it has got neither a baseboard and nor a housing. Sorry that's not an option.

    Thanks Olaf,


    is the TER-GX300 fully compatible to TER-GX110? Are there any known issues that have to be considered in case of a change?

    The TER 110 internally has a second serial port which is usable in conjunction with a level adaption (TTL to RS232).


    As this is not a documented feature I would like to know if it is available in future. You may want to release a new PCB revision and remove or resize the connection.


    I desperatly need a second serial port. Another solution would be if you implement a serial port via one of the IO pins as you did for example for IIC. A separate function for Tx and Rx would save me one of the IO pins, because I only want to read.

    recently I've noticed a change of the moduls name. The name of the TER-GX-110S differs at the end where it is a 'S' or a 'K'. What's the difference?
    I had a look at your hompage but couldn't find anything. Did I miss the product overview? I read about other TER like 104, 105, 300, 400, ... What are they especialy good for?

    sending an SMS gave me this invalid text mode parameter error:
    +CMS ERROR: 305


    The cause was well hidden. The text I sent was copied from a word document. This text containd a minus (-) which looked like the other - in the SMS text which I typed manually. Only the window of hyperterminal showd me a û. The log file from hyperterminal showd the - again but a hex viewer made clear that the real - is 0x2D and the false - is 0x96 which is the ASCII code of û.


    I want to avoid these kind of error in future. Which characters are allowed? Maybe all with ASCII code below 128 and perhaps above 31?

    Once I'm registered at the network I can find the name
    at+cpin?
    +CPIN: READY


    at+creg?
    +CREG: 0,1


    at+cops=?
    +COPS: (2,"E-Plus",,"26203"),(3,"Vodafone D2",,"26202"),(3,"T-Mobile D",,"26201"
    ),(3,"o2 - DE",,"26207"),,(0-4),(0,2)


    at+cops?
    +COPS: 0,0,"E-Plus"


    at#moni
    #MONI: E-Plus BSIC:33 RxQual:0 LAC:0EDD Id:1027 ARFCN:826 PWR:-76dbm TA:0
    atp


    @ Wilhelm
    Do you know why Franks provider name is hidden behind by a number where german provider names are not. I'm always worried if you can make thing this or that way. That means you have to make it both ways to be sure that it works at least in one way. :(


    at+copn
    (...)
    +COPN: "26201","T-Mobile D"
    +COPN: "26202","Vodafone D2"
    +COPN: "26203","E-Plus"
    +COPN: "26207","o2 - DE"
    (...)
    +COPN: "72234","AR PERSONAL"
    (...)

    That doesn't make a difference. I've copied my whole pythen dierctory to a PC with proper serial ports and get the same exception.


    BTW: when I started to use the GM862-PY I got confused with the function names of the serial port. E.g. I mixed up SetSpeed() (port on the PC) and set_speed() (port on the module). Is there a reason for the differnet names of the same thing. I would expect to use the same commands no matter on which platform my software is located.
    Think of a general tool you've written and you want to reuse it elswhere - you can't, first you have to replace Telit python by standard pythen.

    no, it wasn't the firmware it was due to Memory Limits as described in chapter 5.1 as described in Easy Script in Python (r5)


    I revised my code and reduced the total amount of variable names by reusing the same name in all functions and I terminated strings with \r.


    Using MemCheck as described I found that I now have space for some 120 names left, where I started with missing space.


    Are ther further optimisations to save memory?

    Quote

    Originally posted by Wilhelm


    The extension should be all time *.pyo


    This is the GPIO.py located in %ProgramFiles%\Python on my PC.
    As I've read in the manual the function accessing the IOs on the TER is not using the AT#GPIO command but a more efficient function that is closer to the hardware implementation. Otherwise I would already have written my own GPIO using AT#GPIO and avoid this problem. In fact I had to modify the GPIO.py of the Telit package to avoid the program crash caused by the try to convert a non digit character to an integer.


    Quote


    I don't understand, please explain. Thank you.


    Thats Telit code, you'll find it in GPIO.py


    Quote

    I would suggest make the same test direct in your module without your PC and post me the result. Thanks.


    The problem does not exist on the module since the manual states that it is a different implementation and I have not observed this error on the module.


    ------------------------------------------------
    Any suggestions to the "serial" exception?

    TER GX 110S (7.03.500)
    Telit Python 1.5.2+ Package


    set COM Ports with Telit COM Port Selection Tool to
    MDM: com1
    SER: com9
    MDM2: no com
    SER2: no com


    The Application, which will be uploaded to the TER, is located in one directory on my PC. That is all *.py, *.ini, ... files plus exceptions.py from Python directory.


    It works fine, so far, except that after my last command has been executed this exception gets thrown, when the application is closing.


    One drawback might give a hint. My thread T:getRI() vs. CPAS: 3 suggests that not all functions of the MDM and SER library are available in the PC version of this library.
    Another clue could be that the control lines of the serial port are monodirectional, e.g. RING is an output of the TER and an input of the PCs com port. Does that help?


    Another disadvantage is that GPIO.getIOvalue (Telit extension GPIO.py) sometimes returns neither 0 nor 1.


    Code
    1. while((resp.find('OK') == -1) and (resp.find('ERROR') == -1) and (time.time() < timer)):
    2. resp = resp + MDM.mdmser.read()
    3. if resp.find('ERROR') != -1:
    4. result = -1
    5. else:
    6. commapos = resp.find(',')
    7. stat = resp[commapos+1]
    8. result = int(stat)
    9. return result


    If you have already received something (not ERROR, not OK) and a timeout occured you set stat to the first character of the received string which even might not be a digit. Bad thing to do: int('c') ;)


    P.S.:
    I've just seen that I'd previously posted this issue please see: GPIO.getIOvalue() occasionally returns 5 or crashes
    It's not fixed yet but I think the explanation above is quite plausible. Perhaps someone could update the other (closed) thread.
    thx

    Q: Type of module? A:gm862py
    Q: Firmware version? A: 7.3.500
    Q: Type of starter kit you have?s2


    get.RI() does not return 1 on incoming calls if the script is run on the PC.
    A possible workaround could be using AT+CPAS it returns a 3 if its ringing.


    Could Telit fix that in their Python package?