i try to sending video stream. the source is jetson orin and the client is flutter web app.
i'm also want to store the data in db.
i'm look for recommendation which db,server,transfer data protocols to use for this task.
my stracture right now :
jetson AGX orin --> serialization to jeson string base64 → rabbitmq → server (node.js+express) → mongoDB → client (flutter)
Related
I am trying to connect Neo6 GPS module to Rpi3. I referred this link https://sparklers-the-makers.github.io/blog/robotics/use-neo-6m-module-with-raspberry-pi/, but I am unable to receive data from GPS module
.
I made sure serial is enabled with sudo raspi-config. but still it is not receiving data.
So I am trying to upload and encode file on azure media service. If the video format is MPEG-4 it uploads successfully, but if the format is MPEG-PS it fails.
Error Code:
ErrorExecutingTaskUnsupportedFormat
Error Message:
An error has occurred. Stage: AnalyzeInputMedia. Code: System.IO.InvalidDataException. System.IO.InvalidDataException: Failed to create MediaItem for blob-ea71728299ee44a5b9866e478292a2a0: Invalid data found when processing input!
I believe the mentioned exception is caused by the unsupported input file format. The official docs say only MPEG-TS is supported.
The input protocols supported by Live Encoding are: RTMP, RTP (MPEG
TS) and Smooth Streaming. You can send in a live feed where the video
is encoded with MPEG-2 (up to 422 Profile), or H.264...
The difference between MPEG-TS and MPEG-PS
MPEG-TS - transport stream for communication and broadcasting app,
MPEG-PS - used for storage application (DVD).
Simply, Azure Media Services supports only MPEG-TS containers.
Qs (1) Does Siddhi application support connecting to Kafka using SASL_SSL protocol with PLAIN as SASL Mechanism.
Qs (2) If not what SASL options are available. I am using WSO2 Streaming Processor 4.4.
Below is a simple program that's expected to read from a Kafka topic and write the content as is on server console.
Note-1: The connections establishes just fine (Deployment on worker node is also successful). But nothing reflected on console.
Note:2: The program runs just fine if connected to a non secure Kafka cluster (I remove the optional.configuration and change the bootstrap servers value appropriately)
#App:name("SKAppOne")
#source(
type='kafka',
topic.list='skapp1',
group.id='g1',
partition.no.list='0',
threading.option='single.thread',
bootstrap.servers='**KAFKABROKERIP:KAFKABROKERPORT**',
optional.configuration=
***"sasl.mechanism:PLAIN,security.protocol:SASL_SSL,***
sasl.jaas.config:org.apache.kafka.common.security.plain.PlainLoginModule required username='**validuserid**' password='**validpassword**';,
ssl.truststore.location:**validlocationfor_client.truststore.jks file**,
ssl.truststore.password:**validpassword**,
ssl.keystore.location:**validlocationfor_server.keystore.jks file**,
ssl.keystore.password:**validpassword**,
ssl.key.password:**validpassword**",
#map(type='json'))
define stream InputStreamFromSecureKafka (name string, location string);
#sink(type='log')
define stream SOutputStreamToConsole (name string, location string);
#info(name='kafkatosconsole')
from InputStreamFromSecureKafka
select *
insert into SOutputStreamToConsole;
I have a few TinkerForge sensors connected to a Raspberry Pi. I have humidity and barometer bricklets and almost everything is working fine. The only exception is for a single sensor: the Illuminance bricklet. For this there is no data sent to Cumulocity. The TinkerForge demo application works perfectly and displays luminosity values, so the sensor is producing data properly. But the Agent is not recognizing this sensor, or this type of sensor. The log contains the following warning:
Jun 17 15:12:51 raspberrypi root: 15:12:51.719 [Callback-Processor] WARN c8y.tinkerforge.Discoverer - Unsuported device identifier: 2131
Please advise.
Short answer: Some bricklets are just not supported.
I downloaded the source code for the Cumulocity Agent (written in Java) and I browsed through it and I found out that the Illuminance bricklet is not listed.
Until Cumulocity updates their agent, it just won't work.
If and when this happens, I will update this answer.
I would like to ask if it is possible to receive UDP or TCP packets instead of just the Physical layer by configuring the wifi_rx.grc 1 flow graph in GNU Radio.
wifi_rx.grc 1 is from the example in gr-ieee80211
I am using a LimeSDR-Mini as rx source
You can use the Wireshark Connector block to write the decoded frames in a PCAP file and inspect all layers with Wireshark/tcpdump/tshark just with like a normal WLAN card.
The flow graph you are referring to already contains these blocks albeit they are disabled by default. Click on them and click Enable in the context menu. Then run the flow graph and open the file in Wireshark. If you want live decoding you can write to a Linux pipe. See the rx_demo.sh script in the apps folder on how to do that.