[HOW TO] TTL to Ethernet with RPI

UAVPilot

Bernt...yes, I can sucessfully ping the TTL from the RPi. I have tried both shared gnd but most the times I used separate gnd.
See current ps ax below:

image 479759455580d14242dc9b923926635.png

I will try this again with single gnd.

Sinamics

Gents, im currently offshore and my online connection is on/off all the time. Just so you know.

UAVpilot
That seems fine. I bet your problem is either wrongly connected wires, or ground issue.
You can connect your laptop directly into the TTL adapter (Set static ip on your laptop, same as RPI) and you should be able to connect using Mission Planner, That way you can verify if TTL is working properly.

Skylab.
Normally a ESC calibration is started by having the Throttle at full speed while connecting your battery. A special beep sequence should take place and then you move the throttle to the bottom, following by a beep sequence.
You need to read the Esc manual to get that right.

Before starting Esc calibration, your radio needs to calibrated propely in mission planner.

UAVPilot

Bernt, I have replaced the eth port IP on my my laptop with the eth (eth0) IP address of the RPi. I am able to ping the TTL from my laptop but still unable to communication the TTL and Mission Planner. I also tried AMM Planner as well, still no change. In an earlier attempt, I also tried changing the TTL IP address and Gateway to the IP address the IP address that was on eth port of my laptop, still mission planner not able to connect.

My RPi w/ArduPilot 2.5 with GPs and TTL. 5v power to ArduPilot is coming laptop USB, black USB cable on upper right corner plugged into laptop. Another 5v black cable leaves ArduPilot into RPi.

image 811897432580d2c91572fb266671968.jpeg

5v delivered to TTL from telemetry port on ArduPliot.

image 769758357580d2ca2bbbb8945790641.jpeg

Telemetry port on ArduPliot, this 4-pin extenstion cable is connection to TTL. (See above)

image 2120596761580d2cb51d8ee843606944.jpeg

The orange and white cable is in fact 5v/gnd from the USB port on laptop. The other 5v/gnd (red/blk) goes to power RPi.

image 634920653580d2cc51cc86368730503.jpeg

Both RPI and ground into the Ardupilot share common ground. This is my set up, once again I cannot connect and communication with Mission Planner.

Sinamics

UAVpilot..
Thank you for the pictures. Seems like everything is properly wired.
I know the APM will not start to send telemetry as long as USB cable is connected, but it seems like you dont have the USB plugged in.

Are you sure the telemetry port is working?

Chuckster1

Probably not your problem, but you could try swapping send and receive....won't hurt anything..will only work 1 way, not the other.The transmit from 1 goes to the receive of the other. Also, I'm not sure about your USB power coming from your laptop.

That is going through your flight controller and back out to the Raspberry Pi and also to your serial to ethernet ...seems like too big a load for 1 USB laptop port (possible voltage drop, causing things not to work right?...just a theory).When my setup wasn't working, I got 915mhz telemetry radios to verify that my telemetry port worked, and it ended up being my settings in my serial to ethernet converter.Can you take a picture of your settings in your converter?

UAVPilot

Bernt,
At the time I took the pictures, it was when I had just finished testing the possiblility of APM 2.0 connecting my TTL via the eth port on my laptop. Of course I had to change the IP of the eth port on my laptop to the same IP as eth0 on my RPi. So that is why it is pictured that way, other than that it was connected to the eth0 on the RPi all along.

Chuckster,

I have checke the tx/rx on both the TTL and Ardupilot and I have swapped them several times. I read about 3.4 - 3.8v from both tx/rx. I will test you power theory, after all there is a drop in voltage before it hit the RPi however it is not a whole lot. I just checked it and it is 4.74v into the RPi.

It is possble the USB is not providing enough current, I'm only using the USB from laptop until my Lipo comes in. I have some parts coming in and will connect the Lipo into the system, maybe that will work.

Here are the TTL configs:

image 504115587580ea43538417737955514.png

Thanks for the follow ups.

skylab

sorry is your module ip 192.168.0.10 while your gateway 192.168.0.110?

If yes then that is wrong

skylab

I think an Ethernet ip can not work that way. In my case I connect the raspberry via Ethernet cabel to my pc, and I ping raspberrypi.mshome.net through cmd to know my Ethernet ip and I got 192.168.137.27. now I know that 192.168.137. is the Ethernet ip then I added 250 to the last part for my ttl ip 192.168.137.250. and my gateway is rpi ip. that worked perfect for me.

skylab

on rpi i made a static eth0 : 192.168.137.50

UAVPilot

By connecting the RPi eth0 port to your laptop eth port, you pinged from RPi to your laptop and found the IP of eth to be 192.168.137.27. Realizing the subnet is 192.168.137.x, you then made the TTL ip 192.168.137.27 and the RPi 192.168.137.50. To sum this up: RPi eth0: 192.168.137.50 TTL eth: 192.168.137.250 Is this correct?

skylab

To sum this up:

RPi eth0: 192.168.137.50
TTL eth: 192.168.137.250

Is this correct?

skylab

i think ttl only work with eth0 ip. so in my case the defalt eth0 ip in my country is 192.168.137.x I don't know about others

skylab

By connecting rpi to Ethernet port on my laptop, I first shared the network on my laptop. I then ping the rpi by typing "ping raspberrypi.mshome.net" . the ping gave me the eth0 ip of my rpi as 192.168.137.x and I then made my rpi Ethernet ip static in /etc/dhcpcd.conf as 192.168.137.50/24 which means my ttl ip should be 192.168.137.x

skylab

This should explain the eth0 ip part

image 504115587580ea43538417737955514.png

image 2030284968580f6dd9d2c36189213546.png

skylab

now your ttl should be 192.168.137.x only if your config is like this

UAVPilot

Skylab,
a bit unsure becasue in two diffrent post you show two different eth0.

From yourt RPi you have:

192.168.137.50/24 on RPi Eth0
192.168.137.250 on TTL

From your CMD you have:

192.168.137.55 RPi Eth0

Either way you are putting the TTL and the RPi eth in the same subnet, which is what I have.

My TTL is 192.168.0.10
My RPi eth0 is 192.168.0.110

This set up is the same as your set up.

skylab

when you ping rpi from your laptop when your rpi is connected via Ethernet port, what ip do you get?

UAVPilot

Give me a few hours, I will check once I get home.

UAVPilot

skylab, see results below:

Ping from eth on laptop to eth0 on Rpi.

image 165293867580ff7c1ddafe750516569.png

Laptop IP configs:

image 33683585580ff80995474824363388.png

Ping from eth0 on RPi to eth on laptop.

image 305502569580ff866c9616505628466.png

RPi IP configs:

image 1310367437580ff847871b8890890481.png

I am not able to ping the RPi eth0 from the laptop eth and not able to ping the laptop eth from the RPi eth0 as they are on differnt subnets. I think this is expected but correct me if I am worng.

TTL configs:

image 1316271080580ff8cbb9496068472476.png

I feel that I have the same IP config format as both you and Bernt, let me know what you think.

skylab

you are pinging the ip. I think you should ping raspberrypi.mshome.net from your computer but make sure you are connected to rpi via laptop Ethernet port

image 20401988580ffc4055d5e931139089.png

« Previous Page Next Page »