Add rough random movements... WIP?

3096 · 3096 · commit 2e2796e4e9ac · 2018-04-08T04:42:28.000-07:00
diff --git a/Joystick.c b/Joystick.c
@@ -148,6 +148,7 @@ void HID_Task(void)
 
 typedef enum {
 	SYNC_CONTROLLER,
+	BOOYAH,
 	SYNC_POSITION,
 	ZIG_ZAG,
 	MOVE,
@@ -239,6 +240,8 @@ void complete_zig_zag_pattern(USB_JoystickReport_Input_t *const ReportData)
 	return;
 }
 
+bool moving_left = true;
+
 // Prepare the next report for the host
 void GetNextReport(USB_JoystickReport_Input_t *const ReportData)
 {
@@ -281,7 +284,7 @@ void GetNextReport(USB_JoystickReport_Input_t *const ReportData)
 		if (command_count > ms_2_count(2000))
 		{
 			command_count = 0;
-			state = SYNC_POSITION;
+			state = BOOYAH;
 		}
 		else
 		{
@@ -292,6 +295,47 @@ void GetNextReport(USB_JoystickReport_Input_t *const ReportData)
 			command_count++;
 		}
 		break;
+	case BOOYAH: ;
+		bool a_down = false;
+		if(command_count % 2 != 0)
+		{
+			ReportData->Button |= SWITCH_A | SWITCH_RCLICK;
+			a_down = true;
+		}
+
+		if(command_count/60 % 3 != 0)
+			ReportData->Button |= SWITCH_ZR;
+		else
+			ReportData->Button |= SWITCH_ZL;
+
+		int rnd;
+
+		// Booyah!
+		if((rnd = rand() % 512) == 0 && a_down)
+			ReportData->HAT = HAT_BOTTOM;
+
+		if((rnd = rand() % 16) == 0)
+			moving_left = !moving_left;
+		if(moving_left)
+			ReportData->LX = STICK_MIN;
+		else
+			ReportData->LX = STICK_MAX;
+
+		ReportData->LY = STICK_MIN;
+
+		if((rnd = rand() % 16) == 0)
+		{
+			if((rnd = rand() % 4) == 0)
+				moving_left = !moving_left;
+			if(moving_left)
+				ReportData->RX = STICK_MIN;
+			else
+				ReportData->RX = STICK_MAX;
+		}
+
+
+		command_count++;
+		break;
 	case SYNC_POSITION:
 		if (command_count > ms_2_count(4000))
 		{
@@ -344,7 +388,7 @@ void GetNextReport(USB_JoystickReport_Input_t *const ReportData)
 		return;
 	}
 
-	if (state != SYNC_CONTROLLER && state != SYNC_POSITION && state != DONE)
+	/*if (state != SYNC_CONTROLLER && state != SYNC_POSITION && state != DONE)
 	{
 		// Position update (diagonal moves doesn't work since they ink two dots... is not necessary to test them)
 		if (ReportData->HAT == HAT_RIGHT)
@@ -359,7 +403,7 @@ void GetNextReport(USB_JoystickReport_Input_t *const ReportData)
 		// Inking (the printing patterns above will not move outside the canvas... is not necessary to test them)
 		if (is_black(xpos, ypos))
 			ReportData->Button |= SWITCH_A;
-	}
+	}*/
 
 	// Prepare to echo this report
 	memcpy(&last_report, ReportData, sizeof(USB_JoystickReport_Input_t));
diff --git a/README.md b/README.md
@@ -8,17 +8,14 @@ On June 20, 2017, Nintendo released System Update v3.0.0 for the Nintendo Switch
 
 Unlike the Wii U, which handles these controllers on a 'per-game' basis, the Switch treats the Pokken controller as if it was a Switch Pro Controller. Along with having the icon for the Pro Controller, it functions just like it in terms of using it in other games, apart from the lack of physical controls such as analog sticks, the buttons for the stick clicks, or other system buttons such as Home or Capture.
 
-### Printing Splatoon Posts
-For my own personal use, I repurposed Switch-Fightstick to output a set sequence of inputs to systematically print Splatoon posts. This works by using the smallest size pen and D-pad inputs to plot out each pixel one-by-one.
+### Booyah?
+For my own personal experiment, I re-purposed Switch-Fightstick to use random inputs to spray ink in turf war.
 
-#### Printing Procedure
-Just press L to select the pixel pen and plug in the controller: it will automatically sync with the console, reset the cursor position, clean the canvas and print. In case you see issues with controller conflicts while in docked mode, try using a USB-C to USB-A adapter in handheld mode. In dock mode, changes in the HDMI connection will briefly make the Switch not respond to incoming USB commands, skipping pixels in the printout. These changes may include turning off the TV, or switching the HDMI input. (Switching to the internal tuner will be OK, if this doesn't trigger a change in the HDMI input.)
+#### That's bad. Your team will lose...
+I like to see the world burn.
 
-The printing goes from top to bottom, alternating between two lines, from left to right and viceversa. Printing currently takes about 25 minutes.
-
-Optionally, upon completion, the Teensy's LED will begin flashing. On compatible Arduino boards, some combination of the onboard LEDs will flash. On the UNO, for instance, both TX and RX LEDs will flash, however the other LEDs will not. If this functionality is desired, issue `make with-alert` when building the firmware. All pins on both PORTB and PORTD are toggled! Beware of possible interactions with any attached peripherals, say from another project.
-
-This repository has been tested using a Teensy 2.0++, Arduino UNO R3, and Arduino Micro.
+#### I'll repor-
+I mean after like a few matches, it'll be ranked into only playing with baby squids by the match making anyway. They most likely don't play much better than random inputs anyway.
 
 #### Compiling and Flashing onto the Teensy 2.0++
 Go to the Teensy website and download/install the [Teensy Loader application](https://www.pjrc.com/teensy/loader.html). For Linux, follow their instructions for installing the [GCC Compiler and Tools](https://www.pjrc.com/teensy/gcc.html). For Windows, you will need the [latest AVR toolchain](http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx) from the Atmel site. See [this issue](https://github.com/LightningStalker/Splatmeme-Printer/issues/10) and [this thread](http://gbatemp.net/threads/how-to-use-shinyquagsires-splatoon-2-post-printer.479497/) on GBAtemp for more information. (Note for Mac users - the AVR MacPack is now called AVR CrossPack. If that does not work, you can try installing `avr-gcc` with `brew`.)
@@ -42,60 +39,3 @@ Sometimes, the Arduino will show up under a different port, so you may need to r
 If you ever need to use your Arduino Micro with Arduino IDE again, the process is somewhat similar. Upload your sketch in the usual way and double tap reset button on the Arduino. It may take several tries and various timings, but should eventually be successful.
 
 The Arduino Leonardo is theoretically compatible, but has not been tested. It also has the ATmega32u4, and is layed out somewhat similar to the Micro.
-
-#### Attaching the optional buzzer
-A suitable 5V buzzer may be attached to any of the available pins on PORTB or PORTD. When compiled with `make with-alert`, it will begin sounding once printing has finished. See above warning about PORTB and PORTD. Reference section 31 of [the AT90USB1286 datasheet](http://www.atmel.com/images/doc7593.pdf) for maximum current specs.
-
-Pin 6 on the Teensy is already used for the LED and it draws around 3mA when fully lit. It is recommended to connect the buzzer to another pin. Do not bridge pins for more current.
-
-For the Arduino UNO, the easiest place to connect the buzzer is to any pin of JP2, or pins 1, 3, or 4 of ICSP1, next to JP2. Refer to section 29 of [the ATmega16u2 datasheet](http://www.atmel.com/Images/Atmel-7766-8-bit-AVR-ATmega16U4-32U4_Datasheet.pdf) for maximum current specs. Do not bridge pins for more current.
-
-On the Arduino Micro, D0-D3 may be used, or pins 1, 3, or 4 (PORTB) on the ICSP header. Power specs are the same as for the AT90USB1286 used on the Teensy. The TX and RX LEDs are on PORTD and PORTB respectively and draw around 3mA apiece. Do not bridge pins for more current.
-
-#### Using your own image
-The image printed depends on `image.c` which is generated with `png2c.py` which takes a 320x120 .png image. `png2c.py` will pack the image to a linear 1bpp array. If the image is not already made up of only black and white pixels, it will be dithered.
-
-In order to run `png2c.py`, you need to [install Python](https://www.python.org/downloads/) (I use Python 2.7). Also, you need to have the [Python Imaging Library](https://pillow.readthedocs.io/en/3.0.0/installation.html) installed ([install pip](https://pip.pypa.io/en/stable/installing/#do-i-need-to-install-pip) if you need to).
-Using the supplied sample image, splatoonpattern.png:
-
-```
-$ python png2c.py splatoonpattern.png
-```
-Substitute your own .png image to generate the `image.c` file necessary to print. Just make sure your image is in the `Switch-Fightstick` directory.
-
-To generate an inverted colormap of the image:
-
-```
-$ python png2c.py -i splatoonpattern.png
-```
-
-#### What the dither?
-As previously mentioned, png2c.py will dither the input image if you supply an image that is not already made up of only black and white pixels. Say you want to print this bomb image you created...
-
-![http://imgur.com/r2GoVdD.png](http://imgur.com/r2GoVdD.png)
-
-*image via [vjapolitzer](https://github.com/vjapolitzer)*
-
-...but you want to know what it will look like before committing to printing it in Splatoon. Fret not! You can also preview or save a copy of the bilevel version of your image.
-
-To preview the bilevel image:
-
-```
-$ python png2c.py -p yourImage.png
-```
-
-To save the bilevel image:
-
-```
-$ python png2c.py -s yourImage.png
-```
-
-![http://imgur.com/uUOeJ7P.png](http://imgur.com/uUOeJ7P.png)
-
-*image via [vjapolitzer](https://github.com/vjapolitzer)*
-
-Looks good! Time to get printing.
-
-### Sample
-![http://i.imgur.com/93B1Usb.jpg](http://i.imgur.com/93B1Usb.jpg)
-*image via [/u/Stofers](https://www.reddit.com/user/Stofers)*
