San Francisco 49ersSan Francisco's reshaped backfield committee might be a nightmare-in-waiting for anyone who invests in their stable of runners. But the 49ers' have yet to make any roster additions that dramatically impact their depth chart at the wide receiver position, as represents the only new component among the team’s receiving weaponry.As a result, Pettis appears primed to function as San Francisco’s WR1 during just his second season. That will place him in position to build upon the momentum that he had established in Weeks 12-15 when he accumulated 338 of his 467 yards (84.5 YPG) along with four of his five of touchdowns. Pettis had only been targeted eight times between Weeks 1-9, but collected 37 from Weeks 10-16 (6.2 per game), while accruing seven in three straight contests.An MCL injury prematurely ended his season in Week 16, but the prospects of having Pettis flourish throughout an entire 16-game schedule should provide enormous motivation to target him during your drafts. He should also benefit greatly from the reemergence of, who only connected with Pettis on three passes in 2018.He will also have the chance to capitalize on the extra attention that should be dedicated toward containing. Opposing defensive staffs will have been presented with an entire offseason to dissect how to neutralize Kittle in the aftermath of his unquestioned breakout year (136 targets/88 receptions/1,377 yards). Any strategy that is designed to constrain his output should open space for Pettis, and increase his chances to flourish.Pettis is not currently contending with any formidable competition for WR1 responsibilities among other 49er wide receivers.
DMX-Break™ is a 'Break Out Box' for DMX512. It is primarily intended for engineers and allows the pins of the DMX512 XLR connector to be individually. If this occurs, then the function will return nullptr, but otherwise fails silently. Additionally, all responders are wiped out, including any previously-set responders. Hardware connection. DMX uses RS-485 differential signalling. This means that a transceiver is needed between the Teensy and the DMX lines. See DMX512 for DMX connector pin guidance.
Beyond 's 126-yard, two-touchdown performance in Week 6, his sixth-professional season was impacted by multiple injuries (quad/hamstring/calf) as Goodwin only surpassed 55 yards in one other contest. Neither Matthews or pose a genuine threat to commander greater usage than Pettis and has been jettisoned from the roster.Opportunities for Pettis will remain frequent throughout 2019. When that is blended with his route running acumen, and his potential to explode for big plays, then the perfect mixture exists for him to deliver a breakout season., Carolina PanthersMoore's enticing combination of size, athleticism, and speed compelled the Panthers to select him 24th overall in the 2018 NFL Draft. He eventually assembled an encouraging collection of numbers despite playing on just 38.5% of Carolina's snaps from Weeks 1-7. That percentage improved to 89% from Weeks 9-17, which coincided with a rise in output as the season advanced.Moore had only averaged 2.4 receptions-per-game and just 37 yards-per-game from Weeks 1-9. But that expanded to 4.6 from Weeks 11-17, while his YPG average rose to 67. Moore’s increased role was also instrumental in his ability to lead all first-year receivers with 960 yards from scrimmage, which was the second-best total in Carolina franchise history.But arguably Moore’s most noteworthy achievement was leading all wide receivers with 7.9 yards after catch per reception according to Next Gen Stats.
He also finished second among first-year receivers in targets (82), receptions (55), and yardage (788). The significant increase in his targets and production as the year progressed now transitions fluidly to an accessible path toward functioning as Carolina's WR1 in 2019.Moore gradually assumed those responsibilities during 2018, when his expanding role corresponded with a significant decline in usage for. The four-year veteran's 84% count from Weeks 1-11 plunged to just 32% in Weeks 13-16, and a large percentage of the 79 targets that Funchess attained last season should be earmarked for Moore.In addition to the yardage that he will accrue when operating outside, Moore’s ability to exploit overmatched defenders from the slot provides the Panthers with the option of lining him up in multiple formations.
Moore also presents owners with the potential to accumulate yardage on the ground, after he finished second among all receivers in rushing yards last season (172).Moore’s projected surge in output is predicated on having a healthy spearheading the Panther passing attack, and Moore’s target total may not match the number that will be commandeered by. But Moore should function as a high-end WR3 with the clear potential to ascend even higher. Tampa Bay BuccaneersGodwin’s numbers were respectable last season, as he tied for 13 th in touchdowns (7), finished 37 th in receptions (59), and was also 26 th with 842 yards. But an upward trajectory to his career appears imminent, as Godwin should eclipse his 2018 production this season.That should occur as the result of the massive runway that has been cleared for him to run routes as the WR2 with the Buccaneers, after the collective departures of and This has presented Godwin with a tremendous opportunity to experience a substantial increase in value during his third season, as a large percentage of the 179 targets that Jackson and Humphries collected in 2018 will be reallocated to Godwin. He did garner 10 targets in two different contests last season.
But the presence of and Tampa Bay's other receiving weaponry led to unpredictable usage, as he also failed to surpass four targets in six different games.He was deployed regularly in the red zone during 2018, as he collected 16 targets and tied for third among all receivers with 11 targets inside the 10. But his potential to stockpile targets near the goal line will expand even further. As many of the 19 red zone targets that were allocated to Jackson and Humphries should now be designated for Godwin.Godwin’s production during the four games in which Jackson was unavailable last season does not reveal a discernible pattern, even though he collected 12 receptions, generated 228 yards, and produced three touchdowns during those matchups. Those numbers were built with erratic weekly results, as he accrued 11 catches, 215 yards and all three touchdowns in Weeks 13 and 17, while those contests were interspersed with two abysmal performances in Weeks 14 and 15 (1 reception/13 yards).
The varying results are not necessarily a concern since he will be operating in a totally different offense this season.While it is conceivable that will siphon some targets, Godwin presents the upside to function as a low-end WR2 for owners, as he ascends into a more prestigious tier., Los Angeles ChargersWilliams did not present the Chargers with a sufficient return on their investment during his injury-laden 2017 rookie season, as a lower back issue limited him to 10 games, 11 receptions, and 95 scoreless yards. But he rebounded sizably in 2018, primarily through his propensity to generate touchdowns. Williams tied for fifth among wide receivers in this category (10), although his numbers in other critical areas were not as impressive.He only finished 47th with 664 yards and was just 53rd with 43 receptions. While that output placed him second on the Chargers in yardage and third in receptions, his production could rise significantly in both categories this season, even as he encounters the difficult challenge of replicating last year’s touchdown total.will be running routes for division rival Oakland after signing a four-year contract, which releases the 65 targets that he procured in 2018 for redistribution. That should result in a hefty increase in opportunities for Mike Williams, who finished 63rd last season (66/4.1 per game).Tyrell Williams also played on 761/76.5% of Los Angeles’ offensive snaps, while Mike Williams was deployed on 139 fewer snaps (622/62.5%). That count should rise, as could the number of red zone targets that he is allotted. Any surge in opportunity near the goal line would be more incremental, as Mike Williams trailed by just one last season (15/14), while Rivers targeted Tyrell Williams seven times inside the 20.While Mike Williams accumulated double-digit touchdowns in 2018, the potential for variance in this category would suggest that it is hardly a given that he can achieve that once again.
But both his red zone opportunities and overall target totals should climb. When those are combined with the probability that he will develop into a more complete receiving weapon during his third year, then the prospects of a breakout season rise. Arizona CardinalsKirk's promising rookie season was concluded abruptly in Week 13 by a broken foot.
But that still provided a sufficient sample size to determine that he can emerge as a highly productive member of the 2018 class. Not only was Kirk performing as Arizona's most dynamic receiving weapon throughout a large percentage of the season but he was also the Cardinals' most effective playmaker.That was partially a byproduct of the ill-conceived strategy for deployment of, but Kirk's value to the Arizona attack is unquestioned. Kirk entered Week 14 with 68 targets, which placed him second to in that category among all first-year receivers. He had also captured 6.2 targets-per-game during his final five matchups (Weeks 8-13), which had improved his season-long average to 5.7 per game. Kirk had also assembled 43 receptions (3.6 per game) and accrued 590 yards (49.2 per game) before his health issue, which placed him on pace to garner 58 receptions for 787 yards.
That would have paced the Cardinals in receiving yardage, while his numbers would have placed him third among rookies in receptions and yardage.The inadequate planning and decision-making of last year's coaching staff set the offense on a collision course with total inadequacy, and the Cardinals finished dead last in total offense and scoring. But the primary culprits that were responsible for that forgettable debacle have been removed as part of the transition to Kliff Kingsbury's air raid approach.
Registered: Posts: 188Posted Hi guys,New to all of this but feeling ambitious. I've got some solid ideas of what I want to build, just need to figure the best way to implement. Looking at the DMX config files, it looks like Artemis' implementation seems to generally assume a 3 channel RGB output.
If I'm hooking up (via Arduino) to a general RGB strip, this would work wonderfully and simply it seems.I'm definitely more interested though in doing things with the individually addressable lights, and being able to drive them from a single output data link from the Arduino. Strip of 10 lights gives me 10 individually controllable lights. But it doesn't seem that DMX understands this?
Or at least the way that Artemis implements it.If I look at the shields on entryI'm wondering what is actually happening over the serial link here. My interpretation (don't have anything plugged in yet) is that the serial RX on my Arduino will receive 3 'channels' via the DMXlibrary. I'll get a value on each channel representing the color.
But there's not enough here to tell my 2812 what to do on an individual light basis. What do the various fields in this DMX event represent? Specifically and the 'change' field in the set value commands?
Is this defining a rate of change over a period of time?I'm thinking at this point, that its going to be easier for me to just rewrite the DMX config items to represent a more general transmission to the arduino - instead of reading the values that DMX wants to send, have it instead some kind of discrete indicator, that the Arduino will then read and trigger a function and do all the color and activation work on that side instead.i.e. Registered: Posts: 188Posted I'll definitely share what I discover after my RedBoard comes in (combines an Uno with an FTDI chip, so best of both worlds) I'll probably set up a serial write and try to capture what signaling comes across and try to reverse engineer that to decipher Thom's implementation in Artemis.Actually now that I'm thinking of it - is the formatting and usage of the DMX config file a general standard? That code block I posted in the previous one?I'll dig around and share what I find.But if anybody already knows, feel free to share 😉. Registered: Posts: 188Posted Haven't been able to play with the receive side yet, but having some fun with my test strip, creating cool effects.My thinking now is that I'll set the Arduino to read the inbound signaling packets, and look at things as an on/off per channel, with each channel representing a different action.
Kind of translating the Artemis event into a discrete channel signal on/off to the Arduino, which will then use that signal to begin, or stop a given function. It seems like this will give me much more of what I want than just live feeding the channel values over and translate them there. In that case, I'm stuck having to program the effects in the Artemis config file, but I'm just not really seeing how to do more elaborate things that way.
Maybe I'm just missing the forest for the trees?Shields Up - Steady value of (channel/value) = 0/1.Arduino runs a loop of the shieldsUp function which will do a wipe up of blue lights.Shields Down - Steady value of 0/0 -Arduino now stops running the shuieldsUP function.Red alert On - 1/1Red alert Off -1/0Uh oh, I think I may have cornered myself already. Can you multithread on an Arduino?Back to the drawing board.
Registered: Posts: 270Posted It sounds like you've been working out the details of your light control scheme.As you noted earlier, there is a choice to make between how much programming you want to do with the script vs. How much programming you want to do with the Arduino. Since the Arduino approach offers more flexibility, especially with respect to logic, it's been my preference to do the programming there.In regards to your last remark, I would like to point out that you do not need multi-threading to accomplish the task you are describing.
Here is an outline of how it works in my programs for reference:. The sketch has a number of global variables to keep track of the active animation states and their progress. One common structure I use is to have a 1-dimensional integer array, with one 'row' for each one of the possible animations. The row stores a '-1' if the animation is inactive and stores a positive number to represent the 'frame' of each animation. The main loop calls a number of functions, including a function ('updateanimation') to advance to the animation frame, and a function ('updatelights') to update the LED hardware. These two functions are separate because the updatelights function typically needs to be trigger more often.
If the update dmx function on the Arduino detects a change from Artemis, it can be programmed to enter a '-1' or a frame number into the array to start (or stop) the animation. Calls to updatelights or updateanimation are triggered from an 'if' statement that checks a timer. If the right number of milliseconds (or microseconds, according to taste) have gone by, the corresponding function is called and the timer reset. updateanimation increments the frame count for active animations and then adjusts the corresponding LED states (intensity, color, etc.) in a separate array according to the animation scheme. updatelights updates the actual hardware states (either via the PWM pins or normal digital pins, according to taste) based on the data in the lights array. This scheme is only needed if there is any hardware overlap between lights (such as an LED matrix).The timer-based coding method above allows the Arduino controllers to do many different things at the same time. Registered: Posts: 188Posted EditedHey Angel of Rust or anyone else that knows anything about PCB design.
Any advice on design? I tried creating an account over on Fritzing to ask someone to sanity check what I've done, but their sign up process is messed up.
(Captcha not working). So I went full bore and DL'ed a copy of Eagle. Took a while to get the hang of it, but I like it. I see that you made a few PCBs for your control panels, wondering if you wouldn't mind weighing in with an opinion on mine?
SV2 will be connected to an RJ-45 cable, which is carrying the signal for the SN75176 on pins 4 and 5, and +5v and - on the other pairs. 1, 3, 7 are - and 2, 6, 8 are +5v. Each + and - are on a twisted pair together. SV1 goes out to the light strip. I couldnt figure out how to move the pins on the schematic, so its a little bit messy, but it translated nicely on the PCB.Here's the schematic for the receivers, for anyone interested.And now a graphic of the PCB design:I'll try to find other sources for help with the design before I order it. It'll will sure beat wiring up the boards manually - too many easy mistakes to make.
Originally Posted by e4mafiaHey Angel of Rust or anyone else that knows anything about PCB design. Any advice on design?I think the overall design looks good.
If I understand your previous post correctly, you have built a breadboard prototype and verified that the design is working. That is good. I couldn't tell if each of the receivers needed to be individually addressed, or if each one has its own control signal from the main controller. If you could speak to that point, it would help to understand. The arrangement of the PCB looks like each board gets its own signal.As for the physical layout of the PCB itself, I have a few thoughts:.
the entire board can be made smaller by moving the components closer together. It will save you some money and the soldering won't be much more difficult. I recommend you put some screw holes in the board so it's easy to mount to other enclosures.
Just make sure the clearances around the screw heads are large enough for the other components. SV2 appears to be designed to mount the RJ45 jack on a separate breakout board that has the 8 pins arranged in a line. If you haven't already bought the breakout boards, you could consider mounting the jacks on the PCB directly using the two staggered rows of pins that are typical for RJ45 jacks. No matter how you choose to mount the jack, you will likely want to make sure it is located entirely over the board so it is less likely to move when plugging and unplugging the cat5 cable.
a lot of PCB designs have the GND conductor as a fill covering the entire face of the board that is not being used for other traces. I am told this is a good practice. Also it is easy to do in EAGLE and looks really good. The only caveat is to make sure you specify the minimum amount of isolation between traces. the VCC trace seams a little too close to the other pads on SV1 and SV2. Since you have a lot of room to work with, I recommend increasing the separation between them.
It will make accidental shorts less likely during assembly. since the PCB is quite small, the current limits for the traces are not likely to be an issue. However, it is easy to check and making the traces wider is easy to do in EAGLE. Since you are driving LEDs off of this board, I recommend you check them. Here is a calculator:That's all I can think of. Registered: Posts: 188Posted All great advice, thanks!.
I did already have the breakouts for the RJ-45. I didn't even think to do a staggered series of holes in Eagle, my brain was locked on the fact that I couldn't do that on my breadboard. If I do another run, I'll do that. Could have saved 5 bucks on breakouts 😉 - I guess v 0.2 will not need breakouts for the jacks.
tightened it up and got rid of a lot of extra space. forgot about mounting holes. Thats a really good idea. I have a friend who's gonna 3d print some small enclosures for me, so its not quite so important. Gonna try to use a slot to mount in place. I tried to figure out the ground plane in Eagle, but gave up after a bit. Maybe worth another look.
Total voltage moving through the non power lines will be 5 volts, and very low current. The lines to SV1 will pull up to a theoretical 3.6 amps, but in practice will be much less. The only lighting effect that uses all the LEDs at once is red alert, and some other environmental effects, but they wont ever be on at full bright, and not for long at that.
Maybe a few flashes of white for damage effects, but sustained higher current shouldn't be a problem. I could also just run dedicated, thicker traces to those lines right?Gonna go take another pass at this one, and also the control board, which I just realized would be a hell of a lot simpler to build as a shield on the arduino, rather than screwing around with connectors and such. Just found the Eagle template for one, Yay!
Registered: Posts: 188Posted First round boards are back. Like a dope I mislabeled +5 and gnd, so when I first hooked ip up, not much happened except a shitload of heat generating on the jst whip. Figured it out and swapped, and it works like a champ now. I wish I had put more space between the holes for the resistor, and used a natural footprint for the rj45 rather than mounting it onto a breakout and then the breakout to the board - but everything else is pretty hunky dory. To say I've learned a lot from this is an understatement. And now in fine myth busters fashion, I'm feeling the 'if its worth doing, its worth overdoing' bug, and wanting to build out nice neat boards for everything to really clean this thing up. But of course that's more money.Out of curiosity, would anyone be interested in buying one of these setups from me?
I can probably manufacture them without too much stress at this point, and could recoup some of the cost in R&D. Registered: Posts: 188Posted Down to 17 hours until the big event. My test run on Wednesday went as smooth as can be. The great giggle to me here is that 6 of the systems in use for this will be Macs, for a windows native game 😉I didn't get all of the lighting effects to do everything I wanted.
I guess thats what a 2.0 code rev is for. But for the 1.0 version of hardware I am very happy. The Arduino's network connection is really flaky, and I sometimes have to reconnect power a dozen times before it comes up, once it does, we're cooking with hot fire! He receiver boards work perfectly.
The transmit board is 100% as well. I didn't do a PCB for that yet, since I've only got the need for 1 of them, but my OCD overdo-er is telling me at some point I'll PCB that one too. The distribution PCBs also work well, but I think there's a minor physical flaw in the location of things in terms of wire routing in the case. Something to think about for V2.Heres a block diagram of how its all worked together, along with some photos for your enjoyment.I'll post the finished code after the weekend and push it to Git for everyone to have to do with what they please.Block Diagram of Signals. Power is also sent to receivers via the distribution boards.Components in the case.some creative rigging to get it all to stay in place.
The vertical pins for power on the bistro boards, I'll probably remove and just solder direct tot he boards, but leave the other end as a disconnect-able line.Receiver PCB designDistribution board designEventual PCB for the transmit board. Registered: Posts: 188Posted EditedLearned a lot, the event was a success. Not without problems of course.
Nearly melted some wires at the very beginning not noticing a short on my lighting controller. Might only be 5v, but that ATX power supply has a lot of Amps to push over those tiny wires!Wifi there sucked, so we ended up needing to switch to wired, but had to 'order out' for a switch and a bunch of cables. Should have planned ahead for that.Here was the bridge layout: Rationale for the setup was Comms behind the captain, so they were close for constant interaction, and science next to weapons for the info sharing there. Engineering where it was with a big monitor so the captain can see at a glance what's up over there.My DMX setup for the energy meter needs a little work, as the output is a little wonky. The code on the Arduino for outputting the effect to the WS2812B is solid though, so there's half the work done already. I want to add 'static' like effects to the shield meters when a hit is taken, but haven't quite figured that one out yet.Where to go from here? The Arduino Mega I'm using has a LOT of outputs, so maybe strobe lights, smoke machines, a klaxon.who knows?
Anyone have any cool ideas? Registered: Posts: 188Posted In the process of drawing up a new, more efficient PCB for the whole thing. It will plug directly into a standard 24 pin ATX power supply, no modifications needed, and will handle all power distribution and data signals out to the ethernet jacks. Should be able to support 8, which is 2 more than I'm using right now. So conceivably, it could power 2 more LED strips, and/or any other devices that could be data controlled by an Arduino, and need 5v or 12v power. (I'm thinking strobe lights,smoke machines, rotating siren style lights, etc) Interesting thought is to put switches on the board to be able to swap between 12v and 5v to the individual output lines for power. The ATX supply outputs both, so I've got both right there.
Anyone have any thoughts there?I'll have to order 3 of them (that's the way OSH park works), so if anyone is interested, I'm happy to sell one of the extras. (I'll keep the second as a backup spare) I'll provide a components list and the schematics too, along with a link to the receiver board for the LED strips, and the code for everything too.I've really enjoyed working on this project. Customer controls like Angel of Rust did may be next on the horizon for me. Can't stop the train once it gets rolling! Registered: Posts: 188Posted Ugh.I haven't figured out an effective way to get the board size down to a reasonable cost for the 'master controller'. What I'd really like it to have on a single board, the Arduino, the transceivers, the power distribution and the cat 5 out lines to the lights all together. Because it needs to be an Arduino mega, there's a sizable footprint there that I haven't figured out how to dual purpose the space.
I'll continue to update progress as I goSome caveats I need to figure out - the ethernet ports all need to be on a single side, facing out, otherwise I need to build a different case, and I'm pretty partial to the mini ATX computer case I'm using now. I guess making a custom sized out might be a big help, as I could then put the rj45's on both sides.things to think about. Right now it has 8 x rj45 outbound to the lights, 1 x rj45 inbound to the ethernet shield on the Arduino.
Theres an internal rj45 that connects to that one so that I can jumper to the shield without having to run a cable into the case, and instead have it nice and neat terminated on the back panel.Right now its about 3'x6.5', which makes for a somewhat steep cost to run at oshpark. Anyone come across any alternatives that are cheaper? Not that its necessarily better to go that way, as I'm very happy with what Oshpark has put out for me so far.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |