gps tracker, wmo2, no communication

[amml2000]

hey guys

I am nearly finished with my tracker, finally =) However, i just cant get my tracker to talk to my wmo2 phone. The phone works on baud 9600, i can use it on my pcs com port, all fine. The level converter also seems to work fine as im using it for the debug out to my computer. Here is what I get through the debug line:

Code: Select all

MACHINE STARTED IN DEBUG MODE
•ATE0

OPERATION TIMED OUT
•ATE0

OPERATION TIMED OUT
•ATE0

OPERATION TIMED OUT
•ATE0

OPERATION TIMED OUT
•ATE0

OPERATION TIMED OUT
ATE0

OPERATION TIMED OUT
ATE0

OPERATION TIMED OUT
ATE0

OPERATION TIMED OUT
ATE0

OPERATION TIMED OUT
ATE0

OPERATION TIMED OUT
PHONE SPACE USED IS 19363 OF 7900
POLL INTERVAL IS 600

I also interfaced the serial out to the phone and the "ATE0" command is what came through.

Now i was wondering, why is it sending ATE0? Is that an at command im unaware of? Any other ideas?

So close, cant wait to finish it =D

Cheers

[Mike]

As I understand it:

You are using a WMOD2 module.
You can send AT to the module and get OK, using a PC at 9600 baud.
You have setup the tracker to run at 9600 baud (using the PHONE_TYPE_WMOD2 setting)
You can see the tracker sending at 9600 baud the ATE0 command.
You cannot see the OK reply coming back from the module, if you use the PC to tap the TX out from the module.

Is that correct?

[Mike]

I see the output you posted is from the tracker's debug port.
Turn off debug and use your PC to tap the in and out lines from the GSM module. That will tell you what is really going on. Set the PC to 9600 baud, N, 8, 1, no flow control.

[amml2000]

Hi Mike

Alright, one step further, I found a wrong cable. However, phonepoll still fails. I taped both lines, in and out of gsm module:

line in: ATE0
line out responds with: OK

so everything seems to be working fine, however the gps tracker doesnt seem to get it.

Heres the current Debug:

Code: Select all

MACHINE STARTED IN DEBUG MODE
•ATE0
••
OPERATION FAILED
•ATE0
••
OPERATION FAILED
•ATE0
••
OPERATION FAILED
•ATE0
••
OPERATION FAILED
•ATE0
••
OPERATION FAILED
ATE0
••
OPERATION FAILED
ATE0
••
OPERATION FAILED
ATE0
••
OPERATION FAILED
ATE0
••
OPERATION FAILED
ATE0
••
OPERATION FAILED
PHONE SPACE USED IS 19361 OF 1244
POLL INTERVAL IS 600

So the tracker gets a response now, guess the 2 dots stand for OK, however he cant seem to read it.

[Mike]

If the response shows up as two dots on the PC...
most likely the tracker is not reading it right either.

When you tap the TX (to GSM) line you should see ATE0.
When you tap the RX (to MCU) line you should see OK.

Is the module expecting a DTR, RTS/CTS or other control line to let it talk?
Configure the device for no hardware flow control.

Mike

[amml2000]

When you tap the TX (to GSM) line you should see ATE0.
When you tap the RX (to MCU) line you should see OK.

Yes thats exactly what I see when I tap the lines:

Code: Select all

•ATE0•ATE0•ATE0•ATE0•ATE0ATE0ATE0ATE0ATE0ATE0

Code: Select all

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

Nope, no flow control needed, i can talk to the module just fine over serial baud 9600 without flow controll, the attiny is talking to it fine too as the gsm responds with "OK". however the gps tracker recieved two dots, at least thats what comes out from the serial debug pin. So at least something is recieved by the attiny84. Must be my level converter, thats what I thought, but cant really be if the gsm recieves the correct message and the serial out to my comport is also going through the max3232 and working too. Just dont know where to look...

Thanks

Adi

[amml2000]

still stuck on it... any ideas?

cheers

[Mike]

Maybe the clock timing is out of spec. Can you experiment with the oscillator calibration? Do you have another AVR to test with?
If all else fails, you can ship me the device to be fixed.

[amml2000]

Ok thanks, I'm gona try with a different avr and recheck all the components this weekend

[amml2000]

Rebuilt the tracker from scratch, and got it working, finally =) Now all thats left is connect the GPS, tomorrow hopefully.

As stupid as it may sound, but i think it might have been a problem with the gorund cable. I realized that with the ground missing, the wmo2 module recieves the command correctly, but the attiny wont recieve the reply. Anyhow, rebuilding it was well worth it, ill post a photo of the tracker once im done.

Cheers