Others Extensions - Revision history

WikiSysop: /* Assembly */

2026-04-22T12:47:53Z

Assembly

← Older revision		Revision as of 12:47, 22 April 2026
Line 102:		Line 102:

	==Assembly==		==Assembly==
	<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3]</td><td align="center">[4.1]</td><td align="center">[4.2]</td></tr><tr><td>[[File:cliff-mounting-1.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-2.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-3.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-4-1.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-4-2.jpg\|~~200px~~]]</td></tr><tr><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[6]</td><td align="center">[7]</td><td align="center">[8]</td></tr><tr><td>[[File:cliff-mounting-5-1.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-5-2.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-6.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-7.jpg\|~~200px~~]]</td><td>[[File:cliff-mounting-8.jpg\|~~200px~~]]</td></tr></table></span>		<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3]</td><td align="center">[4.1]</td><td align="center">[4.2]</td></tr><tr><td>[[File:cliff-mounting-1.jpg\|x200px]]</td><td>[[File:cliff-mounting-2.jpg\|x200px]]</td><td>[[File:cliff-mounting-3.jpg\|x200px]]</td><td>[[File:cliff-mounting-4-1.jpg\|x200px]]</td><td>[[File:cliff-mounting-4-2.jpg\|x200px]]</td></tr><tr><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[6]</td><td align="center">[7]</td><td align="center">[8]</td></tr><tr><td>[[File:cliff-mounting-5-1.jpg\|x200px]]</td><td>[[File:cliff-mounting-5-2.jpg\|x200px]]</td><td>[[File:cliff-mounting-6.jpg\|x200px]]</td><td>[[File:cliff-mounting-7.jpg\|x200px]]</td><td>[[File:cliff-mounting-8.jpg\|x200px]]</td></tr></table></span>
	# Unscrew the 3 screws, unmount the e-jumper (top piece where there is the speaker) and unscrew the 3 spacers		# Unscrew the 3 screws, unmount the e-jumper (top piece where there is the speaker) and unscrew the 3 spacers
	# Remove the pcb from the case body gently		# Remove the pcb from the case body gently

WikiSysop: /* Assembly for e-puck2 */

2026-04-22T12:46:47Z

Assembly for e-puck2

← Older revision		Revision as of 12:46, 22 April 2026
Line 90:		Line 90:

	==Assembly for e-puck2==		==Assembly for e-puck2==
	<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3.1]</td><td align="center">[3.2]</td><td align="center">[3.3]</td><td align="center">[3.4]</td></tr><tr><td align="center">[[File:ground-assembly-1.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-2.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-3.1.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-3.2.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-3.3.~~png~~\|~~200px~~]][[File:ground-assembly-3.4.~~png~~\|~~200px~~]]</td><td align="center">[[File:ground-assembly-3.5.png\|~~200px~~]]</td></tr><tr><td align="center">[4]</td><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[5.3]</td><td align="center">[5.4]</td><td align="center">[6]</td></tr><tr><td align="center">[[File:ground-assembly-4.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-5.1.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-5.2.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-5.3.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-5.4.png\|~~200px~~]]</td><td align="center">[[File:ground-assembly-6.png\|~~200px~~]]</td></tr></table></span>		<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3.1]</td><td align="center">[3.2]</td><td align="center">[3.3]</td><td align="center">[3.4]</td></tr><tr><td align="center">[[File:ground-assembly-1.png\|x200px]]</td><td align="center">[[File:ground-assembly-2.png\|x200px]]</td><td align="center">[[File:ground-assembly-3.1.png\|x200px]]</td><td align="center">[[File:ground-assembly-3.2.png\|x200px]]</td><td align="center">[[File:ground-assembly-3.3.jpeg\|x200px]][[File:ground-assembly-3.4.jpeg\|x200px]]</td><td align="center">[[File:ground-assembly-3.5.png\|x200px]]</td></tr><tr><td align="center">[4]</td><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[5.3]</td><td align="center">[5.4]</td><td align="center">[6]</td></tr><tr><td align="center">[[File:ground-assembly-4.png\|x200px]]</td><td align="center">[[File:ground-assembly-5.1.png\|x200px]]</td><td align="center">[[File:ground-assembly-5.2.png\|x200px]]</td><td align="center">[[File:ground-assembly-5.3.png\|x200px]]</td><td align="center">[[File:ground-assembly-5.4.png\|x200px]]</td><td align="center">[[File:ground-assembly-6.png\|x200px]]</td></tr></table></span>
	# Unscrew the 3 spacers and remove the battery.		# Unscrew the 3 spacers and remove the battery.
	# Remove the top side from the case body gently.		# Remove the top side from the case body gently.

