TC65 Module Exchange Suite (MES) problems
October 3, 2009 — Florent ClairambaultWhen you want to locally deploy software on your TC65 chip, you need the Module Exchange Suite (MES). If it doesn’t work, it won’t tell you why, finding out why can be quite tricky.
If you want to find out why the communication with your TC65 failed, the best way is to use the portmon tool and see what is exchanged between the MESServer.exe and the chip.
I collected 3 portmon captures that could help you diagnose your MES communication problems :
- Here is a successful MES files listing at 19200 bps. You can see that it sends the “AT+CGMM” at different bit rates unless it gets a good response. Then it sets some serial communication options. And then it sends the “AT^SQWE=100″ commands which fails and then establish a successful link using the “AT^SQWE=3″ command.
- Here a failed MES file listing. Here, after the “”AT^SQWE=3″” is sent, MES sends a 26 bytes message and receives a 41 bytes message from the chip. Then it should request the file listing. But here, MES doesn’t request anything. Maybe MES doesn’t work well, or maybe the reply from the chip doesn’t satisfy his requirements.
Anyway, after that it should send a 27 bytes message containing : “x-obex/folder-listing”, and it should get the file listing. But it doesn’t. It reads on the serial port like if it was still waiting for something. And finally, it closes the connection (with “+++”). - Here a totally failed communication. Here it’s because the modem gets stuck on waiting for the modem hardware flow control (“IOCTL_SERIAL_GET_MODEMSTATUS”) when it’s only a 3 wires (TX,RX,GND) communication. So MES never reads or writes anything.
If you have the same kind of problem, you can send me your portmon capture file.
October 6, 2009 at 5:06 am
Hello,
Thank you for sharing your experiences with TC65 and similar modules.
I am trying to develop J2ME applications under Linux (Ubuntu 9.04), and Im having difficulties sending files to it. I need the Wireless Toolkit, but it is not available for linux. I’m trying to run it under wine, but I just cant map the COM1 to the ttyACM0 successfully.
I tried using the obexftp, but I cant connect, I think I need to edit the sources to fit my needs.
Compiling is ok, first tried with eclipse, with no success, and with NetBeans 6.7.1 I’ve got it working, using the windows SDK, and vitalization with wine the windows binaries files.
I just need to make it connect, or by Wine, or by obexftp.
Then I can make a shell script to automate and auto build and send to module.
Do you have some suggestions to work around this?
Thanks.
October 8, 2009 at 1:25 am
I’m sorry but I really can’t help you with that. I don’t know anything about obex transfers and I’ve never tried to send files to the chip on Linux. I guess obexftp is the best app you could start from, but I have no idea how OBEX works. You should talk to the guys who actually do this kind of stuff (OBEX with Linux).
October 8, 2009 at 10:26 pm
Hi,
I wrote java tool for Linux – for MES replacing. It is no graphics, only line commands tool.
I am developing M2M apps. on Linux since 2006.
Send me your emails on oj@alarex.cz, if you want to linux tool.
Best regards Oja
October 8, 2009 at 10:47 pm
Well, that’s good news for Linux users.
November 7, 2009 at 1:56 pm
I’m experiencing some problems with MES and a TC65i.
I can transfer files of some kbytes (1, 2 kb) but i can’t transfer bigger files e.g. 30kbytes or more.
Do you know something about such issue?
Thank you
Roberto
November 8, 2009 at 6:39 pm
I have never noticed anything like this. For me, it works or doesn’t (due to the absence of support of the DTR and DSR pins).
But I have never tested it on a TC65i.
Have you tried to reduce the bandwidth ? (you can try “AT+IPR=19200″)