[Ovmsdev] 3G network
Mark Webb-Johnson
mark at openvehicles.com
Wed Jul 3 08:38:07 HKT 2019
I got a sample. Physically and electrically, it is pretty much a drop in replacement for the SIM5360. But, the firmware (and AT commands) are different.
V (69794) simcom: rx: 0a 4f 4b 0d 0a | .OK..
D (69794) simcom: rx line ch=0 len=2 : OK
V (71754) simcom: tx: 41 54 2b 43 47 4d 52 3b 2b 49 43 43 49 44 0d 0a | AT+CGMR;+ICCID..
D (71754) simcom: tx scmd ch=0 len=16 : AT+CGMR;+ICCID
V (71764) simcom: rx: 0d 0a 2b 43 47 4d 52 3a 20 4c 45 31 31 42 30 32 | ..+CGMR: LE11B02
V (71764) simcom: rx: 53 49 4d 37 36 30 30 4d 32 31 2d 41 0d 0a 0d 0a | SIM7600M21-A....
D (71774) simcom: rx line ch=0 len=26 : +CGMR: LE11B02SIM7600M21-A
(redacted)
V (71774) simcom: rx: 4b 0d 0a | K..
D (71774) simcom: rx line ch=0 len=2 : OK
V (74754) simcom: tx: 41 54 2b 43 4f 50 53 3f | AT+COPS?
D (74754) simcom: tx scmd ch=0 len=8 : AT+COPS?
OVMS# metrics list mdm
m.net.mdm.iccid (redacted)
m.net.mdm.model LE11B02SIM7600M21-A
V (75754) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 33 | AT+CMUXSRVPORT=3
V (75754) simcom: tx: 2c 31 0d 0a | ,1..
D (75754) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=3,1
V (75764) simcom: rx: 0d 0a 45 52 52 4f 52 0d 0a | ..ERROR..
D (75764) simcom: rx line ch=0 len=5 : ERROR
V (76754) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 32 | AT+CMUXSRVPORT=2
V (76754) simcom: tx: 2c 31 0d 0a | ,1..
D (76754) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=2,1
V (76764) simcom: rx: 0d 0a 45 52 52 4f 52 0d 0a | ..ERROR..
D (76764) simcom: rx line ch=0 len=5 : ERROR
V (77754) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 31 | AT+CMUXSRVPORT=1
V (77754) simcom: tx: 2c 31 0d 0a | ,1..
D (77754) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=1,1
V (77764) simcom: rx: 0d 0a 45 52 52 4f 52 0d 0a | ..ERROR..
D (77764) simcom: rx line ch=0 len=5 : ERROR
V (78754) simcom: tx: 41 54 2b 43 4d 55 58 53 52 56 50 4f 52 54 3d 30 | AT+CMUXSRVPORT=0
V (78754) simcom: tx: 2c 35 0d 0a | ,5..
D (78754) simcom: tx scmd ch=0 len=20 : AT+CMUXSRVPORT=0,5
V (78764) simcom: rx: 0d 0a 45 52 52 4f 52 0d 0a | ..ERROR..
D (78764) simcom: rx line ch=0 len=5 : ERROR
V (79754) simcom: tx: 41 54 2b 43 4d 55 58 3d 30 0d 0a | AT+CMUX=0..
D (79754) simcom: tx scmd ch=0 len=11 : AT+CMUX=0
Then it resets, as our firmware interprets that as a CMUX failure.
I did manage to type manual commands and get a 4G LTE connection established. It seems that the AT+CMUXSRVPORT commands are no longer support (necessary?). Also forcing a ’simcom setstate MuxStart’ at the appropriate time (just after " AT+CMUXSRVPORT=0”) gives us:
D (713784) simcom: rx line ch=2 len=14 : CONNECT 115200
I (713784) simcom: PPP Connection is ready to start
I (714754) simcom: State: Enter NetMode state
I (714754) gsm-ppp: Initialising…
I (714944) gsm-ppp: StatusCallBack: None
I (714944) gsm-ppp: status_cb: Connected
I (714944) gsm-ppp: our_ipaddr = 10.170.204.16
I (714944) gsm-ppp: his_ipaddr = 10.64.64.64
I (714944) gsm-ppp: netmask = 255.255.255.255
I (714944) gsm-ppp: our6_ipaddr = ::
D (714944) events: Signal(network.interface.up)
D (714964) events: Signal(system.modem.gotip)
D (714964) netmanager: Saved DNS#0 212.9.0.135
D (714964) netmanager: Saved DNS#1 212.9.0.136
D (714984) events: Signal(network.modem.up)
D (715004) events: Signal(network.interface.change)
OVMS# simcom muxtx 3 AT+CPSI?
V (1159254) simcom: mux tx: 41 54 2b 43 50 53 49 3f 0d 0a | AT+CPSI?..
D (1159254) simcom: tx mcmd ch=3 len=10 : AT+CPSI?
V (1159254) simcom: tx: f9 0d ff 15 41 54 2b 43 50 53 49 3f 0d 0a 1d f9 | ....AT+CPSI?....
V (1159384) simcom: rx: f9 0d ff b1 0d 0a 2b 43 50 53 49 3a 20 4c 54 45 | ......+CPSI: LTE
V (1159384) simcom: rx: 2c 4f 6e 6c 69 6e 65 2c 34 35 34 2d 30 30 2c 30 | ,Online,454-00,0
V (1159394) simcom: rx: 78 30 34 35 38 2c 32 37 32 39 37 36 36 39 2c 34 | x0458,27297669,4
V (1159394) simcom: rx: 34 36 2c 45 55 54 52 41 4e 2d 42 41 4e 44 37 2c | 46,EUTRAN-BAND7,
V (1159394) simcom: rx: 33 31 35 30 2c 35 2c 35 2c 2d 31 32 35 2c 2d 39 | 3150,5,5,-125,-9
V (1159394) simcom: rx: 35 33 2c 2d 36 32 39 2c 31 31 0d 0a c2 f9 f9 0d | 53,-629,11……
OVMS# simcom muxtx 3 AT+CNSMOD?
V (1221734) simcom: mux tx: 41 54 2b 43 4e 53 4d 4f 44 3f 0d 0a | AT+CNSMOD?..
D (1221734) simcom: tx mcmd ch=3 len=12 : AT+CNSMOD?
V (1221734) simcom: tx: f9 0d ff 19 41 54 2b 43 4e 53 4d 4f 44 3f 0d 0a | ....AT+CNSMOD?..
V (1221734) simcom: tx: 14 f9 | ..
V (1221744) simcom: rx: f9 0d ff 2d 0d 0a 2b 43 4e 53 4d 4f 44 3a 20 30 | ...-..+CNSMOD: 0
V (1221744) simcom: rx: 2c 38 0d 0a 0d 0a 4f 4b 0d 0a 37 f9 | ,8....OK..7.
It is going to take some work to get this compatible (but doesn’t look too hard). Pricing is still higher than SIM5360, global LTE bands painful to support, and certification would be more hassle, but it seems at least worth trying to get it supported as an option.
Regards, Mark.
> On 22 Jun 2019, at 1:41 PM, Mark Webb-Johnson <mark at openvehicles.com> wrote:
>
>
> FYI: SIMCOM is now recommending SIM7600. That is closer in price to SIM5360 and is supposedly pin-for-pin compatible with SIM7100 and SIM5360. I will get one sample made and try it.
>
> Regards, Mark.
>
>> On 21 Jun 2019, at 7:23 PM, Mark Webb-Johnson <mark at openvehicles.com <mailto:mark at openvehicles.com>> wrote:
>>
>> Craig,
>>
>> Our modem design was loosely based on some suggestions from SIMCOM. Like:
>>
>> https://simcom.ee/documents/SIM7100E/SIM7100_SIM5360_SIM800C%20Compatible%20Design_V1.01.pdf <https://simcom.ee/documents/SIM7100E/SIM7100_SIM5360_SIM800C%20Compatible%20Design_V1.01.pdf>
>>
>> I did get a SIM7100 module a year or two ago, and did some basic testing with it, but cost was just too high at that time. I will ask again to see where we are today. A quick check on aliexpress shows the SIM7100E at US$50 per module, and SIM5360E at US$20, in quantities of 1.
>>
>> My main concern is software support. On paper, the SIM7100 looks compatible, and the AT commands very close. But the same was true of the SIM7000 I tried, and that was a mess - it seems the first firmware didn’t even support the MUX mode we rely on.
>>
>> Given all the passive components required, it is probably easiest to just use a SIM5360 board, unsolder the modem module and replace it, then add / move that one antenna. To get my china contacts to make 3 one off boards is probably about the same price. In general, it is easy to get 1 or 1,000, but quantities in between are the issue.
>>
>> Regards, Mark.
>>
>>> On 21 Jun 2019, at 12:49 AM, Craig Leres <leres at xse.com <mailto:leres at xse.com>> wrote:
>>>
>>> On 2018-06-12 15:26, Mark Webb-Johnson wrote:
>>>> Very easy to make. Our current modem circuit board layout actually supports both the SIM5360 (3G) and SIM7100 (4G) SIMCOM modules; we can simply drop in the appropriate module during production, and build with either 3G or 4G. If there is demand, we can satisfy within weeks
>>> What is my easiest path to getting a small quantity of ovms modem cards with SIM7100A modems? I probably only need 3, should I just buy some SIM5360A ovms boards and swap the simcom modules? And I guess move or add an antenna connector? I've attached a png version of a image from the message I'm replying to. It shows the SIM5360A using ANT1 and ANT3 while the SIM7100E uses ANT1 and ANT2 (and I see now the silkscreen documents this difference).
>>>
>>> Craig
>>> <PastedGraphic-2.png>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190703/bca4feca/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-2.tiff
Type: image/tiff
Size: 74656 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190703/bca4feca/attachment-0001.tiff>
More information about the OvmsDev
mailing list