Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
kc868-A8S v2 not working with SIM7600E
#1
HI

SIM7600E module plugged in kc868-A8S v2.0 , running KCS 2.2.2. 
  • cannot send message, 
  • cannot receive message (crash/reboot when message is received) 
  • cannot receive call
  • can only place test phone call

also : 
  • the SIM7600E module was successfuly tested with an usb-to-Serial converter and putty. --> the SIM7600 module works fine, can send/receive messages
  • I also tried Tasmota on the kc868, impossible to establish connection to the SIM7600 in serial bridge --> Issue with RX/TX GPIO13/GPIO15 ?
     

Board Model
KC868_A8S
Software Version
v2.2.2
Build Date
Dec 6 2023 22:18:36
Serial Number
08F9E08BCAD4
Board Time
2024-8-27 11:58:45
Time Zone
UTC+2
Lan IP
Lan Netmask
Lan Gateway
Lan MAC
08:F9:E0:8B:CABig Grin7
Wifi STA IP
192.168.0.21
Wifi MAC
08:F9:E0:8B:CABig Grin4


Tests :

Outgoing 
when issuing test;  I got this :

MAKE A CALL ;  OK, my Mobile phone is properly called.

log :   
Code:
I (121694) SIM7600: call +32xxxxxxxxx

SEND A MESSAGE,  ERROR (no message received on mobile phone)

Log :

Code:
I (689066) SIM7600: [1/1] 0011000B912374940999F500007A2654747A0E4ACF416110BD3CA783DAE5F93C7C2E83CCF2771BB41CE26CB84810377501
 

INCOMING

CALL : nothoing happens, no log
Reply
#2
receive   MESSAGE kc868 reboots

log  :

Code:
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x400014fd  PS      : 0x00060230  A0      : 0x801629e0  A1      : 0x3ffe52d0 
A2      : 0x00000000  A3      : 0xfffffffc  A4      : 0x000000ff  A5      : 0x0000ff00 
A6      : 0x00ff0000  A7      : 0xff000000  A8      : 0x00000000  A9      : 0x3ffe5290 
A10    : 0x00000000  A11    : 0x3f4e9a1c  A12    : 0x3ffe5514  A13    : 0x3ffaeb58 
A14    : 0x00000000  A15    : 0x00000001  SAR    : 0x00000004  EXCCAUSE: 0x0000001c 
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xffffffff 


Backtrace: 0x400014fa:0x3ffe52d0 0x401629dd:0x3ffe52e0 0x4016404d:0x3ffe55f0 0x40176f51:0x3ffe5620 0x4008dd29:0x3ffe5650 0x400e22ca:0x3ffe56a0 0x400e23fc:0x3ffe57f0 0x400e241b:0x3ffe5810 0x400e294f:0x3ffe5a30



ELF file SHA256: 2b1db7d975ea26ea

