Is the UM982 an F9P killer for AOG?

UM982 logic, rx tx pins are 3.3v, so its important for converter to be 3.3v logic.

If you are referring to boards that have integrated usb port on them, they should have logic converter on them.

Can anyone explain the differences in the HEADING2 modes?
The difference between FIXLENGTH and VARIABLELENGTH is obvious, but I don’t understand STATIC, LOWDYNAMIC, and TRACTOR. My hunch is that STATIC is for a UM982 that’s e.g. on a building. That still doesn’t explain how LOWDYNAMIC and TRACTOR are different.

Also, it seems there is no relationship between HEADING2 mode and messages like HPR2 and UNIHEADING2. Those messages seem to be for a mode where multiple rovers are connected to the same base (perhaps drone “fireworks” shows?). Is this correct, that UNIHEADING is what I want for a slow-moving vehicle (sailboat)?

I am looking at boards with a USB socket on them. I don’t have any all-in-one boards and just making sure that there is no reason to use it with a teensy, unlike dual or panda F9p receivers.

Most of the information I could find for the UM982 seems to be for use on V4 boards.

Dual um982 can output ksxt direct to AgIO thru USB, teensy is not needed.

Heading2 is for heading only, so no good for AOG.

Fixlength is when distance is known between antennas, variablelength is when its not (F9P also uses variable base line). Variablelength is best mode as quality of rtk is higher than in fixlenght.

STATIC is that if you move you lose position, lowdynamic if you move like walking you also lose position. Tractor is mode with much averaging of roll and heading, but when error exceeds few degrees it suddenly jumps to correct value so its not usable for AOG. Idk if some other autosteer software want that behavior, if not I dont see why whould they add it and call it tractor mode.

1 Like

teensy: teensy_um982_alpha_12-10-23.hex
UM982:
Version 0.1
CONFIG ANTENNA POWERON
CONFIG NMEAVERSION V410
CONFIG RTK TIMEOUT 600
CONFIG RTK RELIABILITY 3 1
CONFIG PPP TIMEOUT 300
CONFIG SMOOTH RTKHEIGHT 10
CONFIG HEADING OFFSET 90.0 0.0
CONFIG HEADING RELIABILITY 3
CONFIG HEADING TRACTOR
CONFIG HEADING VARIABLELENGTH
CONFIG DGPS TIMEOUT 600
CONFIG RTCMB1CB2A ENABLE
CONFIG SMOOTH HEADING 10
CONFIG ANTENNADELTAHEN 0.0000 0.0000 0.0000
CONFIG SBAS DISABLE
CONFIG PPS ENABLE GPS POSITIVE 500000 1000 0 0
CONFIG MMP ENABLE
CONFIG SIGNALGROUP 4 5
CONFIG ANTIJAM AUTO
CONFIG AGNSS DISABLE
CONFIG COM1 460800
CONFIG COM2 460800
CONFIG COM3 460800
MODE ROVER SURVEY
GPGGA COM1 0.1
GPVTG COM1 0.1
GPHPR COM1 0.1
SAVECONFIG

Does anyone have any photos or experience using the Witmotion UM982 board with a V4.5 std board? - Witmotion UM982

Its the same as any other board. Juat connect rx and tx to where f9p should be. And add 5v and gnd and your good to go.

1 Like

Has anyone noticed that the heading is slightly delayed on the UM982? It might also be due to the configuration I’m using. I’ve already tested two configurations and got the same results with both. If I drive faster than 6 km/h, there are wavy lines.

If I corner and brake quickly to a stop, it takes about a second for the heading value to be correct. I haven’t observed this behavior with F9P or BY-NAV.

What are your um982 settings and dual or single

Dual Heading
Config:

Version 0.1
CONFIG ANTENNA POWERON
CONFIG NMEAVERSION V410
CONFIG RTK TIMEOUT 600
CONFIG RTK RELIABILITY 3 1
CONFIG PPP TIMEOUT 300
CONFIG SMOOTH RTKHEIGHT 10
CONFIG HEADING OFFSET 90.0 0.0
CONFIG HEADING RELIABILITY 3
CONFIG HEADING TRACTOR
CONFIG HEADING VARIABLELENGTH
CONFIG DGPS TIMEOUT 600
CONFIG RTCMB1CB2A ENABLE
CONFIG SMOOTH HEADING 10
CONFIG ANTENNADELTAHEN 0.0000 0.0000 0.0000
CONFIG SBAS DISABLE
CONFIG PPS ENABLE GPS POSITIVE 500000 1000 0 0
CONFIG MMP ENABLE
CONFIG SIGNALGROUP 4 5
CONFIG ANTIJAM AUTO
CONFIG AGNSS DISABLE
CONFIG COM1 460800
CONFIG COM2 460800
CONFIG COM3 460800
MODE ROVER SURVEY
GPGGA COM1 0.1
GPVTG COM1 0.1
GPHPR COM1 0.1
SAVECONFIG

This can couse that behavior. Set it to 0

1 Like

CONFIG PPP TIMEOUT 300 ???
$command,CONFIG PPP TIMEOUT 300,response: PARSING FAILED FIELD OUT OF RANGE,300*7E

yes had this error to. set it to 180 and it works

i will try it

Is it better to use rover mode automotive instead of survey? As it seems survey mode should be better for static scenarios like geodesy and could be filered and less responcive to rapid movements. And automotive should work better in dynamics.
Maybe someone tried any other modes?

After using the UNLOGALL command the Constellation window and Tracking Status windows are blank. What command is used to view the constellation and tracking status information again?

The default configuration just outputs the GGA, VTG, GSV, GSA sentences etc with an the satellite data. If you turn them off, the software can’t display anything. If you didn’t save the setting, try power cycling the receiver to restore the settings.

I’ve got myself in a bit of a muddle with a Witmotion UM982 board and need to reset it.
I can’t quite seem to work out where or how to enter the freeset command.
I’ve tried reflashing with Configomatic but doesn’t seem to help.
In Uprecise configuration page I just get Query response timeout.

Did you try manual baudrate. Tye 115200 or if flashed before with the configmatic tool try 460800 as baud and send a message