MakerGram Logo

    MakerGram

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Tags
    • Users
    • Groups

    Vehicle data retrieving

    Raspberry Pi
    iot raspberrypi nodemcu
    3
    10
    391
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Abhay
      Abhay last edited by

      Which will serve better for the purpose of data retrieving from vehicles, NodeMCU or Rasberry pi

      It is for the purpose of securing information via blockchain. (we want to store the retrived data using blockchain)

      1 Reply Last reply Reply Quote 0
      • kowshik1729
        kowshik1729 last edited by

        @Abhay can you please let us know what kind of vehicle data would you require?? Because there are very easy ways I can suggest if what parameters do you want to obtain from vehicles?

        And also let us know whether you are planning to require the data for cars???

        Abhay 1 Reply Last reply Reply Quote 1
        • salmanfaris
          salmanfaris last edited by salmanfaris

          Hi @Abhay ,

          I don't know what exactly your application is or what you are going to do with the data is ? if you want to read vehicle data you can use OBD-II CAN-BUS development kit. also for the esp vs raspberry pi decision is also depends upon what you are doing with the data.

          Abhay 1 Reply Last reply Reply Quote 2
          • Abhay
            Abhay @kowshik1729 last edited by

            @kowshik1729 accelerometer reading, gps location, airbag activation etc. Are the main reading were are looking at present. We are planing to collect it from car as a live demo and store it using blockchain.

            1 Reply Last reply Reply Quote 0
            • Abhay
              Abhay @salmanfaris last edited by

              @salmanfaris OBD devices are in every new cars right, I don't know if I am right but I think we need seperate android app to collect data using obd and i think it don't retrive accelerometer reading i guess.

              salmanfaris 1 Reply Last reply Reply Quote 0
              • salmanfaris
                salmanfaris @Abhay last edited by salmanfaris

                Hi @Abhay ,

                Yes, OBD interfaces are now available in most the cars these days , you can get the vehicle sensor data using the OBD interface and you can process it using any controller like esp8266 or something.

                Car => Data => OBD => Micorcontroller

                Abhay 1 Reply Last reply Reply Quote 1
                • Abhay
                  Abhay @salmanfaris last edited by

                  @salmanfaris don't we need seperate android apps for collecting those data.?

                  1 Reply Last reply Reply Quote 0
                  • kowshik1729
                    kowshik1729 last edited by

                    @Abhay As you mentioned, I strongly feel that, the infotainment systems inside the cars these days aren't serving data like GPS location and all. I have used the OBD(On-Board Diagnostics) module in order to acquire data like Fuel tank levels, acceleration of the car, Brake levels, Battery levels, etc., In order to acquire the data like GPS you can install your own GPS module like UBLOX GPS sensor which can be easily interfaced over UART of any MCU's like ESP8266, ESP32, Arduino etc., and pertaining to your last question in the thread I would say "NO" you don't need any separate android apps to obtain data from OBD devices(if they are Bluetooth enabled). Because OBD's like ELM327 is Bluetooth enabled and hence you can use a simple Bluetooth terminal app to connect and get the data.

                    Abhay 1 Reply Last reply Reply Quote 2
                    • Abhay
                      Abhay @kowshik1729 last edited by

                      Hi @kowshik1729
                      Thank you for the insight. Will definitely post further queries here as we progress on the project. Hope you could suggest answers like these again. Thank you

                      1 Reply Last reply Reply Quote 1
                      • kowshik1729
                        kowshik1729 last edited by

                        @Abhay Glad that it helped you. Yes, I can suggest you with the queries as far as I know. All the best..!!✌

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post

                        Recent Posts

                        • Testing Raspberry Pi's Camera Module 3 (NEW for 2023)

                          • read more
                        • 1666287f-258d-437d-b2c5-91851d08617c-image.png
                          The classic compact camera for Raspberry Pi with a 12MP sensor and autofocus

                          Available from $25 with your choice of standard and wide lenses, with or without an infrared filter

                          bf34763e-5ba3-4962-8e92-75583fd1e96c-image.png

                          More details: https://www.raspberrypi.com/products/camera-module-3/

                          Raspberry Pi Camera Module 3 - Autofocus cameras!

                          Resource:
                          Documentation: https://www.raspberrypi.com/documentation/accessories/camera.html
                          Camera Software: https://www.raspberrypi.com/documentation/computers/camera_software.html

                          • read more
                        • Hey @rafitc99 ,

                          Did your issue resolve? Curious to know 😊

                          • read more
                        • @rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:

                          host="MyRPiAPMode"
                          sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
                          sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
                          sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
                          sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
                          sudo nmcli radio wifi on
                          sudo nmcli con up $host

                          Hi @rafitc99, Are you able to set up the AP when trying the commands individually?

                          • read more
                        • I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.

                          Bash Script to set AP Mode

                          host="MyRPiAPMode" sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword" sudo nmcli radio wifi on sudo nmcli con up $host

                          Error ----

                          Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added. Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).

                          nmcli con (After script execution)

                          NAME UUID TYPE DEVICE Wired connection 1 9589ff1a-9923-3de3-a8a4-90b319661878 ethernet eth0 MyRPiAPMode 60965f2a-f510-48ef-afaf-0864242d0c06 wifi --

                          nmcli dev

                          DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi unavailable -- lo loopback unmanaged --

                          I tried to make it availble via sudo nmcli radio wifi on
                          But not working.

                          this is the log

                          -- Journal begins at Sat 2021-08-07 09:28:21 IST. -- Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info> [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success" Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info> [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success" Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))."

                          • read more
                        By MakerGram | A XiStart Initiative | Built with ♥ NodeBB
                        Copyright © 2021 MakerGram, All rights reserved.
                        Privacy Policy | Terms & Conditions | Disclaimer | Code of Conduct