Rebooting...
I (13) boot: ESP-IDF v4.4.5-dirty 2nd stage bootloader
I (13) boot: compile time 21:27:12
I (13) boot: chip revision: v3.1
I (15) boot.esp32: SPI Speed      : 40MHz
I (20) boot.esp32: SPI Mode      : DIO
I (24) boot.esp32: SPI Flash Size : 4MB
I (29) boot: Enabling RNG early entropy source...
I (34) boot: Partition Table:
I (38) boot: ## Label            Usage          Type ST Offset  Length
I (45) boot:  0 nvs              WiFi data        01 02 00009000 00026000
I (53) boot:  1 phy_init        RF data          01 01 0003f000 00001000
I (60) boot:  2 factory          factory app      00 00 00040000 003b0000
I (68) boot: End of partition table
I (72) esp_image: segment 0: paddr=00040020 vaddr=3f400020 size=104af8h (1067768) map
I (467) esp_image: segment 1: paddr=00144b20 vaddr=3ffb0000 size=0316ch ( 12652) load
I (472) esp_image: segment 2: paddr=00147c94 vaddr=40080000 size=08384h ( 33668) load
I (486) esp_image: segment 3: paddr=00150020 vaddr=400d0020 size=a8454h (689236) map
I (736) esp_image: segment 4: paddr=001f847c vaddr=40088384 size=06ec0h ( 28352) load
I (756) boot: Loaded app from partition at offset 0x40000
I (756) boot: Disabling RNG early entropy source...
I (767) cpu_start: Pro cpu up.
I (768) cpu_start: Starting app cpu, entry point is 0x40081254
I (762) cpu_start: App cpu up.
I (784) cpu_start: Pro cpu start user code
I (784) cpu_start: cpu freq: 240000000
I (784) cpu_start: Application information:
I (788) cpu_start: Project name:    kc868-a-serial
I (794) cpu_start: App version:      v1.0.0-167-gf459a12-dirty
I (800) cpu_start: Compile time:    Dec  6 2023 22:16:06
I (807) cpu_start: ELF file SHA256:  2b1db7d975ea26ea...
I (813) cpu_start: ESP-IDF:          v4.4.5-dirty
I (818) cpu_start: Min chip rev:    v0.0
I (823) cpu_start: Max chip rev:    v3.99
I (827) cpu_start: Chip rev:        v3.1
I (832) heap_init: Initializing. RAM available for dynamic allocation:
I (840) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (845) heap_init: At 3FFC76A0 len 00018960 (98 KiB): DRAM
I (852) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (858) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (864) heap_init: At 4008F244 len 00010DBC (67 KiB): IRAM
I (872) spi_flash: detected chip: generic
I (875) spi_flash: flash io: dio
I (880) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (895) main: [APP] Startup..
I (898) main: [APP] Free memory: 214320 bytes
I (903) main: [APP] IDF version: v4.4.5-dirty
I (1175) NVS: init nvs finish.
I (1179) system_api: Base MAC address is not set
I (1179) system_api: read default base MAC address from EFUSE
I (1201) esp_eth.netif.netif_glue: 08:f9:e0:8b:ca:d7
I (1201) esp_eth.netif.netif_glue: ethernet attached to netif
I (5202) eth: Ethernet init
I (5202) wifi station: ESP_WIFI_INIT
I (5202) eth: Ethernet Started
I (5205) wifi:wifi driver task: 3ffd4b18, prio:23, stack:6656, core=0
I (5226) wifi:wifi firmware version: 0f80fa0
I (5227) wifi:wifi certification version: v7.0
I (5227) wifi:config NVS flash: enabled
I (5227) wifi:config nano formating: disabled
I (5232) wifi:Init data frame dynamic rx buffer num: 32
I (5236) wifi:Init management frame dynamic rx buffer num: 32
I (5242) wifi:Init management short buffer num: 32
I (5246) wifi:Init dynamic tx buffer num: 32
I (5250) wifi:Init static rx buffer size: 1600
I (5254) wifi:Init static rx buffer num: 10
I (5258) wifi:Init dynamic rx buffer num: 32
I (5263) wifi_init: rx ba win: 6
I (5266) wifi_init: tcpip mbox: 32
I (5270) wifi_init: udp mbox: 6
I (5274) wifi_init: tcp mbox: 6
I (5278) wifi_init: tcp tx win: 5744
I (5282) wifi_init: tcp rx win: 5744
I (5286) wifi_init: tcp mss: 1440
I (5306) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
I (5392) wifi:mode : sta (08:f9:e0:8b:ca:d4)
I (5393) wifi:enable tsf
I (5396) web_server: Starting HTTP Server on port: '80'
I (5404) wifi:new:<6,0>, old:<1,0>, ap:<255,255>, sta:<6,0>, prof:1
I (5400) gpio: GPIO[0]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 1| Intr:0
I (5911) wifi:state: init -> auth (b0)
I (5914) gpio: GPIO[2]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0
I (5917) ntp: tz:UTC-2
I (5919) wifi:I (5918) UDP SERVER: Socket created
state: auth -> init (8a0)
I (5925) UDP SERVER: Socket bound, port 4001
I (5928) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
I (5920) RF: RCSwitch->nReceiverInterrupt=16 gpio_pin_sel=65536
I (5945) gpio: GPIO[16]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:3
I (5955) RF: Start RF receiver
I (5955) uart: queue free spaces: 20
I (5962) gprs: gprs init success.
I (5969) pcf857x: pcf857x init.
eFuse Two Point: NOT supported
eFuse Vref: Supported
I (5975) analog: ---->adc1 thresholdd : 0
I (5979) analog: ---->adc2 thresholdd : 0
I (5984) analog: ---->adc3 thresholdd : 0
I (5989) analog: ---->adc4 thresholdd : 0
I (5993) analog: adc 0 monitor items : 0
I (5998) analog: adc 1 monitor items : 0
I (6003) analog: adc 2 monitor items : 0
I (6007) analog: adc 3 monitor items : 0
I (6012) gpio: GPIO[14]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 0| Pulldown: 0| Intr:0
I (8372) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
I (8373) wifi:state: init -> auth (b0)
I (8379) wifi:state: auth -> assoc (0)
I (8386) wifi:state: assoc -> run (10)
I (8418) wifi:connected with living, aid = 3, channel 6, BW20, bssid = 00:31:92:81:48:e6
I (8419) wifi:security: WPA2-PSK, phy: bgn, rssi: -72
I (8425) wifi:pm start, type: 1

