Yukun, I stand corrected. You are correct. In the instance you describe above, the Nomad is emulating the NMEA sentences from COM2 to COM3 in Windows Mobile. I completely forgot about this WM GPS Emulation feature.
I'm just wondering since I don't have much experience with these devices. When I first got the NOMAD and before I installed GPScorrect, the GPS on the unit was not working. I was trying to figure it out and bumped into the GPS settings under windows mobile, where the default settings for hardware port was COM2, and program port was COM3. The "allows Windows to automatically assign port" options was unchecked. I went ahead and checked it, opened up ArcPad and in its GPS Preference menu, set the port to COM3, and voila! GPS worked. That's why when I was troubleshooting error code 5 and saw everyone use COM3 as their GPS port for ArcPad I thought I used the correct setting.Thanks for your response Alex.
I cannot confirm that I've ever seen a Nomad connecting to COM3 for GPS data with default settings. However, I can confirm that the COM2 is the way to go.
The GPS Port on the Nomad is COM2. COM3 will always get you nowhere on a Nomad. The assignment to COM3 in the above posts that you read are specific to a GeoExplorer. Roll with the following settings on the Nomad and you should be fine...;)Protocol: Trimble GPScorrectPort: COM2 Baud: 9600
I have a NOMAD 900 G series and has been playing with ArcPad 8.0 for a while and haven't had any issue with the GPS receiver. Today after I installed and activated GPScorrect 3.10 on it, neither ArcPad nor GPScorrect can connect to the GPS receiver. If I use what seem to be the standard settings in ArcPad's GPS preference:Protocol: Trimble GPScorrectPort: COM3 (this doesn't say Trimble TIPS or whatever, just COM3)Baud: 9600Then whenever I try activating GPS I got error code 5.So frustrated I decided to uninstall GPScorrect and see what happens. The uninstallation was smooth, however, once I fired up ArcPad, within a minute everything froze. Even holding down the power button won't do anything. Had to take the battery out and let tbe power drain to get the unit working again.After that I reinstalled GPScorrect. COM3 was still no go. But if I set the port to COM2 (the hardware port), both ArcPad and GPScorrect seem to be working fine with the GPS receiver. I was able to collect some data, and do post-processing. However, since wherever I look, everyone is setting the port to COM3, I have to wonder, is it completely wrong to use COM2, though things "seem" to be working? Thanks for any insight you may provide.
I do have a question on the priority script though. The script allows you to change the priority for two things; the draw priority and the GPS priority. Could you leave the draw priority at above normal (to keep the drawing speed relatively high) and simply set the to the GPS to the "highest" priority?
Sounds like you've tried some of these, but go through the list and check. a. Install the Priority Scripti. The Priority script that ships with ArcPad allows us to modify the priority of the thread that�??s doing the redraw. The script is installed in: Computer Drive with ArcPad Installation C:\Program Files\ArcPad 8.0\Developer\Samples\Applets. ii. If you copy the script to \Program Files\ArcPad\Applets on the geo and restart arcpad, you�??ll see a little extra item in the tool bar �?? looks like the ArcPad logo. Activate this tool bar and click the one icon that appears to run the script.iii. Then change the drawing priority from �??abovenormal�?? (the default) to �??normal�??, hit OK and quit ArcPad. iv. Restart Arcpad and the new setting will take affect. The change allows the GPS to keep working during the redraw.Eric B
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.