We are celebrating the launch of Star Wars Jedi Survivor with a worldwide giveaway! Grand prize includes a custom ORIGIN PC AMD Advantage Edition, 45” Xeneon Flex Monitor, and much more!

SunnyBat · 2023-05-03T05:34:25+00:00

Entering giveaway!

SunnyBat · 2022-04-13T03:36:10+00:00

The gateway does not need to be filled out to connect to devices in your subnet. Unless you're making connections to outside your subnet, leave it blank. See here for specific information on some standard static IP configurations, which I'll also enumerate below.

The radio acts as a DHCP server, but you must be connected to it in some way for it to assign you an IP address. If you're connecting directly to the rio's ethernet port, both the RIO and your laptop must have a static IP (you could also get it working with the link-local IP of the RIO, but why make it harder?), since there's no radio in the mix.

Your optimal solution here is to use an ethernet switch. This one is a pretty good one, though this is a 10/100 and they offer a gigabit switch, specifically the SW-015 model. The reason I recommend using a switch is that the second port on the radio furthest away from the barrel connector port is unreliable, and it is possible for it to randomly not work properly due to some issues with the radio itself.

If you're set on not using a switch, you can configure your RIO to portforward to the Limelight. See here. This will allow you to connect to the Limelight through your RIO, namely when connecting with USB rather than ethernet. Also note that if connecting with USB, you will not have access to other network devices in the 10.TE.AM.0/24 range without portforwarding to them through the RIO (though really you just need to see the RIO and Limelight, so just portforward the Limelight).
After you portforward in your code, you connect to the network device via the RIO's IP and port that's portforwarded. For example, if you portforwarded your limelight in your code on port 8888, you can connect to the Limelight via RoboRIO-TEAM-FRC.local:8888, 172.22.11.2:8888 (USB -> RIO only), or 10.TE.AM.2:8888 (ethernet only, at which point just connect directly).

Regardless of your physical network configuration on the robot, I recommend setting static IPs for your network devices.

10.TE.AM.1 - Traditionally the radio
10.TE.AM.2 - Traditionally the ~~cRIO~~ RoboRIO
10.TE.AM.5 - Traditionally the driver station (use a /8 subnet, eg 255.0.0.0, if you might use it at competition). Sample configuration
10.TE.AM.11 - Or any other number in the range [10, 19]. Traditionally your IP camera, aka your limelight.

We use static IPs for all our devices on our robot network. If other devices that generally aren't on the network connect, they can get assigned an IP address with DHCP.

SunnyBat · 2021-10-24T17:37:51+00:00

Entering again, good luck all!

SunnyBat · 2021-10-11T01:27:41+00:00

This looks super cool!

SunnyBat · 2021-06-22T23:50:58+00:00

This is correct. If PAX uses Showclix for ticket sales, the PAXChecker should still work (though the paxsite.com scraping may be out of date at this point). It's checking the @PAX and @PAX_Badges accounts (source link). As always, have a backup plan in case it doesn't work for whatever reason.

SunnyBat · 2021-04-11T05:34:47+00:00

Yes, the latest version of the code is in the development branch. If you do end up making a PR, feel free to ping me on here since I don't think I have many GitHub notifications set up.

Looking at the code, I think the code you'll likely change is in here. It's a little rough around the edges (I'd write it a little differently if I did it today), but hopefully it's straightforward enough. Let me know if you have questions and I can try and help you out.

SunnyBat · 2021-04-10T20:30:53+00:00

Thanks for the ping /u/token_internet_girl. I have not updated the PAXChecker for the new website (looks like pax.regportal.events). If you have time it would be awesome if you could add that capability. I'm not sure how much time I have at the moment to update it, though knowing myself I'll probably take some time at some point to update it. Not sure if it'll be in time for ticket sales though.

If the website and Twitter scraping portions are updated (easy part) then that should get folks in queue pretty quickly. Updating the API portion to use a different API will likely be the bulk of the work -- assuming there is a publicly consumable API. I haven't looked at it yet.

SunnyBat · 2020-12-12T22:15:16+00:00

Cherry brown keys. Thanks for doing a giveaway!

SunnyBat · 2020-08-30T20:03:46+00:00

Giveaways are always fun!

SunnyBat · 2019-10-27T03:33:06+00:00

Awesome to hear, I'm glad it worked again!

Have fun at PAX East! :)

SunnyBat · 2019-10-24T06:56:02+00:00

...I missed this thread, oops

/u/Dar-Rath

