We always require students to use the LiPo alarms. Would that be a good requirement?

Describe the bug
In 'getting_started/firmware/firmware_vesc.rst' line 59 (steps for enabling servo output). Users need to also click on 'Write App Configuration' (highlighted in the screenshot below) to enable servo output in the hardware. This instruction seems to be missed and needs to be added

Screenshots

1. Screenshot of current instructions on the f1tenth build documentation here

2. Screenshot from VESC tool 6.02 highlighting the 'Write App Configuration' button

I am using jetson orion nano development kit. I followed all the process as mentioned in the build section. I encountered a problem during "setting up the driver stack". As mentioned in the build process, I followed following commands:
cd $HOME/f1tenth_ws
rosdep update
rosdep install --from-paths src -i -y

But in the third line: "rosdep install --from-paths src -i -y" I got following error:
WARNING: ROS_PYTHON_VERSION is unset. Defaulting to 3
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies (ROS distro is not set. Make sure ROS_DISTRO environment variable is set, or use --rosdistro option to specify the distro, e.g. --rosdistro indigo):
vesc_driver: Cannot locate rosdep definition for [sensor_msgs]
teleop_tools: Cannot locate rosdep definition for [ament_cmake]
mouse_teleop: Cannot locate rosdep definition for [rclpy]
teleop_tools_msgs: Cannot locate rosdep definition for [action_msgs]
vesc_ackermann: Cannot locate rosdep definition for [tf2_ros]
vesc_msgs: Cannot locate rosdep definition for [geometry_msgs]
joy_teleop: Cannot locate rosdep definition for [rosidl_runtime_py]
ackermann_mux: Cannot locate rosdep definition for [diagnostic_updater]
key_teleop: Cannot locate rosdep definition for [rclpy]
f1tenth_stack: Cannot locate rosdep definition for [std_msgs]
vesc: Cannot locate rosdep definition for [ament_cmake_auto]

Can someone please help me?

UDEV Rules:

• Joystick is product id c21f instead of c219

Teleop

• When joystick is turned on, switch has to be in X and you have to hit mode once
• Edit f1tenth_system/racecar/racecar/config/racecar-v2/joy_teleop.yaml
  • Change teleop/human_control/axis_mappings/axis (the drive.steering_angle one) to 0 instead of 2
  • catkin_make workspace

Describe the bug
The Master BOM Google Spreadsheet is not available in bom.rst.
https://docs.google.com/spreadsheets/d/1ykUyrZq-vLlMTf0TIcdMrRbGKcRWglW6ol76QyGst2I/edit#gid=2038095912
Access denied.

To Reproduce
Steps to reproduce the behavior:

1. Go to f1tenth_doc/getting_started/build_car/bom.rst
2. Click on Master BOM link

Expected behavior
It should show a Google Spreadsheet.
But it says that the organization that owns this item does not allow you to access it.

Describe the bug
A clear and concise description of what the bug is.
Addition to the VESC HW V4.12 instructions

"
VESC out of sync errors: Check that the VESC is connected. If the error persists, make sure you’re using the right VESC driver node. Currently, the vesc package in the f110_system repo only supports VESC 6+. If you have an older implementation of VESC (for example the FOCBox), use the repo here instead.
"
One needs to indicate the firmware needed to be compatible with the MIT vesc_driver. The driver expects firmware 2.18. But it will not work with the VESC Tools you have on the F1/10 instructions.

See proposed solution below.

To Reproduce
Steps to reproduce the behavior:
VESC HW4.12.
At this point I am using VESC Tool V2.03. It supplies the latest firmware that I could find that has VESC_servoout.bin. As of 28Apr20, the latest VESC Tool is 2.05. It has firmware 5.1. I don’t see vesc_servoout.bin available with it...

I uploaded firmware V4.2 VESC_servoout.bin to the VESC HW 4.12
The BLDC sensored motor was detected without problems.

Need to use this repository to build the vesc_driver into the ROS
This is how you can do it. Adjust your paths accordingly
ssh to the jetson

cd ~/projects/f110/f110_ws/src/f110_system
rm -rf vesc
git clone https://github.com/erwincoumans/vesc
cd ~/projects/f110/f110_ws
catkin_make
source devel/setup.bash

