S22: Firebolt - Revision history

243 user1: /* Team Members & Responsibilities */

2022-06-11T06:54:38Z

‎Team Members & Responsibilities

2022-05-29T08:12:46Z

‎DBC File

2022-05-29T08:11:51Z

‎Team Members & Responsibilities

2022-05-28T22:08:55Z

‎Advise for Future Students

2022-05-28T22:06:48Z

‎Advise for Future Students

2022-05-28T22:05:35Z

2022-05-28T22:04:47Z

2022-05-28T20:00:55Z

‎Bluetooth Block

2022-05-28T20:00:47Z

‎Map and Marker Blocks

2022-05-28T20:00:33Z

‎Bluetooth

@@ Line 39: / Line 39: @@
 <font color="black"> '''Priyanka Rai   [https://www.linkedin.com/in/priyanka-rai-009ba975/  LinkedIn]''''''
 *  Geo Controller
 *  GPS and Compass Interfacing
 *  Integration Testing
 *  Wiki Page Update
@@ Line 53: / Line 52: @@
 *  Driver Node
 *  LCD interfacing
 *  Integration Testing
 *  Wiki Page Update

@@ Line 580: / Line 580: @@
 |-
 |2
-|101
+|200
 |Sensor sonars from front, back, left ,right sensor
 |Driver

@@ Line 40: / Line 40: @@
 *  Geo Controller
 *  GPS and Compass Interfacing
 *  Integration Testing
 *  Wiki Page Update
@@ Line 52: / Line 53: @@
 *  Driver Node
 *  LCD interfacing
 *  Integration Testing
 *  Wiki Page Update

@@ Line 1,446: / Line 1,446: @@
 *Make sure to get a power supply which gives a steady 5V and 1A current so you don't lose boards due to sudden power surge. When all the car's subsystems are running, the current draw may be higher than expected. Make sure to have a common ground for all the components related to a single ECU.
 *The most critical hardware connection is for motor node. We used the receiver , which we used to calibrate the ESC for Servo, DC and RPM power supply. We did that 1 week before our demo, and the motor node was fine.
-* Do not overlook any software bug or hardware connection, It can cost you very badly. Be responsible for your node to send reliable data on bus.
+* Can Transceiver: Our CAN bus data was not coming on Bus Master but every node was receiving the data, we were using same module which previous groups used. Later we found out the termination was the problem. Each Can transceiver had 120 ohm resistor. Debugging without Bus Master was a nightmare.
 * It is always better to buy new and quality components. The RC Car performance depends on what components you are using. The better and reliable components makes your life easier.

@@ Line 1,442: / Line 1,442: @@
 === Advise for Future Students ===
 * Get started early and make your hardware stable as early as possible so that you have enough time for extensive testing of the software. Because without on field testing corner cases and potential problems in the code can't be determined.
-* Make use of the holidays and spring break. If you have your basic framework of the software and hardware is complete by the end of spring break you can start testing ASAP.
+* Make use of the holidays and spring break. If you have your basic framework of the software and hardware completed by the end of spring break you can start testing ASAP.
 * Start researching as soon as possible and collect all the information related to the module that has been assigned to you, as there is no single book or manual to refer to. Go through all the problems faced by previous teams as they are a treasure trove of information. If you are facing a problem, it is very likely that some team in previous semesters has faced it. It will save you some precious days.
 *Make sure to get a power supply which gives a steady 5V and 1A current so you don't lose boards due to sudden power surge. When all the car's subsystems are running, the current draw may be higher than expected. Make sure to have a common ground for all the components related to a single ECU.

← Older revision		Revision as of 22:05, 28 May 2022
Line 1:		Line 1:
−	[[File:~~Firebolt~~.jpeg\|500px\|thumb\|right\| The RC Car]]	+	[[File:Firebolt2.jpeg\|500px\|thumb\|right\| The RC Car]]

	== Abstract ==		== Abstract ==

← Older revision		Revision as of 22:04, 28 May 2022
Line 1:		Line 1:
−	[[File:~~First_Image~~.~~JPG~~\|500px\|thumb\|right\| The RC Car]]	+	[[File:Firebolt.jpeg\|500px\|thumb\|right\| The RC Car]]

	== Abstract ==		== Abstract ==

@@ Line 1,375: / Line 1,375: @@
 <br/>
-== Bluetooth Block ==
+=== Bluetooth Block ===
 The firebolt app uses the bluetooth client block to establish a connection with the HC-05 bluetooth module onboard the car. It is necessary to establish connection and connect to a bluetooth pair to send and receive messages.

@@ Line 1,382: / Line 1,382: @@
 <br/>
-== Map and Marker Blocks ==
+=== Map and Marker Blocks ===
 The map block is used to create and display a 2D map of the world for location, navigation and other map functions. It uses an open-source map library which is very similar to Google Maps. The Map bloc has several functions including display, zoom, direction, distance, coordinate calculation. Fireblot uses this block to locate a destination location for the car and send the corresponding latitude and longitude values. This is made possible by the marker block. Markers can be placed on any location on the map and the pinpointed location coordinates can be received as floating point integers. These values are displayed on the app and also used to send as a bluetooth message to the HC-05 module when required.
@@ Line 1,391: / Line 1,391: @@
 MIT App inventor projects can be accessed for testing on the MIT AI companion app or built into a downloadable APK file. It can also be exported as a file to be later imported. The file extension for an app inventor project is “.aia”.
 ==Bluetooth==

← Older revision		Revision as of 20:00, 28 May 2022
Line 1,393:		Line 1,393:


−	===Bluetooth===	+	==Bluetooth==

	Gitlab link: https://gitlab.com/Ritika_Beniwal_/firebolt/-/tree/Bluetooth_and_app		Gitlab link: https://gitlab.com/Ritika_Beniwal_/firebolt/-/tree/Bluetooth_and_app