This message was deleted by its author
i guess there're many ways to do this, but the only "universal" way is to simulate a com port via bluetooth that accepts NMEA commands.
Related
Hi There
Does anyone know if there is such a thing as a mini-USB to Serial (or parallel) device on the market? Something that would provide PPCs like the K-JAM/WIZARD with a serial/parallel port.
I know they are available for desktop PCs, but what about hand-helds?
Ken
not without USB host. However you can use bluetooth to serial. I got ones of these:-
http://www.merlinbluetooth.co.uk/merlinbluetooth/promi-bluetooth-module-p-33.html
Bluetooth-serial
Thanks for that; it looks great, so I will (I imagine) need to get some software to read/write to that device.
At the device end I should be able to configure some Data Acquisition circuitry.
My problem is that I don't get access to the Vario/K-JAM until Christmas Day - it's a present from my wife - so I have no idea about writing stuff to access the bluetooth system Does it present itself as some sort of I/O?
I've just bought the NSBASIC/CE, so I was hoping to be able to write the necessary stuff with that.
The K-JAM looks a great bit of kit, but I'm never satisfied until I can get two-way interaction with the outside world in both Digital and analogue.
Thanks again,
Ken
It appears as a com port "COM5" on mine. You can open it just like normal using CreateFile / WriteFile etc
Many people seem to be having problems using a Bluetooth GPS with nav software on a Pocket PC. I have had a few issues and trawled the net looking for answers and there seems to be a lack of reference information on this. This forum is probably the best hope of getting a definitive reference document compiled.
My XDA Pro (Universal) did not have the GPS Settings control panel installed in Settings/Connections until I edited the registry to make it visible. Why was it not enabled originally? Does it not work?
What does GPS Settings actually do? (My premise is that it virtualises the GPS Com port is that right?)
I have set up my BT GPS to be on COM8 by adding a new Outgoing Port. Using GPS Settings-
in the Programs Tab set "Program Port:" to be COM1:
in the Hardware tab set "Hardware portP" to be COM8: (why no 38400 baud rate setting??)
Is it safe to assume that any program that wants to use the GPS should connect to the virtual port COM1: or the actual port COM8:?
From a software perspective when trying to configure a program to connect to a GPS invariably the software will offer a list of COM ports to use e.g......
VisualGPSce (a free GPS monitoring tool from www.visualgps.net) offers a set of COM ports and SER01-SER32. If I connect this to SER08: it works fine but when I look at the settings again it has changed them to COM1: - Drivers\BuiltIn\Serial_dbg. (I assume this is the affect of using the GPS Settings above). Interestingly if I choose an invalid port then choose COM1: it fails to connect until I select SER08: again!!
Fugawi offers COM1: - COM8: but only works when I select COM8: Is this 'not playing the game' because it is talking to the real port and not the 'virtual one'?
A friend has Pocket Nav (Memory Map) which only offers a set of COM ports COM1,2,3,6,7,9 (all of which are named with the kind of device except 7) and none of them work. Is this software only offering COM ports that it believes to be active? It also seems to be not playing the virtual port game (If my premise above is correct). Why doesn't it see the GPS on COM8:?
Sorry for the long posts - lots of questions, a few suppositions and not many answers from me. I just hope the gurus who frequent this forum can provide some good technical answers which will benefit many frustrated (both by things not working but also through lack of techincal reference documentation) people.
Thanks
Clive
hi i'm experiencing the same problem, did you solve it ?
I can't find a useful COM port to connect to my java application using a Qtek 9000 with WM 5 and Creme JVM.
thank you.
I will surely spend a lot of time on this question in my forthcoming Bluetooth Bible (still don't know when to publish).
are you serious ..
or it was sarcastic ?
Yes, maybe i was not so clear writing my question, but i didn't want to write the same words clive_j wrote ...
I'm running a java application on a Qtek 9000 running Windows Mobile 5.1.1700 (build 14354.0.1.1) and using a Java Virtual Machine "Creme 4.12 for PocketPC".
While, via bluetooth manager, I'm able to connect my BTGPS (i.e. bluetooth GPS) only on COM0, or COM4, or COM8, my application can open only COM1, or COM2, or COM3, or COM6, or COM7, or COM9.
I configured GPS Settings on WM 5 just like clive_j did, and still i can't receive any data from the GPS, while VisualGPS can connect and receive data from SER08.
Did you have any idea ?
I found how to solve the problem.
don't know if menneisyys is interested.
Here is what I found from the source code, anymore?
*#06# Display IMEI
*#*#8351#*#* Voice Dialer Logging Enabled
*#*#8350#*#* Voice Dialer Logging Disabled
*#*#4636#*#* Phone Setting
*#*#7262626#*#* FieldTest
android.provider.Telephony.SECRETE_CODE
Already know that 5 Secret Code but could not find any thing which can out it into Diagnostic Mode which was there in Windows Mobile.
Please Upload the Source code also so every body also start searching for something very usefull.
hetaldp said:
android.provider.Telephony.SECRETE_CODE
Already know that 5 Secret Code but could not find any thing which can out it into Diagnostic Mode which was there in Windows Mobile.
Please Upload the Source code also so every body also start searching for something very usefull.
Click to expand...
Click to collapse
The source code is online and available VIA git
And if you are trying to use the field test use anycut to make a shortcut on the desktop and it has a menu item to output diagnostics.
Of course if you have DDMS or Eclipse you can output diagnostics as well.. I believe they have a linux boot image on open handset alliance
those aren't that secret, and aren't anything special.
Any app can register a "secret code" and they are specified in the manifest.xml file.
most of the time those numbers are things like "INFO" and are a lot easier to remember if you think of them that way instead of the digits.
We talking abiut the Diagnostic Mode of Phone Radio so we can plug the Phone into USB and get QxDM (Qualcomm Extendible Diagnostic Mode) Software and look into Radio NVItem from 0 to 4000. DDMS is useless for that kinda Stuff. Radio Software is build using Some Different Core other then Linux, i have seen commnet of CMonex He said it the same as General other Radio, Remeber Radio and Android is connected with RIL (Radio Interface Layer) using Internally Exposed Serials Ports.
did somebody say exposed serial port?
Over my head a bit, but sounds cool, internally exposed serial ports sound useful, id assume you,d get i/o from both sides radio/droid. Back on the WIZ you could find a radio that works with the rom ver. and carrier to get best clarity, call handling, stability and battery life. This is cool reminds me of the early days of palm os rom hacking/cooking (we didn't call it that back then)
I'm glad I got it and I'm glad its an htc, so the homies at xda-dev will have this bad boy totally tricked out and custom...I love this plave, in a non homo way
Will we all be adding db9 ports on pur g1s
Bhang
no, i do not believe we will ever see a db9 on the G1. First of all, that connector went out of style in the late 90's and second, its rather huge (want do drill a hole in your screen to make room for it??). I would however like to see usb host, but someone commented that it is probably not enabled in the kernel and if it is, there are no drivers for it (hint hint driver g writers). cmonex (is a girl by the way) has been looking into methods to get root on RC30 and many other things so we hope to see some fun new hacks from that.
nice shrring,this is a good source where someone can learn something about their mobile secret functions,meantime i would like to share something which i found last week this is a site where it has network unlock code for all mobiles find further
After all the messing around with the serial port kernels (disadvantage: needs rooting, only works on some fones) and more recently the serial out using the headphone jacks (disadvantage: output only, and kinda slow at 24000bps max) I set out to do an ADB interface for a microcontroller, so as to allow for sensor and motor control from the phone from there. So far so good. If you want to see my results so far (and get the yummy software and schematics -- I sell kits, but it's all free-as-in-speech) check the instructions out.
http://robots-everywhere.com/re_wiki/index.php?title=PropBridge (only source for now)
http://robots-everywhere.com/re_wiki/index.php?title=Serial_on_Android_using_the_audio_port (also available on market, search "serial out" and it'll show up)
Heh, guess nobody cares. Anyway, the relevant apps are now on market, if anyone wants the source just message me.
Last bump...
It's on hackaday http://hackaday.com/2011/03/29/propeller-android-communications-using-debug-mode/ also a number of cool android hacks, usually hardware related.
(I would have posted this in the development forums but apparently I don't yet have enough "karma" or something {grin})
I'm on a project to use Android tablets to exchange data via USB with an embedded microcontroller environment. At present I'm using a Nexus 7 (because it supports USB Accessory mode, so it can be powered by the other end) and an Arduino Due (because it has two USB interfaces). I've read countless articles and scoured everything I can find on the topic of programming for USB, but still have some fundamental questions.
The biggest one concerns how the host and device interfaces "identify" each other. Seems like each end needs to expose a USB interface with VID/PID values that the other end knows about and looks for during initialization. This implies that the code on each end would need to control the PID and VID values, as well as other USB descriptor values. Yet none of the code examples I've found ever discuss this.
Example: I've found that the Nexus 7 exposes one PID value (0x4E42) when its USB port is configured in "media device (MTP)" mode, and a different PID value (0x4E44) when its USB port is configured in "camera (PTP)" mode. The protocols for interacting with these two configurations is different, and the code on the other end of the wire needs to know how to handle that. I haven't checked yet but I suspect the values in the usb_interface and usb_interface_descriptor structures also change along with the PID value, since usb.org defines a whole bunch of standardized values for various device types. A connecting device would retrieve these values, potentially from multiple exposed logical interfaces on the same physical USB port, and select a compatible one.
Since I'm writing the code on both ends of the wire, doesn't my code need to somehow convey these values into the USB interface hardware? How is that done, for example, under Android? Do the code examples just omit this because everyone but me knows how to do it?
If I just "ignore" this question, then when the Arduino (acting as USB Host) polls the Nexus 7 it will have to select from whatever interfaces are offered. So... whose code is in charge of those interfaces? How does my code tell the Android OS which of these "default" interfaces it will be handling? My suspicion is that, if a USB interface is being advertised, there is *already* code behind it. That brings me full circle to the question of "How does my code inform Android that it wants to use certain VID/PID values?"
I hope I've explained this clearly. It's a pretty detailed question, so if it's unclear I can try to ask it differently. Thanks in advance for any guidance, tips, RTFM's, etc.!
For interacting arduino with android device, it can be written under eclipse, you can learned it from "Beginning Android ADK with Arduino" which can be downloaded from torrent market. VID/PID mostly used to allow your device to be recognised to your computer.
koklimabc said:
For interacting arduino with android device, it can be written under eclipse, you can learned it from "Beginning Android ADK with Arduino" which can be downloaded from torrent market.
Click to expand...
Click to collapse
Thanks, I'll look for that reference!
VID/PID mostly used to allow your device to be recognised to your computer.
Click to expand...
Click to collapse
Yes, but those parameters (along with a couple of others) are used to 1) confirm that the two devices recognize each other, and 2) in some cases to launch the proper code to handle that interface/protocol. So you must have control over them, and must initialize the USB system with the proper values in some manner. I presumed it would be in the Android API but I can't find any reference to setting the low-level values for USB connections.
Thanks again for the response! Anyone with additional data? It would be greatly appreciated!