GE865 and AT#BASE64

One thought on “GE865 and AT#BASE64

  1. I’ve recently encountered strange behaviour with two of these modules which are both deployed in the field. At extremely random intervals, the device starts encoding the data it’s sending to our server to BASE64. Our code never touches AT#BASE64-command and the data these devices send is wrapped in our own binary protocol format.


    I cannot debug these devices on-site and I’m not able to reproduce the issue in our lab. Our devices have #SMSATRUN enabled, once this problem occurs I can see that the output of AT#BASE64? has changed from the default:




    #BASE64: 1,2,2,0,0

    #BASE64: 2,2,2,0,0

    #BASE64: 3,0,0,0,0

    #BASE64: 4,0,0,0,0

    #BASE64: 5,0,0,0,0

    #BASE64: 6,0,0,0,0





    Any idea how and why this happends?


    As said, we do not use the AT#BASE64 -command in our code. We do however occasionally check for a binary file in the NVM and if it exists, the file contents are ran through a couple of functions which use the binascii module, if that matters. 


    I can turn the encoding off using #SMSATRUN and AT#BASE64-command but this is still very unpredictable behaviour and we should know what’s causing it. 


    Model is GE865 and FW is 10.00.006.