No errors during the catkin_make ...
That is all.

A quick test with your robot framework with the joystick should do it
ex using F1/10. On a terminal tab

source devel/setup.bash
roscore

Another terminal tab
roslaunch racecar teleop.launch

I had to adjust the axis of my joystick
~/projects/f110/f110_ws/src/f110_system/racecar/racecar/config/racecar-v2/joy_teleop.yaml

I changed the axis to map the jstest I ran

axis: 4 target: drive.speed
axis: 0 target: drive.steering_angle

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Currently trying to use a Hokuyo Lidar (10-lx) connect over ethernet to the Jetson Tx2 and Wifi for ssh & internet simultaneously. However, I'm only able to get one working at a time. The ideal setup is to have both my dev laptop and racecar connected to 1 router which has a passthrough into the internet, so I can have web access on both.

Here is more info on this issue: https://forums.developer.nvidia.com/t/how-to-set-wlan0-and-eth0-to-work-simutaneously-for-hokuyo-lidar/43434

The linked thread is long but one of the listed solutions is someone using a Picostation route of getting a AP hotspot, and they listed the settings they used.

I've been messing with this for a long time, I also tried the f1 tenth instruction for setting up the hotspot but it didn't work, I couldn't get my laptop to connect when the lidar was plugged in.

Thanks!

re: Approximate Time Investment: 5-7 hours at the introduction page.

I would imagine it will take more than 7 hours for someone to build the car, configure the software on the host and target, and start to drive the robot.
How about we have some new fresh people try the process from start to end and then get the typical build time listed.

Thank you,
-Jack (UC San Diego)

Describe the bug

Documentation - 2. Driving Car

Additional context
Add any other context about the problem here.

should be <catkin_make>, no? It missing "_".
I hope this help.

"
Navigate to other free terminal using Ctrl-B and then P or N by switch to previous or next session, or using Ctrl-B and then the number of the session, navigate to your workspace that we set up before, run $ catkin make and source the directory using

