ELS61-E2 unexpected reply to SMONI | Telit Cinterion IoT Developer Community
February 1, 2019 - 3:03pm, 1434 views
Hi
Fromt the documentation the reply to an AT^SMONI command should start with "^SMONI: " but this is not the case below:
AT^SMONI
AT^SMONI
--,--FDD,--,FFFFFFFF,10,--,-69,-17.0,CONN
OK
Is this, perhaps, a normal reply but not documented?
Thanks,
Hello,
You are right that SMONI reply should start with '^SMONI:'. Can you write more - do you always get such reply?
Please paste ATI1 and AT^SCFG? outputs. Do you experience any problems with this module? Does it register and communicate? Does it throw any special URCs?
Regards,
Bartłomiej
Hi
I've only seen it once.
ATI1
ATI1
Cinterion
ELS61-E R2
REVISION 02.000
A-REVISION 01.000.01
OK
AT^SCFG?
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/mode/ASC1","gpio"
^SCFG: "Gpio/mode/DAI","gpio"
^SCFG: "Gpio/mode/DCD0","gpio"
^SCFG: "Gpio/mode/DSR0","gpio"
^SCFG: "Gpio/mode/DTR0","gpio"
^SCFG: "Gpio/mode/FSR","gpio"
^SCFG: "Gpio/mode/MCLK","gpio"
^SCFG: "Gpio/mode/PULSE","gpio"
^SCFG: "Gpio/mode/PWM","gpio"
^SCFG: "Gpio/mode/RING0","gpio"
^SCFG: "Gpio/mode/SPI","gpio"
^SCFG: "Gpio/mode/SYNC","gpio"
^SCFG: "Gpio/port/MCLK","GPIO4"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","ELS61-E R2"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Comp1",""
^SCFG: "MEopMode/CregRoam","0"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MeOpMode/SRPOM","0"
^SCFG: "Radio/Band/2G","0x00000014"
^SCFG: "Radio/Band/3G","0x00000081"
^SCFG: "Radio/Band/4G","0x08080085"
^SCFG: "Radio/Mtpl/2G","0"
^SCFG: "Radio/Mtpl/3G","0"
^SCFG: "Radio/Mtpl/4G","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "RemoteWakeUp/Event/USB","none"
^SCFG: "RemoteWakeUp/Ports","current"
^SCFG: "RemoteWakeUp/Ports","powerup"
^SCFG: "Serial/Ifc","0"
^SCFG: "Serial/Interface/Allocation","0","0"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","005B","Cinterion Wireless Modules","ELSx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/TLS/Version","MIN","***"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "Urc/Ringline","local"
^SCFG: "Urc/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","0"
OK
This specific module works generally fine. We have many of them around including US and AUS variants. Some ***** we have issues registring and with modems falling off the USB bus. When it registers, it communicates fine and we don't see any special URC coming up.
Hello,
So for now one thing is certain that this is not the regular and documented output. As some values are missing I suppose that at the moment of command execution the module was unable to collect all the necessary values to place in the reply for some reason.
For now it's hard to say anything more. As it is not happening regularly and is not accompanied by any module's inappropriate behavior I think that we should not treat as any fault.
Best regards,
Bartłomiej