i am facing a problem with understanding the platform awareness concept. My aim now is to make 2 agents communicate (one agent is on my laptop and the other one is on my raspberry pi) and my laptop & pi are connected to the same wifi network. The agent on my laptop provides a service that is required by the agent on the pi. I am facing a problem with the binding and scope arguments.
Hope anyone can help me
Regards,
Sandra
Related
Let me explain what I want to happen.
I have an http server program that displays a website every time I connect to my raspberry pi's ip address on port 8080. But this only works on my current network. I want to be able to access this raspberry pi from any network by typing a website address. How would I connect my URL to this raspberry pi so that I can just type the domain and it will take me to my raspberry pi?
P.S. I have already tried searching for this extensively, but none of the results fits my needs
Thank you in advance,
Nick.
Assuming that your current network is your home network and any network is the internet as such, I think your question points into the direction of dynamic DNS (DDNS).
DDNS allows you to assign a fixed domain name to the (usually) varying external IP adresses of your home network.
This would make your PI reachable to the outside world.
Search for DDNS providers.
This post is related to ROS (Robot Operating System) and ESP8266, and has also been cross-posted on ROS Answers and Robotics Stack Exchange.
I've ROS Melodic running on a Raspberry Pi 4 and need to send out information (as strings) over wifi to multiple ESP8266. I'm only just starting so it's just one ESP8266 for now. For communication, I'm using socket_node found in the ROS package rosserial_server (package wiki).
Referring to the picture below, the slave node publishes to the topic /Topic_data_over_wifi which is subscribed by a node running on the ESP8266:
The problem is, the node /rosserial_server_socket_node remains floating!
I've double checked names of topics and IP addresses, and at one point, got the node /rosserial_server_socket_node to actually link to the rest of the ROS network as shown in the "What I want" section. However, that was just one time (a fluke?) and never could I again get /rosserial_server_socket_node to join the ROS network.
rosserial_server's socket_node is used with its default settings (port 11411). I did try other port numbers but there was no difference. After all nodes have been launched, here's the output of rostopic list (other than the usual /rosout and /rosout_agg):
/commands_from_master_node
/topic_data_over_wifi
Goal: I need to find a way to connect the ESP8266 and the Raspberry pi 4 over wifi using ROS. More specifically, I need to get data from the slave node (on Raspberry Pi) to the node running on the ESP8266.
I've already looked at this multiple-TCP-connections post but didn't find anything that could solve my problem.
Any inputs/suggestions will be very appreciated.
Depending on the software running on the ESPs, it might be an option to use the ROS MQTT bridge. The downside is that you will need an additional MQTT broker (I am not sure, but as I recall mqtt_bridge is an MQTT client and requires a broker like Mosquitto). You can add MQTT clients to the ESPs and connect them to the same broker and subscribe to MQTT messages. In other words, you create a MQTT network for the ESPs with their borker and add ROS to that network, via mqtt_bridge. If you are not running ROS specific software on the ESPs it should work fine.
I've worked a tad with IOT on Raspberry pi before, but as a student I ran into a problem and was hoping someone could answer my question. So I need to run Windows IOT Core on the Raspberry Pi 3 (if it was up to me I'd use raspbian or some other flavor of linux, but it's not up to me) and I need to run it at a school who's network I don't have access to. Is there any way of running IOT on raspberry Pi without an internet connection. I had read somewhere that I could buy a router (and even though there was no internet connected to it) I could run ethernet from the router to my laptop and another from the router to the raspberry pi and ssh into the pi from my laptop. Is this true? and how would I go about ssh-ing into the pi? OR is there a better/alternative solution to running IOT with no internet?
You can directly connect Raspberry Pi to your laptop with the network cable. Then the Raspberry Pi will get an IP address. With this IP address, you can either debug app with Visual Studio or connect to the Raspberry Pi via SSH. There are some tools like IoT Dashboard or Device Portal you may need.
For more information about connecting Windows 10 IoT Core, you can reference Windows 10 IoT documentation->Connect your device.
I have a task to connect PROFIBUS (field bus technology by Siemens) to my Raspberry Pi. I need to make my Raspberry pi as a master and others devices as a slaves.
Let me know if you have any idea about how to make this connection. I am totally new in this topic and have no idea about this.
You might have a look at this project: https://bues.ch/cms/automation/profibus
When I understand it correctly, Profibus (Modbus) ist implemented by RS-485, that is not directly supported by the Raspberry Pi GPIOs.
You have to buy an extra shield or an USB to RS-485 Adapter.
There is also a library to send/receive data using modbus-protocol:
http://libmodbus.org/
I want to install MATLAB and Simulink support package for Raspberry Pi. I follow this link to do . I directly connect my laptop with Raspberry Pi using Ethernat cable.
But i didn't get output.
while installing i got error - "Could not detect a Raspberry Pi board on "Local Area Connection". Check your Ethernet connection to Raspberry Pi.
The FDX/LNK/100 LEDs on the Raspberry Pi board should be illuminated.
For network trouble-shooting instructions see http://www.mathworks.com">The MathWorks Web Site"
Can anyone help to solve this problem?
I have also experienced your same issue but after proceeding in this way I solved it.
Before you put the SD card on the Raspberry Pi you need:
power off the Pi
connect the Ethernet cable to the host computer
finally power on the Pi
In addition you may take a look at this troubleshooting guide.
Try the following steps.
1. Open cmd and execute 'ipconfig'
check for a network interface with '169.x.x.x' ip address
If there is one, you could access your Pi via IP 169.254.0.2
If there is none, check if your Ethernet port is enabled and no static IP is configured.
The above steps make sure that your Ethernet port is in proper state.
Repeat the hardware setup with direct connection in the network settings.