I read the thread again, and it looks like you have no panda board.
So did you use the two 2.2 K ohm resistors between 3.3 V and SDA and SDL which are pin 18 and 19 on teensy, used for the BNO (I used some 3.5 Kohm I had, and on PJRC forum 4.5 K ohm is mentioned as pull up for teensy inputs)
I do not have pull ups on teensy pin 28 and 29 where F9P rx tx is connected.
I see the two pull ups, are used on all three boards: Basic Panda, Panda Hat, and all in one teensy autosteer.
I got the config file from 5.6.33. I was having a h–l of a time getting firmware to load. That one finally took.
I figured that one out about 3 AM this morning.
I did not on my breadboard setup. I checked this AM and I do have them in my PCB schematic. I’ll put them on the breadboard this AM.
Thanks guys!
You can connect the the teensy directly to the sda/scl of the chinese bno and adafruit boards as these resistors already exist on them. No extra parts required.
You are receiving from your receiver, thats a good sign, but not the right packets.
Normally, only GGA and VTG Messages should be enable at your F9P. (via u-center)
Which receiver do you use ? Ardusimple , Sparkfun …?
The config files are only for the Ardusimple ones.
It’s also from \PandaUpdates:
Ublox F9P Configurations.zip (1,3 MB)
Good to know as I’m using an Adfruit.
So I need a different config? A F9 is not a F9? They are the same Ublox chip.
I used the BIN file you attached and the 1.32 SingleAntennaRover config.
Do I need a different one?
The F9P is the same, but there are different pheriperals on the boards.
I’m using the ublox C099 F9P Board, it won’t work with a ardusimple config.
I do my config manually.
Which board do you use?
Try out to use u-center to show the actual configuration:
Improved konfiguration files for f9p with firmware 1.13 - GPS / RTK / GNSS - AgOpenGPS
Don’t forget to store changes in the flash memory
I’m using a ZED-F9P SMA from Sparkfun.
When I started up after dinner I was back to Swaping ports.
I redid the firmware 1.32 and the config file as in the above post. This time I did as suggested in the link you just posted and disabled everything but GGA and VTG. Here is what is coming out in Ucenter. (I unplugged it and plugged it back in to make sure it stuck.)
20:11:52 R → NMEA GNVTG, Size 21, ‘Course Over Ground and Ground Speed’
20:11:52 R → NMEA GNGGA, Size 42, ‘Global Positioning System Fix Data’
20:11:52 R → NMEA GNVTG, Size 21, ‘Course Over Ground and Ground Speed’
20:11:52 R → NMEA GNGGA, Size 42, ‘Global Positioning System Fix Data’
20:11:52 R → NMEA GNVTG, Size 21, ‘Course Over Ground and Ground Speed’
20:11:52 R → NMEA GNGGA, Size 42, ‘Global Positioning System Fix Data’
20:11:52 R → NMEA GNVTG, Size 21, ‘Course Over Ground and Ground Speed’
20:11:53 R → NMEA GNGGA, Size 42, ‘Global Positioning System Fix Data’
20:11:53 R → NMEA GNVTG, Size 21, ‘Course Over Ground and Ground Speed’
20:11:53 R → NMEA GNGGA, Size 42, ‘Global Positioning System Fix Data’
Start setup
SerialAOG, SerialRTK, SerialGPS and SerialGPS2 initialized
Here is where I am (again) from the serial monitor.
Starting AutoSteer…
ADC Connecton FAILED!
Autosteer disabled, GPS only mode
Starting Ethernet…
Initializing ethernet with static IP address
Ethernet cable is not connected - Who cares we will start ethernet anyway.
Ethernet status OK
IP set Manually: 192.168.1.120
Ethernet IP of module: 192.168.1.120
Ethernet sending to IP: 192.168.1.255
All data sending to port: 9999
Ethernet GPS UDP sending from port: 5120
Ethernet NTRIP UDP listening to port: 2233
Ethernet AutoSteer UDP listening to & send from port: 8888
Starting IMU…
Swapping GPS ports…
Swapping GPS ports…
I unplug the 5V to the teensy when I plug in the USB (if that makes a diff)
From your first post, you are trying to use PANDA + V2 board?
So first we just want to make PANDA, try swapping your rx tx wires from the Sparkfun to the teensy. Ensure the baudrate is set the same inside the sparkfun and in the teensy. Uart 1 is the mosi/miso on the sparkfun.
make sure the “dsel” jumper on the back is not soldered shut.
If the teensy is making panda it will blink, Panda will leave on the teensy Ethernet connection. The Green data light on the Ethernet port will blink fast and continuous if PANDA is being sent.
If you are using V2 as the input for the WAS, the teensy will always say ADC connection failure because it is not there. The serial debuggers only work on the local device they are directly connected to.
Triple check that all of your devices IP’s are on the same network, and do not have a duplicate last number.
Be sure to send it to Uart1 also, not only USB
I[quote=“Pat, post:24, topic:11024, full:true”]
Be sure to send it to Uart1 also, not only USB
[/quote]
It has passed 24 ,so Happy New year 
used f9p firmware 1.13 with config 1 13.
Had no issue connecting to teensy .
When uploading firmware or config, make sure baud is quite high. Above 115000.
I am not sure 1.32 is an advantage for agopen.
1.13 has 10 Hz which is quite sufficient for autosteer. 1 32 can go higher as far as I know.
1 Like
Swapping GPS ports mean you have now communication between Teensy and your Sparkfun receiver!
I had to swap the RX/TX wires on my C099 regarding to the original Panda board schematic. It’s important to have the same baudrates on each side.
Yes that is right.
Swapping RX and TX has no effect. and I’m hooked to pins 7 & 8 - RX2 - TX2.
I figure I should be configured as described in the Sketch.
// Configuration of receiver
// Position F9P
// CFG-RATE-MEAS - 100 ms -> 10 Hz
// CFG-UART1-BAUDRATE 115200
// Serial 1 In - RTCM (Correction Data from AOG)
// Serial 1 Out - NMEA GGA
// CFG-UART2-BAUDRATE 460800
// Serial 2 Out - RTCM 1074,1084,1094,1230,4072.0 (Correction data for Heading F9P, Moving Base)
// 1124 is not needed (China’s BeiDou system) - Save F9P brain power
Here is what I have
The RTCM messages are greyed out & I haven’t figured out how to select them. I’m Also not sure of how to set -
Serial 1 In - RTCM (Correction Data from AOG)
Serial 1 Out - - NMEA GGA
1 Like
Make sure the baudrate set for gps port in teensy ino is the same as uart1 baudrate on f9p. If these two settings dont match, my experience is you will be stuck wit «switching gps ports»
Check:
UART1 must be checked!
In my case must using Baudrate 460800 because of the internal need of the C099 board, also I don’t use UART2
1 Like
@wland I have set my config as you have shown above. I get connected and AGIO shows panda connected but I still have no GPS. I have swapped wires on pins on both UART1 and UART2 (on the f9) - no change. I also did continuity test from pins on teensy to pins on GPS to rule out bad wires.
@PotatoFarmer Could you share your config file? You have your Sparkfun f9 working so maybe it would make mine work also.
Just for my understanding, you tried for sure:
Teensy Pin 7 RX2 to F9P RX/MOSI
Teensy Pin 8 TX2 to F9P TX/MISO
and cross both wires
Teensy Pin 7 RX2 to F9P TX/MISO
Teensy Pin 8 TX2 to F9P RX/MOSI
with setting the baudrate 115200 for UART1 on Teensy and F9P side
Note: Be sure the DSEL jumper on the rear of the board is open.
1 Like
So you get the $PANDA message received in AgIO but just unpopulated?
Here is my sparkfun 1.32 config file, but I do not use Glonass, and uart1 I have set to 921800 because its used in an all UDP setup with a ttl adapter.
AgOpenGps Sparkfun UDP PANDA v1.txt (25.0 KB)
the config for these is a bit of a beast, it needs the port, message type and message to be enabled one by one. This is the gen9 configuration view I find it easier to use.
I am so glad you raised the question. In all my switching around I had put the wires on the X2 pins and not the MOSI. I now have Panda sentences with serial monitor. Orange light on teensy is flashing, that’s a first for that!!!
I have a green light on the antenna in AGIO, which I have not had until now and I have a GPS signal and tilt in AOG. 
THANK YOU ALL!!!
3 Likes
I was updating from 1.13 to 1.32, teensy wasn’t seeing it, I made the configuration as the ray_jorgensen suggested. it works perfectly now. The only problem I don’t understand is that I did the speed this way while updating, I wasn’t sure if I did it right.
The speed of the update process itself depends on this.