WikiSysop: /* Range and bearing */

2026-04-22T12:44:23Z

Range and bearing

← Older revision		Revision as of 12:44, 22 April 2026
Line 1:		Line 1:
	=Range and bearing=		=Range and bearing=
	[[File:randb-1.jpg\|~~150px~~]] [[File:randb-2.jpg\|~~150px~~]]<br/>		[[File:randb-1.jpg\|x150px]] [[File:randb-2.jpg\|x150px]]<br/>
	The board allows situated agents to communicate locally, obtaining at the same time both the range and the bearing of the emitter without the need of any centralized control or any external reference. Therefore, the board allows the robots to have an embodied, decentralized and scalable communication system. The system relies on infrared communications with frequency modulation and is composed of two interconnected modules for data and power measurement.<br/>		The board allows situated agents to communicate locally, obtaining at the same time both the range and the bearing of the emitter without the need of any centralized control or any external reference. Therefore, the board allows the robots to have an embodied, decentralized and scalable communication system. The system relies on infrared communications with frequency modulation and is composed of two interconnected modules for data and power measurement.<br/>

WikiSysop at 12:44, 22 April 2026

2026-04-22T12:44:02Z

← Older revision		Revision as of 12:44, 22 April 2026
Line 1:		Line 1:
	=Range and bearing=		=Range and bearing=
	~~<span class="plainlinks">~~[~~https~~:~~//www.gctronic.com/doc/images/~~randb-1~~-small~~.jpg ~~<img height=150 src="https://www.gctronic.com/doc/images/randb-1.jpg">~~][~~https~~:~~//www.gctronic.com/doc/images/~~randb-2~~-small~~.jpg ~~<img height=150 src="https://www.gctronic.com/doc/images/randb-2.jpg">~~]~~</span>~~<br/>		[[File:randb-1.jpg\|150px]] [[File:randb-2.jpg\|150px]]<br/>
	The board allows situated agents to communicate locally, obtaining at the same time both the range and the bearing of the emitter without the need of any centralized control or any external reference. Therefore, the board allows the robots to have an embodied, decentralized and scalable communication system. The system relies on infrared communications with frequency modulation and is composed of two interconnected modules for data and power measurement.<br/>		The board allows situated agents to communicate locally, obtaining at the same time both the range and the bearing of the emitter without the need of any centralized control or any external reference. Therefore, the board allows the robots to have an embodied, decentralized and scalable communication system. The system relies on infrared communications with frequency modulation and is composed of two interconnected modules for data and power measurement.<br/>

Line 77:		Line 77:

	=Ground sensors=		=Ground sensors=
	~~<span class="plainlinks">~~[~~https~~:~~//www.gctronic.com/doc/images/~~E-puck-groundsensors.jpg ~~<img width=200 src="https://www.gctronic.com/doc/images/E-puck-groundsensors.jpg">~~]</~~span~~>		[[File:E-puck-groundsensors.jpg\|200px]]<br/>

	The factory firmware of both the e-puck1 and e-puck2 supports the ground sensors extension: for e-puck1 refer to the section [https://www.gctronic.com/doc/index.php?title=E-Puck#Standard_firmware Standard firmware], for e-puck2 refer to section [https://www.gctronic.com/doc/index.php?title=e-puck2#Factory_firmware Factory firmware].		The factory firmware of both the e-puck1 and e-puck2 supports the ground sensors extension: for e-puck1 refer to the section [https://www.gctronic.com/doc/index.php?title=E-Puck#Standard_firmware Standard firmware], for e-puck2 refer to section [https://www.gctronic.com/doc/index.php?title=e-puck2#Factory_firmware Factory firmware].
Line 90:		Line 90:

	==Assembly for e-puck2==		==Assembly for e-puck2==
	<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3.1]</td><td align="center">[3.2]</td><td align="center">[3.3]</td><td align="center">[3.4]</td></tr><tr><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-1.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-1_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-2.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-2_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-3.1.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-3.1_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-3.2.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-3.2.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-3.3.~~jpeg <img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-3.3_small.jpeg">~~][~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-3.4.~~jpeg <img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-3.4_small.jpeg">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-3.5.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-3.5.png">~~]</td></tr><tr><td align="center">[4]</td><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[5.3]</td><td align="center">[5.4]</td><td align="center">[6]</td></tr><tr><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-4.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-4_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-5.1.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-5.1_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-5.2.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-5.2_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-5.3.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-5.3_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-5.4.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-5.4_small.png">~~]</td><td align="center">[~~https~~:~~//projects.gctronic.com/epuck2/wiki_images/~~ground-assembly-6.png ~~<img height=200 src="https://projects.gctronic.com/epuck2/wiki_images/ground-assembly-6_small.png">~~]</td></tr></table></span>		<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3.1]</td><td align="center">[3.2]</td><td align="center">[3.3]</td><td align="center">[3.4]</td></tr><tr><td align="center">[[File:ground-assembly-1.png\|200px]]</td><td align="center">[[File:ground-assembly-2.png\|200px]]</td><td align="center">[[File:ground-assembly-3.1.png\|200px]]</td><td align="center">[[File:ground-assembly-3.2.png\|200px]]</td><td align="center">[[File:ground-assembly-3.3.png\|200px]][[File:ground-assembly-3.4.png\|200px]]</td><td align="center">[[File:ground-assembly-3.5.png\|200px]]</td></tr><tr><td align="center">[4]</td><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[5.3]</td><td align="center">[5.4]</td><td align="center">[6]</td></tr><tr><td align="center">[[File:ground-assembly-4.png\|200px]]</td><td align="center">[[File:ground-assembly-5.1.png\|200px]]</td><td align="center">[[File:ground-assembly-5.2.png\|200px]]</td><td align="center">[[File:ground-assembly-5.3.png\|200px]]</td><td align="center">[[File:ground-assembly-5.4.png\|200px]]</td><td align="center">[[File:ground-assembly-6.png\|200px]]</td></tr></table></span>
	# Unscrew the 3 spacers and remove the battery.		# Unscrew the 3 spacers and remove the battery.
	# Remove the top side from the case body gently.		# Remove the top side from the case body gently.
Line 102:		Line 102:

	==Assembly==		==Assembly==
	<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3]</td><td align="center">[4.1]</td><td align="center">[4.2]</td></tr><tr><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-1.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-1-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-2.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-2-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-3.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-3-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-4-1.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-4-1-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-4-2.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-4-2-small.jpg">~~]</td></tr><tr><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[6]</td><td align="center">[7]</td><td align="center">[8]</td></tr><tr><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-5-1.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-5-1-small.jpg">~~]</td><td>[~~https://www.gctronic.com/doc/images/cliff-mounting-5-2.jpg <img height=200 src="https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-5-2~~-small~~.jpg">]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-6.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-6-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-7.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-7-small.jpg">~~]</td><td>[~~https~~:~~//www.gctronic.com/doc/images/~~cliff-mounting-8.jpg ~~<img height=200 src="https://www.gctronic.com/doc/images/cliff-mounting-8-small.jpg">~~]</td></tr></table></span>		<span class="plainlinks"><table><tr><td align="center">[1]</td><td align="center">[2]</td><td align="center">[3]</td><td align="center">[4.1]</td><td align="center">[4.2]</td></tr><tr><td>[[File:cliff-mounting-1.jpg\|200px]]</td><td>[[File:cliff-mounting-2.jpg\|200px]]</td><td>[[File:cliff-mounting-3.jpg\|200px]]</td><td>[[File:cliff-mounting-4-1.jpg\|200px]]</td><td>[[File:cliff-mounting-4-2.jpg\|200px]]</td></tr><tr><td align="center">[5.1]</td><td align="center">[5.2]</td><td align="center">[6]</td><td align="center">[7]</td><td align="center">[8]</td></tr><tr><td>[[File:cliff-mounting-5-1.jpg\|200px]]</td><td>[[File:cliff-mounting-5-2.jpg\|200px]]</td><td>[[File:cliff-mounting-6.jpg\|200px]]</td><td>[[File:cliff-mounting-7.jpg\|200px]]</td><td>[[File:cliff-mounting-8.jpg\|200px]]</td></tr></table></span>
	# Unscrew the 3 screws, unmount the e-jumper (top piece where there is the speaker) and unscrew the 3 spacers		# Unscrew the 3 screws, unmount the e-jumper (top piece where there is the speaker) and unscrew the 3 spacers
	# Remove the pcb from the case body gently		# Remove the pcb from the case body gently
Line 155:		Line 155:
	==Images==		==Images==
	Robot equipped with the cliff sensor: <br/>		Robot equipped with the cliff sensor: <br/>
	~~<span class="plainlinks">~~[~~https~~:~~//www.gctronic.com/doc/images/~~Cliff+charger.jpg ~~<img width=300 src="https://www.gctronic.com/doc/images/Cliff+charger.jpg">~~]~~</span>~~ <br/>		[[File:Cliff+charger.jpg\|300px]]<br/>

	The robot can be easily moved to the charging station as shown in the following figure: <br/>		The robot can be easily moved to the charging station as shown in the following figure: <br/>
	~~<span class="plainlinks">~~[~~https~~:~~//www.gctronic.com/doc/images/~~Cliff-charging.jpg ~~<img width=300 src="https://www.gctronic.com/doc/images/Cliff-charging.jpg">~~]~~</span>~~ <br/>		[[File:Cliff-charging.jpg\|300px]]<br/>

	The following figure shows the two additional sensors (near the wheels) mounted on the cliff module and the three frontal sensors of the ground module: <br/>		The following figure shows the two additional sensors (near the wheels) mounted on the cliff module and the three frontal sensors of the ground module: <br/>
	~~<span class="plainlinks">~~[~~https~~:~~//www.gctronic.com/doc/images/~~Cliff-zoom.jpg ~~<img width=300 src="https://www.gctronic.com/doc/images/Cliff-zoom.jpg">~~]~~</span>~~ <br/>		[[File:Cliff-zoom.jpg\|300px]]<br/>

	==Videos==		==Videos==
	{{#ev:youtube\|7iFmLBng3qg}}		{{#ev:youtube\|7iFmLBng3qg}}
	{{#ev:youtube\|NYOcb1QoUTM}}		{{#ev:youtube\|NYOcb1QoUTM}}

WikiSysop: /* Range and bearing */

2023-04-26T05:48:12Z

Range and bearing

← Older revision		Revision as of 05:48, 26 April 2023
Line 43:		Line 43:
	\|12 \|\| - \|\| Set transmission power (communication range): between 0 (max range) and 255 (min range)		\|12 \|\| - \|\| Set transmission power (communication range): between 0 (max range) and 255 (min range)
	\|-		\|-
	\|13 \|\| - \|\| data ~~LSB~~ (prepare)		\|13 \|\| - \|\| data MSB (prepare)
	\|-		\|-
	\|14 \|\| - \|\| data ~~MSB~~ (send <code>(MSB<<8)+LSB</code>)		\|14 \|\| - \|\| data LSB (send <code>(MSB<<8)+LSB</code>)
	\|-		\|-
	\|16 \|\| - \|\| 0 store light conditions (calibration)		\|16 \|\| - \|\| 0 store light conditions (calibration)

WikiSysop: /* Range and bearing */

2023-03-23T14:59:14Z

Range and bearing

← Older revision		Revision as of 14:59, 23 March 2023
Line 49:		Line 49:
	\|16 \|\| - \|\| 0 store light conditions (calibration)		\|16 \|\| - \|\| 0 store light conditions (calibration)
	\|-		\|-
	\|17 \|\| - \|\| 1=onboard calculation, 0=host calculation		\|17 \|\| - \|\| 0=onboard calculation, 1=host calculation
	\|-		\|-
	\|}		\|}

WikiSysop: /* e-puck 2 */

2023-03-17T14:15:50Z

e-puck 2

← Older revision		Revision as of 14:15, 17 March 2023
Line 71:		Line 71:
	The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>		The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>

	It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing extension; you can use it in your application if you want but you need to take in consideration this side effect.<br/>		It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid (infrared) interference with the front sensors of the range and bearing extension; you can use it in your application if you want but you need to take in consideration this side effect.<br/>
	Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>		Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>

WikiSysop: /* e-puck 2 */

2023-03-17T14:12:26Z

e-puck 2

← Older revision		Revision as of 14:12, 17 March 2023
Line 71:		Line 71:
	The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>		The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>

	It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing; you can use it in your application if you want but you need to take in consideration this side effect.<br/>		It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing extension; you can use it in your application if you want but you need to take in consideration this side effect.<br/>
	Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>		Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>

WikiSysop: /* e-puck 2 */

2023-03-17T14:12:04Z

e-puck 2

← Older revision		Revision as of 14:12, 17 March 2023
Line 70:		Line 70:
	==e-puck 2==		==e-puck 2==
	The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>		The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>

	It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing; you can use it in your application if you want but you need to take in consideration this side effect.<br/>		It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing; you can use it in your application if you want but you need to take in consideration this side effect.<br/>
	Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>		Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>

	Beware that the only communication channel available between the robot and the range and bearing extension is the I2C bus, the UART channel is not available with e-puck 2.		Beware that the only communication channel available between the robot and the range and bearing extension is the I2C bus, the UART channel is not available with e-puck 2.

WikiSysop: /* e-puck 2 */

2023-03-17T14:11:29Z

e-puck 2

← Older revision		Revision as of 14:11, 17 March 2023
Line 69:		Line 69:

	==e-puck 2==		==e-puck 2==
	The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver, when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth.<br/>		The e-puck2 standard firmware contains examples usages of the range and bearing extension. When the selector is in position 4 then the robot is set to be a receiver or a transmitter (you can switch between roles using the small button on the back of the robot), when in position 5 then the robot is both transmitter and receiver at the same time. In both demos the information received (data received, bearing, distance and sensor id) will be printed via Bluetooth and USB.<br/>
			It's important to notice that in both these demos the time of flight sensor is disabled in order to avoid interference with the front sensors of the range and bearing; you can use it in your application if you want but you need to take in consideration this side effect.<br/>
			Moreover also the proximity sensors of the robot interfere with the range and bearing communication, so you have some options to increase communication distance and throughput: first of all if you don't need the proximities you can simply disable them, otherwise you can set a slower proximity sampling frequency and disable the proximity sampling during transmission of a message. The latter option is implemented in the demo 5.<br/>
	Beware that the only communication channel available between the robot and the range and bearing extension is the I2C bus, the UART channel is not available with e-puck 2.		Beware that the only communication channel available between the robot and the range and bearing extension is the I2C bus, the UART channel is not available with e-puck 2.