Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

AT Command instance has been released | Telit Cinterion IoT Developer Community

January 25, 2018 - 11:29pm, 4729 views

Hello I would appreciate any help in trying to locate the cause of the following issue:

I updated the JRC firmware to JRC-56.54 on the EHS6T modem.

However I am having issues with running previously working code in debug mode on Netbeans 7.2 

The software uses embedded AT commands within Java, which previously behaved as expected.

This error is being generated after several AT commands have been issued, without error.

Commenting out sending the AT command prior to the error just shifts the problem later on indicating its probably not the 'at commands' themselves, just keeps on generating the error for subsequent 'at commands'.

I tried running the utility to try and go back to a previous version of JRC firmware but it won't let me.

Is there anything I can check to see what is happening.

Messages generated: 

Error: ATCommand instance has been released

java.lang.IllegalStateException: ATCommand instance has been released

 - com.cinterion.io.ATCommand.send(ATCommand.java:847)

 - com.cinterion.io.ATCommand.send(ATCommand.java:772)

 - ftp_gsm.Ftp_Gsm.waitUntilRegisteredOnNetwork(Ftp_Gsm.java:7625)

 - ftp_gsm.Ftp_Gsm.startApp(Ftp_Gsm.java:948)

                at javax.microedition.midlet.MIDletTunnelImpl.callStartApp(), bci=1

                at com.sun.midp.midlet.MIDletPeer.startApp(), bci=5

                at com.sun.midp.midlet.MIDletStateHandler$StartAppTimerTask.run(), bci=12

                at java.util.TimerThread.mainLoop(), bci=244

                at java.util.TimerThread.run(Timer.java:505)

Error: ATCommand instance has been released

java.lang.IllegalStateException: ATCommand instance has been released

I don't think it is a Netbeans issue, since I am no longer getting responses from the modem when running my MIDlet from the firmware. Inspection via Hyperterminal with at^sjam=5 indicates my program it is being set to Autorun along with the JRC.

The previous JRC firmware installed was JRC-56.42

Tried increasing the 'at command' response period, but made no difference.

Bobg