Describe the bug
The discourse group link provided on the build documentation (https://f1tenth.readthedocs.io/en/foxy_test/) is broken - https://f1tenth.discourse.group/

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://f1tenth.readthedocs.io/en/foxy_test/'
2. Click on 'https://f1tenth.discourse.group/'
3. page no found error

Expected behavior
The discourse link should work

After discussion with @JohannesBetz, it probably makes sense to have two configuration paths in the docs: one for the TX2 board and one for the NX board. Here is my suggestion for the new page layout:

• Introduction
• Building the Car
  • Bill of Materials (stays the same)
  1. Lower-Level Chassis (stays the same)
  2. Computing Hardware
     • NVIDIA Jetson TX2
     • NVIDIA Jetson Xavier NX
  3. Upper-Level Chassis
     1. Mounting the VESC and the Powerboard (modified to include both versions of the powerboard)
     2. Mounting the Computing Hardware
        • NVIDIA Jetson TX2 (include USB Hub instructions here)
        • NVIDIA Jetson Xavier NX
     3. Mounting and Connecting the Lidar
     4. Putting It All Together (stays the same)
• System Configuration
  • NVIDIA Jetson TX2
    1. Pit/Host Steup
    2. Configuring the TX2
    3. Connecting the Pot/Host and the TX2
    4. Advanced Setup
  • NVIDIA Jetson Xavier NX
    1. Pit/Host Steup
    2. Configuring the Xavier NX
    3. Advanced Setup
  1. Installing ROS and the F1TENTH Stack

(The rest is mostly un-changed)

I have two f1tenth cars. On both of them, I followed the same steps as described in the f1tenth website. Whenever I try to drive a car manually, both of them get commands from the same joystick. I have connected both cars to different joysticks but still, both act at the same time when only one joystick is used. Do I need to change anything? Both of them are connected to the same local wifi and use "no machine". When I turn off the wifi, then only they both ack separately.

The BOM contains a typo for the Intel RealSense camera. The text references a d345i, but the link points to the d435. Since I don't think a d345i exists, I assume the text is a typo.

https://f1tenth.readthedocs.io/en/latest/getting_started/build_car/all_together.html#connecting-the-brushless-motor-to-the-vesc

Should be 4mm to 3.5mm, not 3 to 3.5mm.

I have missed on the instruction the initial ROS install

You might need to install some additional ROS packages.

For ROS Kinetic:

$​ sudo apt-get update
$​ sudo apt-get install ros-kinetic-driver-base

I hope this helps.
Thanks
Jack

Assuming ROS was not installed yet:

sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'
sudo apt-key adv --keyserver 'hkp://keyserver.ubuntu.com:80' --recv-key C1CF6E31E6BADE8868B172B4F42ED6FBAB17C654
sudo apt-get update
sudo apt-get install ros-melodic-driver-base

How about adding links to the parts where one can order these?
Amazon, hobby stores, McMaster-Carr...

Thanks,
-Jack

Describe the bug
A clear and concise description of what the bug is.
I just downloaded the latest VESC Tool - 2.05
I can't find the option for the VESC_servoout.bin anymore.
Yes, I have the Show non-default firmwares selected. Done this few times before.
They may have stopped supporting VESC_servoout.bin on latest firmware (5.1) or they have not released the VESC_servoout.bin yet for 5.1 yet.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
   Install the latest VESC Tools, connect to the VESC, select Show non-default firmwares, try to find VESC_servoout.bin.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Currently trying to use a Hokuyo Lidar (10-lx) connect over ethernet to the Jetson Tx2 and Wifi for ssh & internet simultaneously. However, I'm only able to get one working at a time. The ideal setup is to have both my dev laptop and racecar connected to 1 router which has a passthrough into the internet, so I can have web access on both.

Here is more info on this issue: https://forums.developer.nvidia.com/t/how-to-set-wlan0-and-eth0-to-work-simutaneously-for-hokuyo-lidar/43434

The linked thread is long but one of the listed solutions is someone using a Picostation route of getting a AP hotspot, and they listed the settings they used.

I've been messing with this for a long time, I also tried the f1 tenth instruction for setting up the hotspot but it didn't work, I couldn't get my laptop to connect when the lidar was plugged in.

Thanks!

Suggestion

Between [1] and [2]

check if the TX2 shows in the USB devices. Otherwise, don't go to [2] because it wont work

lsusb

Bus 001 Device 020: ID 0955:7020 NVidia Corp.

2. On the Pit/Host computer manually flash the boards by typing the following into the terminal

Describe the bug
Document link seems to be broken

To Reproduce
Steps to reproduce the behavior:

1. Go to
   https://f1tenth.readthedocs.io/en/latest/getting_started/firmware/firmware_vesc.html?highlight=VESC

2. Installing the VESC Tool
   We need to configure the VESC so that it works with the ROS driver package. Before you start, you’ll need to install the VESC Tool v2.03. The latest version, v2.05 does not contain the firmware that we use. The Linux VESC tool v2.03 can be found here.

3. Click on '....'
   The Linux VESC tool v2.03 can be found here.

4. Scroll down to '....'

5. See error
   Sorry, the file you have requested does not exist.

Make sure that you have the correct URL and the file exists.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hello,
I would like to ask if I could use AGX instead of Jetson NX? AGX is available to me, NX is not. And now the delivery time is extremely long.
Hokuyo Lidar also has a lot of delivery time, maybe there are other supported options?
Thanks

Something is confusing in this step :

https://f1tenth.readthedocs.io/en/latest/getting_started/firmware/firmware_vesc.html#doc-firmware-vesc

the point is we have VESC HARDWARE both v4 and v6 and v6 mkIII and ...
in the text it is mentioned the firmware is for vesc v 4.12 hardware but the photo is showing vesc v6 MkIII !

Hello,

I'm using the Logitech GamePad F710 in Direct Input Mode as per the docs, however it doesn't seem to be working properly. I'm also receiving the force feedback error which means the controller is connected. When I run sudo jstest /dev/input/js0 it shows the controller is connected but isn't registering any controller inputs/feedback. I've looked online and it looks like the solution may involve something with a configuration file or extra compiling.

Here is the post I found online, but I'm still not sure how to fix the issue: https://forums.developer.nvidia.com/t/no-data-being-updated-from-joystick-in-o-p-of-sudo-jstest-dev-input-js0-solved/65985

Thank you!