I find you have to drop rate to 1hz before flashing, if you leave it at 8hz it will error, every time i flash, I just change to 1hz, flash, and good to go…
1 Like
So this is where i have the boards know. Is their any other modifications i need to make. Thanks
Looks good, BUT bend the IORef of the Ardusimple, so it won’t go down to the 5V of the ESPduino. The IORef is the supply for the RX/TX pins on the Ardusimple.
ESP needs 3.3V at the GPIOs, 5V will destroy it. So put 3.3V to the IOref on the Ardusimple and provide them from getting down to the 5V IOref pin from the esp.
The “move” of the TX2 to RX2 on the other board looks good, is the TX2 pin (white cable) cut of, so it won’t get into other board TX1?
Actual configs (8Hz, pedestian…) in master branch, latest code in beta branch
on bottom board the pin that would go into 5v on esp is bent over to connect to 3.3 pin but i have not changed anything on top boards IO ref pin so i think your saying that is correct. And yes TX2 pin under white cable is cut off on top board. Thanks
So would you recommend running code from the beta branch??
1 Like
For who doesn’t want to solder to Board. Use the Pixhawk connectors
- 1: 5V_IN
- 2: ZED-F9P UART1 RX (3.3V level)
- 3: ZED-F9P UART1 TX (3.3V level)
- 4,5: Not connected
- 6: GND
And crosslink ZED-F9P UART2 on the Xbee Header (RX>TX TX>RX)
3 Likes
Is the Pixhawk connector 3v3 without the need for ioref being set on the board?
Very neat.
Indeed the UART signal levels are 3.3v without soldering ioref.
The 5V is used to power the board needs about (600mW = 120mA) per board
The board is using a JST SM06B-GHS-TB connector.
The cable should have JST GHR-06V-S as the matching connector.
The Xbee header pin spacing is 2MM, used 90 degree male headerpins here
Thanks!! That was my next question. 
Cool Idea, I thought about this too. Alternatively a PCB. But the Y cable is easier
This seems to be a very simple hookup and would like to see the complete setup to the esp32. Also thanks for adding the connector numbers as this helps those of us will little experience with electronic. When searching for things in Digi-Key it can be overwhelming trying to find things when you do not know what they are called, especially when there is no picture to look at. With that said what are the connectors at the end of the wires with the black sheath, that go into the headers? Are they crimped on to the wires or soldered? Thanks
I ordered the white connectors JST GHR-06V-S on ebay, they came with pre-crimped wires. So just had to put them in the housing at the right place.
The 2 wires on the xbee headers at the top are soldered to 2mm 90degree male pinheaders with some heat-shrink.
Instead of taking some more blurry pictures. Just made this drawing, The ESP pin numbers are the defaults from MTZ8302’s sketch.
7 Likes
Neat idea to use the Pixaxe connectors, but I did it this way:
Using 10mm plastic stackable spacers it needed a few washers to get the spacing right. Three spacers needed shaping to clear the Xbee headers and one espuino header. I used every other wire in the 50 thou spacing ribbon cable only because it was handy but you could use 0.1" ribbon cable. ( note the twist in the RX1 TX1 pair to the top position module)
I put the position F9P on top as I might need to use the top xbee socket for NTRIP RTCM rover input. This would make it standalone and independent of AOG for NTRIP . Only the RX2 for the Transmit of RTCM from pos to heading is needed leaving the receive (confusingly named TX2) free to get RTCM from an xbee if needed. The RX2 and TX2 labeling are confusing as they relate to the xbee point of view not the F9P point of view.
I just used a six way stackable header on each side to pickup three gound pins and the 5volt pins rather than connect all the pins
Seems to work ok but I cannot get the wifi link to work, it just times out and invokes the onboard hotspot.
How are people using UDP though? through the wifi link or would a better way be via an ethernet sheild / adapter?
Actually doesn’t the ESP32 have some ethernet capability built in?
Bottom and top views to complete the picture:
Does anyone have a definitive answer to this?
1 Like
If you want precision to be better than 1.5 m, yes. Dual GPS does not improve precision, it only adds relative position between sensors. (which helps to determine heading, roll etc.)
U-blox wrote a doc on this subject
I understand RTK. I use it. @darrenjlobb noted that if he lost RTK fix with his dual receiver setup he immediately lost autosteer. That was my question.
I think, (But matt / franz would know more than me) that the issue, is that the F9P’s dont give heading without RTK correction, so as soon as its lost, the ESP code has to revert to fix-fix, which in itself shouldnt be a problem, but for some reason it is for me. The problem is that when I loose RTK fix, my gps slows down / lags to 5hz or less, rather than 8, which is to slow and causes the steering to occilate…I am certain it can be fixed / no doubt matt already has / can sort it at some point. At the moment they have both been working super hard to try and get the main math / calculation sorted so it is reliable / correct in all areas of the world.
Hi
Does someone have a schematic of how to wire the connections of the two ArduSimple to the ESP32Duino with MTZ8302 AOG_GPS_ESP32. Instead of looking at blurry pictures.
I can’t get it to work so would be grateful if someone has it up and running to make a schematic.
thx
1 Like
My project thread as some photos from mine which may help?