Few days ago I bought a new MTS Wi-Fi Dongle, today while using it, I did a port scan on 192.168.1.1 using my Android device and surprisingly port 23(telnet) was open. After typing telnet 192.168.1.1, below was the result on window of terminal,
VENKY V2.0 Welcome You!!!
VENKY>
and after sometime, it started showing following message,
^HRSSILVL : 60
^HRSSILVL : 80
^HRSSILVL : 60
and so on, I tried few Linux commands(I know it wont work but still) but none of them worked, one I have figured out is version command, which shows version, Does anyone know what VENKY is or has encountered something same....?
I think this is a command line interface for your Huawei usb modem.
You may try running an AT command like ^TIME, &V or ^OTAACTED and so on.
The HRSSILVL^:<rssi> reports the received signal strength.
Here is a manual page that might be useful: Huawei MC509 User's Manual Page 65
Related
I am building IOT device using a LTE modem form Quectel, the BG95, together with NXP imx6, running Linux. The sim card I am using has the technology of eMTC.
Normally the device is working fine, the issue I am having now, is that the device lost LTE communication randomly (typically after 3-6 days uptime).
My setup
I have disabled echo mode in the BG95 at my init procedure.
I have a periodical call to send AT command "AT+CREG?" toward BG95, and read the response.
What I am seeing from the debugging is following:
My periodical at command "AT+CREG" toward BG95 is not responding.
Linux kernel reports ttyUSB towards BG95 is disconnected.
3-4 seconds, the kernel reports ttyUSB toward BG95 is connected again.
My periodical AT command "AT+CREG" toward BG95 is returning ERROR.
I see from the serial reading from the BG95 has "APP RDY".
I see from the serial reading from the BG95 has echo mode enabled.
Form what I am seeing, I am assuming that the BG95 is somehow "rebooted".
Is there any reason why the BG95 will reboot itself? Or how to confirm this?
I checked the datasheet of BG95, but I cannot find a AT command or other way to check the boot reason.
Do you have other suggestion on how to debug this further? Or similar experience with BG95?
Thanks
I have firmware installed on an Arduino DUE from a different mac, it is designed to interface with a Matlab-based application. It has been tested and known to work. I am attempting to modify the firmware from the mac in my office, but I ran into a snag after installing the Arduino IDE.
First, I cannot get the Arduino Serial Monitor to interact with the DUE. I have tried multiple times, it worked once but I have not managed to make it work since. No errors are reported.
Second, I cannot get the screen terminal command to interact with the DUE either. No errors are reported.
Third, if I simply use text pipes in the terminal (e.g., echo 'status' > /dev/cu.usbmodem1421 or head -20 /dev/cu.usbmodem1421 &) I get appropriate responses from the DUE.
Fourth, the Matlab application can interact with the DUE just as designed.
Note that this is the native USB port in the DUE, no serial adapters (with their driver weirdnesses) are involved. I have not tried to download new code to the DUE as the firmware works as it is as long as we use macs (it is just that I need to modify it so that it can work with the much-slower ports in a Windows PC).
I need to be able to debug the code I am modifying, and for that I need to be able to interact via a terminal, any terminal. Any ideas of where to look?
UPDATE: I noticed that the code was not waiting for USB to be ready. So I added
while(!WiredSerial){
digitalWrite(PIN_LED, HIGH);
delay(125);
digitalWrite(PIN_LED, LOW);
delay(125);
}
After this change the DUE waits for the terminal to be opened and the terminals display the initialization text without a hitch. After that the behavior is the same as reported before.
Never mind.
I was certain that I had already checked this before posting. As a matter of fact, I am sure that it is the first thing I checked, something else must have changed in the interim.
The code was expecting a newline character before it sent anything back while the terminals were just sending a carriage return.
I searched a lot of things about the Flash sms class 0, and I'm really interested in the AT+command to send flash sms to any number.
But I read that this command can be used only on specefic devices, like some versions of Nokia.
Also, some people did this on a basic Terminal on OS X with a 3G+ key.
Please can someone explain me which phone do I need to execute the AT commands, or what 3G+ key do I need ?
I didn't find a real tutorial on how to do that...
For example if I buy an old Nokia phone, is it OK for sending the AT commands ?
Thank you.
https://adywicaksono.wordpress.com/2008/02/08/how-to-send-flash-sms/
You don't have to get a Nokia phone..
I use a gsm modem - https://www.amazon.com/Generic-Wavecom-Q2303A-Interface-Commands/dp/B00BD0V57I
You can connect to it via sample telnet and run any (supported) AT command. Way simpler...
And I have no idea what do you mean by key 3G+ :/
I used “plugin.shell(‘logcat’)” directly in the JavaScript console(chrome://inspect#apps) to get adb log informations before.
But recently, after several times of upgrade, whenever I tap the command, it always prompts "Promise {[[PromiseStatus]]:”resolved”, [[PromiseValue]]:Object}” and no log is displayed.
I have tried to get adb log from ui_log in chrome://system, but failed, the log I write in the code is not displayed either.
I found this problem quite a few days ago and thought it would be fixed be Google.
However, it is still there util now.
My test device information
Chrome OS : version 45.0.2454.15 dev
ARC : 45.5021.433.5
My question is : How can I get adb log now? Or should I use some other method to get adb log?
This is a known regression issue and under investigation now.
Note : logcat is still available in Chrome 44 on stable channel.
Today I am trying to send out SMS with my Prolink PHS300 USB modem by sending AT Commands to it from my machine running OS X Lion.
I have adjusted the settings for my modem such as checking "Connect using a terminal window..." etc. Right now I am trying to send AT Commands to it.
In my terminal window i typed screen /dev/tty.USBModemATPort_ but it tells me messages such as Could not open line '/dev/tty.USBModemATPort_' for R/W: Resource is busy and then Sorry, could not find a PTY.
in a desperate attempt i have even tried chmod 777 the "...ATPort_" but to no avail.
does anyone know if i may have done anything wrong here? thanks so much. :)
found my problem - it was a stupid one. it was because the 3G connectivity app that connects to the internet was opened and hence screen said that the resource was busy.
hope this saves someone some time in future.