|
|
| I closed out a jon and moved to another and found that I have a GPS error and won’t let me open a new job. GPS status: No Date Message Recieved everything else looks fine and it’s streaming data. Anyone come across this?
(IMG_4423 (full).jpeg)
Attachments ----------------
IMG_4423 (full).jpeg (112KB - 235 downloads)
|
|
|
|
NW IL | What gps unit are you running? I’m guessing most likely either:
(1) Phoenix 200
(2) Phoenix 300/mba-6
Edited by swenzel 7/20/2024 15:00
|
|
|
|
| Phoenix 200 |
|
|
|
NW IL | Do you know if the Phoenix 200 is connected directly to the viper pro harness? Or is it first connected to a TM-1 tilt module and then to the viper pro?
You may not even have a tm-1 in your setup.
If the Phoenix 200 is connected directly to viper pro, there is an interface screen you can load to go in and verify settings of the 200.
If the Phoenix 200 is connected to the tm-1, to access the menu you have to disconnect the 200 from the tm1 and connect directly to viper pro harness.
If you bypass the tm1 and connect the 200 directly to viper pro and problem goes away, then maybe tm-1 is failing?
I am by no means a raven expert , just trying to establish what component is failing or causing trouble.
|
|
|
|
| No tilt component, connected directly and have had trouble getting the front panel to work just says connection please wait. When I changed sat. to 135 I had to borrow a pc from the case tech. Nothing ever work quite right. |
|
|
|
 Butterfield, MN | It's showing that it's getting GGA and VTG streaming at 10 hz, as it should, but it's missing the ZDA message for some reason. That will need to be turned on, 1 Hz should be fine. |
|
|
|
NW Illinois | My Viper Pro/ Phoenix 200 combo will do that randomly when I close a job. I usually hit the view data button, let that screen run a couple seconds and close it. This to date has restarted the data connection without having to shutdown everything and turn off rig to cycle power to the antenna.
Not sure what actually causes it. |
|
|
|
| I will try to look at that tonight, had to find my older laptop with a RS232 port as I have not had luck getting the viper pro to connect through the virtual front panel. I did buy a viper 4 with internal GPS this spring but didn't plan on changing over till this winter, after some creative wiring to the cable that came with it I was able to get back running, but I still would like to get the 200 working. |
|
|
|
| I've cycled power a couple of times with no change, still not sure why all the sudden just by closing the job it lost the ZDA message. Ill give that a try though can't hurt. |
|
|
|
 Butterfield, MN | I'd forgotten about how the Viper Pro can sometimes try to program the receiver, but if you have SmarTrax or a TM-1 between the receiver and the Viper Pro that may block the messages from getting back to the receiver. Still doesn't explain how the receiver got messed up in the first place, but it might explain why it's not being fixed. If you have the receiver directly connected to the Viper Pro without anything else between it, I believe you can go to Menu-Setup-Com Ports and put a check mark in Raven GPS, if it isn't already, and press OK. That should program the receiver correctly. If you do have SmarTrax or a TM-1 inline, you can always temporarily bypass them and try this, even though that's easier said than done, depending how much of a rats nest the cabling is in your cab. It's usually connecting the COM1 or DGPS plug from the Viper Pro over to the Port A (NOT A STANDARD SERIAL PORT) plug going to the Phoenix 200. If you get that to work, hook everything back up as it was and go back to Menu-Setup-Com Ports and select the Auto Baud button to get everything working again with SmarTrax or TM-1. |
|
|