Panda - ADC Connecton FAILED!

4

PCB V2 will turn the steer module green, running it in conjunction with PANDA all that will be used on the V2 is the ADS. ACS712, and the Cytron.

Remember to disable any BNO connected to V2, physically by removing wires or in software by putting a false address into i2C.

Pay no attention to the serial debugger, its debugging a device that does not exist. The teensy debugger does not see the nano on V2 and vice versa. Just move the WAS back and forth that is still connected to the V2 and it will show up in AOG like it always has before.

The serial debugger has no effect on actual performance.

Do you have any duplicate IP’s?

5

Does your f9p have same gnd as teensy?
In my test setup with f9p powered by powerbank, the teensy only started blinking orange after both 3v ioref AND gnd were connected to the teensy.
( I had no teensy pcb) And off course sda scl.

6

Ok so still the PCB V2 with nano to read the WAS and control the motor, no IMU on it?

So instead a GPS you have an UDP PANDA board

Thats good, there is no IMU connected to AGio since it is connect to the Teensy!

Do you have problem with the PANDA teensy or the Autosteer nano?

You are showing debugging from the Teensy and talking about ADS1115 problem running with the nano on the pcbV2?
2 different problems
Or am I misunderstanding something?

7

Yep same ground. 5V to 5V pin and 3.3V out to F9 and BNO. (“the teensy only started blinking orange” I don’t get any lights on teensy.

8

No IMU on PCB V2.

Yep BNO & GPS on Teensy UDP.

I see no problem with Autosteer. I’m not getting connected to AGIO with teensy - at least I have no green showing up that I can attribute to Teensy.

I think PF’s post might solve this.

9

Ensure that you are using the latest panda firmware. I had that issue by using firmware which was released with V5.62.

All in One PCB - Hardware - AgOpenGPS

edit2: Unfortunately the link works not properly should be linked to dialog 372

10

Try this firmware:

It’s from \PandaUpdates:

Autosteer_gps_teensy_v5_5.zip (45,3 KB)

1 Like
11

@wland The version # is the same as I’ve been using but something is different cause it works!!!

Thanks to all of you!

2 Likes
12

Like a bad penny I’m Back!!

I’m not getting any GPS data to show in AGIO when I choose GPS data. I figure I either have to be moving and/or I have the wrong firmware and config files.

Could you attach firmware and config files that you are using successfully?? There are a number of diff versions in other threads and diff download versions. Which ones to use and in what combo??

Do I need to be moving to see GPS data??

Thanks

13

First check your teensy with the serial monitor:

Are there a “swapping port” messages or did you get panda sentences?

It is not necessary to move, but you should have free sky view, to get full gps data, but normally it’s working if you place the antenna at the window.

14

I’m guessing this is panda!!!

$GLGSV,1,1,02,87,01,299,88,04,342,076
$GAGSV,2,1,06,02,37,185,33,03,81,053,31,05,31,111,34,13,11,285,23,27A
$GAGSV,2,2,06,24,25,044,23,25,64,107,34,274
$GAGSV,2,1,08,02,37,185,37,03,81,053,21,05,31,111,25,08,39,305,10,77D
$GAGSV,2,2,08,13,11,285,25,15,03,237,08,24,25,044,28,25,64,107,33,770
$GAGSV,1,1,01,26,03,334,046
$GBGSV,1,1,01,32,60,156,31,140
$GQGSV,1,1,00,064

15

$PANDA will be panda, if you see panda you will see no other NMEA.

For Panda the gps needs to be connected directly to the Teensy serial port.

Nmea->teensy4.1->PANDA->AOG

Also I am not sure why you have satellites in view turned on?

16

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.

17

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!

18

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.

19

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)

20

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?

21

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

22

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)

23

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.