This is the source of truth for stuff software needs to do.
Everything shall be fully manual. (No auto tasks in scope, except for gohome recovery)
-- Fourth Task: Heist Monday (sunday night)
Tonight at 9pm:
WHAT: Drive to the Camera Controls location given at the start of a task (in a map), in the dark, without being detected by "several" moving spotlights (moving in fixed patterns), nor tripping tripwires. We cannot shine visible light into these spotlights. Additionally, we cannot use ANY infrared. We do not know how much information will be on provided map.
Once at the location, we must cut a wire. The taskmaster shall tell us what wire to cut based on this doc.
Then, we must find a security console (WHERE???) with a flashing led. We will run @epw1624's code to read the morse code, which contains a password that we will write down. After, we must plug in an XLR connector using the arm. Once connected, we open a serial port that is emulating a "linux-like" terminal. We will log in with the password from the morse code. After we log in, we go into hacker mode to find the vault code. We don't currently have a plan for this.
After finding the vault code and writing it down, we use a morse code key (unser what this kinda looks like) to enter the code with a dit length of 66.7ms 18 words per minute. The vault probably still opens if we slowly enter the code, but we only get full points for quickly entering the code. Then, the door should unlock unsure if we get feedback on this (like a light turning on when it unlocks, and we will open the door by grabbing on a max 30mm handle, rotating it (unkown direction) and pulling on it to retreive the artifact. Then, we need to carry the artifact to the extraction point. then the task is complete
Whats working:
- We have location based camera enumertion. Other than fisheyes, TBD
FIRES:
- Comms base control. (WIRING)
- Drive control
- Flashback to a year ago, we had the dumb drivers. We have new aviators, but the improved control might be what fucked it.
- Cameras: Both Fisheye cameras have major attitude. ls in red ?? THey can disconnect. We might be able to restart it remotley but still have to unplug replug.
- Brightness is a fire, but we have some sort of fix.
- (small) stuttering of arm with analog input...
- A4 is a fire that we will not put out. 5DOF is working well rn.
- STARTUP.
- ROwans computer fucks up on the network to some extent. He does not want to run nodes via ssh on his computer, but can do minor
- Bandaid fix for accel on motors.
- Lighting (contingency: static on, and lose points from spotlights or try to avoid them)
TODODOOSS:
- No infrared. Either scrap realsense (noooo) or ensure they do not emit infrared.
- MOUNT ANTENNA HIGHHHHH no relay
- Charge keyboard and mouse
- Lighting
- plan for hacker mode _what linux commands should we run? _ Lets have a list ready, and like a logic tree of what to do (if we find env vars, do this, if we find something on dmesg, lets do that, etc)
Exactly what does the morse code key loook like? BUTTON- Mount ligthing board on end effector (Lochy Rishi weighing dev cost)
- lower timeout on motor_drive_node Increase vis
CRITICAL:
Network, Comms tower, Drive control, Control Base.
BASICALLY NO WORK TIME, WORK OR SLEEP
-- Fith Task: RoverCooked 7:50 - 9:15
YES :=>
This is the source of truth for stuff software needs to do.
Everything shall be fully manual. (No auto tasks in scope, except for gohome recovery)
-- Fourth Task: Heist Monday (sunday night)
Tonight at 9pm:
WHAT: Drive to the Camera Controls location given at the start of a task (in a map), in the dark, without being detected by "several" moving spotlights (moving in fixed patterns), nor tripping tripwires. We cannot shine visible light into these spotlights. Additionally, we cannot use ANY infrared. We do not know how much information will be on provided map.
Once at the location, we must cut a wire. The taskmaster shall tell us what wire to cut based on this doc.
Then, we must find a security console (WHERE???) with a flashing led. We will run @epw1624's code to read the morse code, which contains a password that we will write down. After, we must plug in an XLR connector using the arm. Once connected, we open a serial port that is emulating a "linux-like" terminal. We will log in with the password from the morse code. After we log in, we go into hacker mode to find the vault code. We don't currently have a plan for this.
After finding the vault code and writing it down, we use a morse code key (unser what this kinda looks like) to enter the code with a dit length of 66.7ms 18 words per minute. The vault probably still opens if we slowly enter the code, but we only get full points for quickly entering the code. Then, the door should unlock unsure if we get feedback on this (like a light turning on when it unlocks, and we will open the door by grabbing on a max 30mm handle, rotating it (unkown direction) and pulling on it to retreive the artifact. Then, we need to carry the artifact to the extraction point. then the task is complete
Whats working:
FIRES:
TODODOOSS:
Exactly what does the morse code key loook like?BUTTONCRITICAL:
Network, Comms tower, Drive control, Control Base.
BASICALLY NO WORK TIME, WORK OR SLEEP
-- Fith Task: RoverCooked 7:50 - 9:15
YES :=>