47 | | = Hardware Headers & Pinouts |
48 | | |
49 | | == J1 Antenna |
50 | | |
51 | | Standard MMCX Connector (Molex 73415-2061) |
52 | | |
53 | | '''Note an active antenna is required by the ZED-F9P''' |
54 | | |
55 | | Recommended Antenna: |
56 | | |
57 | | * u-blox ANN-MB-00 Multi-band active GNSS antenna w/5m cable and SMA Male connector [https://www.u-blox.com/en/product/ann-mb-series Link] |
58 | | * Available at Digikey:[https://www.digikey.com/products/en?keywords=ANN-MB-00 Link] |
59 | | * Gateworks mating cable (GW10074 MMCX to SMA Female): [https://shop.gateworks.com/index.php?route=product/search&search=gw10074 Link] |
60 | | |
61 | | |
62 | | |
63 | | == J5 & J3 UART Headers |
64 | | |
65 | | 4-pin Right Angle 1.25mm header (Molex 0781710004) |
66 | | |
67 | | Note, J3 uses UART2 and J5 uses UART1 from the u-blox ZED-F9P |
68 | | |
69 | | ||Pin||Signal|| |
70 | | ||1|| 3.3VDC + || |
71 | | ||2|| UART_TX || |
72 | | ||3|| UART_RX || |
73 | | ||4|| GND || |
74 | | |
75 | | == J2 Timepulse Header |
76 | | |
77 | | 4-pin Right Angle 1.25mm header (Molex 0781710004) |
78 | | |
79 | | ||Pin||Signal|| |
80 | | ||1|| 3.3VDC + || |
81 | | ||2|| Timepulse || |
82 | | ||3|| Interrupt || |
83 | | ||4|| GND || |
84 | | |
85 | | == LEDs |
86 | | ||Reference||Description|| |
87 | | ||D1|| 3.3VDC Power - Green || |
88 | | ||D2|| Timepulse - Yellow || |
89 | | ||D3|| RTK - Yellow ![1]|| |
90 | | ||D4|| Geofence - Yellow ![1]|| |
91 | | |
92 | | * ![1] See [wiki:expansion/errata#GW16143RTKandGEOFENCELED] for related errata on rev A units. |
| 49 | |
| 50 | |
289 | | The easiest way to use !PointPerfect with the ZED-F9P is through [https://github.com/semuconsulting/pygnssutils pygnssutils]. Our examples also leverage the GW16126 for cellular connectivity and were able to get very precise data in a moving vehicle, even with relatively low reception, though !PointPerfect has various delivery methods (NTRIP, MQTT, L-Band). For this example, the script works without too much configuration since Linux automatically configures cellular modems to make connections work seamlessly. |
| 248 | The easiest way to use !PointPerfect with the ZED-F9P is through [https://github.com/semuconsulting/pygnssutils pygnssutils]. Our examples also leverage the GW16126 for cellular connectivity and were able to get very precise data in a moving vehicle, even with relatively low reception, though !PointPerfect has various delivery methods (NTRIP, MQTT, L-Band). For this example, the script works without too much configuration since Linux configures cellular modems to make connections work seamlessly. |
297 | | |
| 258 | [[Image(point.jpg, width=500)]] |
| 259 | |
| 260 | == |
| 261 | |
| 262 | = Hardware Headers & Pinouts |
| 263 | |
| 264 | == J1 Antenna |
| 265 | |
| 266 | Standard MMCX Connector (Molex 73415-2061) |
| 267 | |
| 268 | '''Note an active antenna is required by the ZED-F9P''' |
| 269 | |
| 270 | Recommended Antenna: |
| 271 | |
| 272 | * u-blox ANN-MB-00 Multi-band active GNSS antenna w/5m cable and SMA Male connector [https://www.u-blox.com/en/product/ann-mb-series Link] |
| 273 | * Available at Digikey:[https://www.digikey.com/products/en?keywords=ANN-MB-00 Link] |
| 274 | * Gateworks mating cable (GW10074 MMCX to SMA Female): [https://shop.gateworks.com/index.php?route=product/search&search=gw10074 Link] |
| 275 | |
| 276 | |
| 277 | |
| 278 | == J5 & J3 UART Headers |
| 279 | |
| 280 | 4-pin Right Angle 1.25mm header (Molex 0781710004) |
| 281 | |
| 282 | Note, J3 uses UART2 and J5 uses UART1 from the u-blox ZED-F9P |
| 283 | |
| 284 | ||Pin||Signal|| |
| 285 | ||1|| 3.3VDC + || |
| 286 | ||2|| UART_TX || |
| 287 | ||3|| UART_RX || |
| 288 | ||4|| GND || |
| 289 | |
| 290 | == J2 Timepulse Header |
| 291 | |
| 292 | 4-pin Right Angle 1.25mm header (Molex 0781710004) |
| 293 | |
| 294 | ||Pin||Signal|| |
| 295 | ||1|| 3.3VDC + || |
| 296 | ||2|| Timepulse || |
| 297 | ||3|| Interrupt || |
| 298 | ||4|| GND || |
| 299 | |
| 300 | == LEDs |
| 301 | ||Reference||Description|| |
| 302 | ||D1|| 3.3VDC Power - Green || |
| 303 | ||D2|| Timepulse - Yellow || |
| 304 | ||D3|| RTK - Yellow ![1]|| |
| 305 | ||D4|| Geofence - Yellow ![1]|| |
| 306 | |
| 307 | * ![1] See [wiki:expansion/errata#GW16143RTKandGEOFENCELED] for related errata on rev A units. |