I’m trying to connect my single GPS setup (simpleRTK2b & BNO085) via Ethernet using a USR-TCP232-T2. I’ve followed this thread but I can’t make a connection in AgIO at all.
I checked all the connections and configurations. Also turned off Windows firewall. Nothing seems to work and I’m running out of ideas Does someone have an idea what the issue could be?
Antenna was connected, uploaded the wrong picture.
Main problem (for now) seems to be that AgIO cannot find anything. Using version 5.7.2 but same issue occurs with older versions.
I don´t know the USR-TCP232-T2, but I think the IP numbers with 172.xxx indicate you also have an usb to eth switch connected to that computer.
I don´t know if USR require a crossed internet cable?
Try every of the 172 numbers instead of 192.168.5 and see if something comes through.(Default switch would be a good start)
The SEND would send to a Nano or Teensy, but also set AOG.
Or try a normal switch that outputs Ip adresses (like your home router) in between USR and usb-eth switch. And Use the IP your home router has.
I had a likely problem with my usb-eth switch, but only when not connected to home router before connect to USB.
So you could try this: Power USR, connect USR to USB-eth, then connect to computer
I wasn’t aware you could connect the bno via uart. I thought it had to be connected by i2c. You need to connect 3.3v to io ref on the f9p so it communicates using the correct voltage and doesn’t fry the tcp. Have you got the tx connected to the rx?
The Ardusiumple board is, or at least was marked incorrectly. RX is the data output and TX is the input. Why they do this I don’t know. So you need to connect tx to tx and rx to rx.
As pictured above, the TX line of the Ardusimple is correct (it’s designed to plug into Arduino’s RX on pin 0), and Ardusimple TX will go to RX on the Ethernet to uart adapter. But yes the ioref line is required.
As for the BNO on uart goes, there is nothing in AOG to process that data over ethernet or serial. Panda (and Panda RVC which may not be released yet) requires a TEENSY to connect to both the F9P and the BNO, and then sends $PANDA NMEA sentences over ethernet to AOG.
Local/remote port may not be labelled right in USR. A few models have jumbled labels. The tcp232 ed2 for example is backwards.
Just like UDP not check remote port, sometimes the english is right sometimes its not. This will turn on off the remote 2233 (check your port not 2223) port for corrections.
Print and sync baud rate should remain unchecked, not used in this instance.
I think I have one of these working connected to an emlid M2, will check settings tonight.
Ive only actually used UART2, which is incorrectly marked at least with respect to F9P uarts, so my mistake. I didn’t realise UART1 was correctly marked.
Here are the working settings from the tcp232 ed2. Windows must of thrown a security update, big problems scanning the network now after a subnet change. Have to restart each time this is new.
Baud is whatever you are using
Should say Remote/local port
Port 2233 is rtcm3 from agio to device
Port 2211 is data to teensy, you will need to change this to agio’s port.
255.255.255.255 is multicast, lets any device have the information
“Not check remote port” is a “check remote port” on this device.
Ive had an Owon hand held scope for quite a while. Great for in field diagnostics but a bit small for more involved stuff so Ive just bought a Rogol 1054z. Not had chance to use it much yet. Very good price for the spec. It does decoding of some common data interfaces.
Thanks for all the hints and tips I’ll look into it.
Regarding the BNO I thought AOG would be able to read it somehow via Ethernet (source). But it sounds like that this is not possible (yet?).