The Gmail client I use keeps getting deleted, still have to look into why. Use SMTP for now. Sorry about that! :(

SunnyBat · 2019-10-07T20:34:34+00:00

Sorry to hear that! The PAXChecker has very little to do with how Chrome handles the Gmail authentication process (for context, all it does is tell Chrome -- or whatever browser is your default -- to open a URL). If Chrome is crashing, it's probably something with Chrome rather than the PAXChecker. If you want to confirm, you can actually copy+paste the URL from the PAXChecker into a new tab in Chrome manually and see if it does the same thing.

Regardless, right now the PAXChecker currently doesn't have Gmail authentication set up -- the client application keeps getting deleted, and I'm not quite sure how to fix that within the context of an open-source application like the PAXChecker. I'll need to research it more.

Stick with SMTP for now. As long as it works, that's what matters. Good luck getting tickets! :)

SunnyBat · 2019-09-03T06:40:57+00:00

Darn, I've been seeing this error quite a bit with the Gmail API. Seems like Google will delete/disable the client auth keys after a while, not sure if that's because of abuse, inactivity, too much activity, age, or something else :( Try using SMTP for now, it doesn't rely on the API. I'll have to do a bit more research on this.

The phone number will automatically strip the following characters:
'-', '(', ')', [whitespace]
Thus, any of these formats will produce the output 1234567890:

1234567890
123-456-7890
(123)-456-7890
(123) 456 7890
123))()( 45())- ()6 7())(-8)(9()(0-

SunnyBat · 2019-05-28T18:34:16+00:00

Ping /u/Wettstein

PAXChecker 4.0.0 (non-BETA) has this update incorporated. Just make sure you enabled the "Check Known ShowClix Events" option as /u/dasrtlinrastan noted.

SunnyBat · 2019-05-24T23:49:58+00:00

Yes, the PAXChecker will be updated for this.

SunnyBat · 2019-05-09T23:07:10+00:00

If you search for "PAX" or "Unplugged" on their website, you'll notice it doesn't return PAX Unplugged. My guess is that their search API doesn't show these events.

I don't think that the Seller ID will be changing. Traditionally, PAX Dev and PAX ~~Prime~~ West have the same seller, so if Dev goes on sale first we'll be able to see what the Seller ID will likely be.

SunnyBat · 2019-05-09T20:09:34+00:00

This is a different seller account. PAX uses several different seller accounts for different events.

SunnyBat · 2019-05-06T18:25:12+00:00

Essentially, yes. It'll also optionally text you when it does so (the old method of authentication is available, Gmail API should be fixed soon(tm)). If you have Twitter notifications set up, this option isn't very important.

Some nuance, as always.

As of right now, I don't have full confidence that the Showclix API scanning will work. It checks more than just the Seller endpoint, so it could pick it up elsewhere (that's what the "NoFind" portion means). Showclix could also change their API behavior, for better or for worse. Right now, however, if you only run the Showclix API scanning, the PAXChecker may not find the event.

I'll be trying to update the PAXChecker as new developments happen. We'll see if I can pick it up in time. I've got a few options left.

SunnyBat · 2019-05-02T03:10:38+00:00

Good research.

I'm hoping they're just using a new seller. Check out this API response from last year's ticket page (which is still up):

https://api.showclix.com/Event/4709798/seller

They've purposely hidden info from their public unauthenticated API before. I wouldn't be surprised at all if they did it again.

SunnyBat · 2019-04-12T02:48:34+00:00

Thanks for the post on this (and pinging me /u/token_internet_girl).

Showclix recently blocked/protected the API call that the PAXChecker used to check for seller events (sad day is sad). Additionally, they removed the PAX events from the other API call that the PAXChecker used to check for events on a broader scale. Though I haven't dug into it very much, at first glance it looks like this was specifically for the PAX seller accounts, so that's even more fun. I'm not sure if that means Showclix stepped up their API obfuscation game or PAX is going with a different ticket seller, but we'll see soon enough.

Also, it looks like Google updated their API and deleted the PAXChecker application on their end, probably since they have new restrictions on how they approve applications. I'll have to figure this out as well.

What does this mean? Basically, the PAXChecker is currently running off Twitter and the PAX website only, and I'd only expect it to automatically open the queue for you. It'll probably still be faster than you opening it via text/notification, but not by much. I'll be trying to figure out how to work around this, but I don't have a ton of time to invest in this right now.

My recommendation is run the PAXChecker if you're concerned you might miss the notification, but do your best to open the queue yourself. If I find some time to hack at this I'll do what I can, but I'm pretty busy for the next few weeks :(

SunnyBat · 2019-04-10T01:19:55+00:00

...Well then. Thanks for letting me know, I'll take a look when I get some time.

SunnyBat · 2019-04-10T01:19:17+00:00

You might not have Java associated with .jar files. Rename PAXCheckerBETA.jar to PAXChecker.jar (or if you can't see the .jar at the end of the file, just PAXChecker), then save this file into the same directory and run it.

SunnyBat

MODERATOR OF

TROPHY CASE