I (8434) wifi:<ba-add>idx:0 (ifx:0, 00:31:92:81:48:e6), tid:0, ssn:0, winSize:64
I (8472) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (9430) esp_netif_handlers: sta ip: 192.168.0.21, mask: 255.255.255.0, gw: 192.168.0.1
I (9432) wifi station: got ip : 192.168.0.21
I (9717) ifttt: start ifttt task 
Reply
#3
upload your GSM setting screen in KCS.
Reply
#4
(08-27-2024, 10:04 PM)admin Wrote: upload your GSM setting screen in KCS.

please find here below the screenshots.

+324xxxxxxxxx is my mobile phone number (I hide the digits for privacy reasons ;-) 

so I can do a test call to my mobile, but anything else fails (outgoing test SMS, incoming control SMS, outgoing notification SMS)


Attached Files Image(s)
           
Reply
#5
do you have set the SMS service number in your mobile phone. just when the SIM card have normal SMS function when using in your mobile phone?
Reply
#6
(08-30-2024, 01:28 PM)admin Wrote: do you have set the SMS service number in your mobile phone. just when the SIM card have normal SMS function when using in your mobile phone?

yes, i tried the exact same hardware combination ( SIM7600E module plugged in kc868-A8S v2.0 ), but  with Tasmota32 instead of  KCS 2.2.2. , and I can manage to send and receive SMS.

so the problem is with  KCS 2.2.2
Reply
#7
ok, next week we will test with KC868-A8S v2 board. if have bug, we will feedback to our software team.
Reply
#8
we have tested with new KCS firmware V2.2.4 here is download link: 
https://www.kincony.com/forum/showthread.php?tid=6600

   
   
   

important: make sure when you enabled GSM, you MUST need click "SAVE" button for reboot. Then you can use TEST with SMS or CALL.
   
Reply
#9
The problem is most likely related to the power supply of the SIM7600E module.
As it is written in the datasheet for this module, it requires 5-10V DC.
However kc868-A8S v2.0 only supplies 4V DC to pin V.
SIM7600E uses a 1084 (or analog) linear regulator in the power circuit with some voltage dropout. As a result, the SIMCOM chip does not have enough power.
This can lead to cyclic reboots and other bad things.
Colleagues from KinCony, can you explain the situation?
Reply
#10
A8Sv2  resistance R31 now is 2.26K, you can replace with 3K. Then it will output 5v for GSM module.
Yes, use 5V will be better.
   
Reply


Forum Jump:


Users browsing this thread:
1 Guest(s)