Hello,
I’m a bit confused about how to configure the ZED F9P using u-center(stand alone operation).
Our HW and SW version are as below :
HW
-version : 00190000
SW
-version : EXT CORE 1.00(61b2dd)
Extension
-ROM BASE 0x118B2060
-FWVER = HPG 1.12
-PROTVER=27.11
-MOD=ZED-F9P
GPS;GLO;GAL;BDS
QZSS
- Firstly, I tried to set configuration using your drotek github web(https://github.com/drotek/RTK-ZED-F9P-GNSS/archive/master.zip) and referring to your document web site. And then I setup the system as follow picture.
But this setting is not worked. I think the base system is working well(I already checked the status(TIME) of base module). But the rover module always shows the status is ‘3D’ in u-center.
I don’t understand this situation. So I checked the output(RTCM) of base module using terminal program.
Actually I cannot interpret the binary output, but this protocol/packet is showed in terminal program with constant time interval.
In this situation, I wonder the telemetry setting parameter(baud rate, data type …) and then I tried to change both setting(telemetry and gps modules).But this is not worked.
- So I tried changing the configuration as follow picture,
As you can see, I changed the connection between base and rover module from wireless to wired ( UART1, UART2 ).
And then I tried to check the packet status using u-center, I can see the status of RX/TX bytes and message parse/process in Message view-‘UBX’-‘IO’& ‘MSGPP’ tab.
In base module side,
The TX bytes(UART2, RTCM port) is increasing,
In rover module side,
The RX bytes(UART2) is increasing, but this message is just ‘UNKNOWN’ bytes in MSGPP monitor.
I think the rover module receive the packet, but the protocol is not valid.
So I tried changing the HW port(UART1<-> UART2), setting the ‘PORT’…
But this is still not worked.
Any idea or solution how to fix this problem?!