Hi,
Recently I purchased a bunch of MC8795V modules that we use in several of our products. These were purchased overseas and I am having trouble getting them registering with the Telstra network.
So far I have managed to connect using USB and can send and receive SMS using the Generic Watcher software ok. I can then do the same using the virtual AT com port and terminal program ok. But when I change to use the serial port (AT!MAPUART = 1) and then reconnect to the module using serial coms port, I can access all the regs ok and set text mode etc but cannot get the modules to register on the network. I suspect that when connecting via USB, the installed watcher driver must be somehow changing a connection mode to make it connect ok. I hope this is just a matter of making some changes to some regs. I noted the sysconfig setting in old modules that do work here was set to 2,0,1,2 and the new modules 2,2,1,2. I tried to change the sysconfig to same (AT^sysconfig=2,0,1,2) but module reports error in response to this.
I have been “playing” a bit more and found if I simply set AT+CFUN =1 it works ok.
There must be a parameter that is causing the module to start up without radio turned on or something. Now my code needs to set CFUN=1 every time it boots.
Until I set cfun=1 I get 0,0 reply to creg?, the second I set cfun to 1 I get 0,1 response to creg? (registered ok with network)
This function appears to not be saved with AT&w0. Would someone know which config setting I need to change to make sure the radio is active each time the module powers up? Or whether there is some other parameter setting that could cause this behavior? I was able to set sysconfig after cfun was changed to 1 (whereas I got error previously). Also noticed these modules send “+PACSP1” at boot, I have not seen this before. Cpin returns ready.
Yes, watcher will communicate with module and that can cause change in behavior.
The 2nd parameter in ^sysconfig just change the network mode order, auto and WCDMA->GSM. So, should not matter in your case.
There are serverals options that can cause module to start with RF off, for example “STARTLPM” in !CUSTOM.
Can you please check AT!CUSTOM? and AT!PCINFO? from UART after module just booted up?
By the way, it is best to use the carrier approved firmware and configuration, please check with the distributor to get such info and upgrade the modules if possible.
And again, it is best to use the carrier approved firmware and configuration, please check with the distributor to get such info and upgrade the modules if possible.