Working with nZero, the City of Reno was able to confirm their carbon baseline, understand their operational emissions, and identify areas to be more carbon efficient. “The investment in our partnership with nZero is helping our climate goals become a reality for generations to come. The accuracy of data provided by nZero allows us to position the City ahead of schedule so we reach our target greenhouse gas reduction numbers,” said Reno Mayor Hillary Schieve. Our Climate Action Plan set the goal of reducing community-wide greenhouse gas emissions by 28% of 2008 levels by the year 2025. This carbon transparency and accessibility is enabling them to implement meaningful change and track more aggressively against sustainability goals. They can also act on their emissions data immediately, no longer reliant on annual or monthly calculations to understand their Scope 2 emissions. On the electric side, 24/7 emissions tracking has allowed the City of Reno to understand their usage patterns, and how much they can change throughout the course of the day, month or season. City employees have instant, up-to-date data throughout the year, and they are able to focus their efforts on implementing more effective climate action. With their emission data automated, housed, and accessed through one, easy to use platform, the City of Reno no longer spends countless hours pulling together data from disparate sources each year. As we continue to battle drought, diminishing water supplies and wildfires across the West, we are reminded daily of how critical our fight is to slow climate change. This innovative technology can help us to accurately measure and track our carbon emissions to work to reduce them. Because nZero connects directly to utilities, meters and other operational data sources, Reno was able to gain direct access to actual, first-party carbon data-allowing the city to confirm their carbon baseline and ensure they are on track to meet their 2025 goal. Utilizing nZero’s best in class data and carbon management platform, Reno could capture, sync and automate real data about emissions across all city operations, related to all three scopes defined by the GHG Protocol. In 2021 the City of Reno partnered with nZero. They also were having trouble capturing their entire carbon footprint, across scopes 1, 2, and 3. Common tracking methodologies based on emissions averages did not provide the strategic and operational insights required to reach these targets. Reno quickly realized the need for better data to implement effective carbon reduction initiatives. In the face of this challenge, Reno has made sustainability a top priority andĬreated a robust 2019-2025 Climate Action Plan, identifying nine sustainability objectives and setting a 2025 goal to reduce greenhouse gas emission in Reno by 28% from 2008 levels. Oasis for its citizens and nature lovers from around the world. Rising more quickly than any city in the United States since the 1970s, posingĪn existential threat to many of the attributes that make this community an Yet,Īccording to a study conducted by Climate Central, Reno’s temperatures are Nevada, and world-class ski facilities make it ideal for outdoor lovers. Is there a right way to configure timers to work in 32bit capture mode without such workarounds.With a population of over 235,000, Reno, The Biggest Little City in the World, Ugly workaround like if (ccr_lsb = 0) ccr_msb++ Looks like some sync problem when capture event at the same time with slave timer overflow event. Most time this code works as expected, but issue occurs when ccr_lsb (master timer captured value) = 0, than ccr_msb (slave timer captured value) is one less than expected, and period_ticks become 65535 less than expected. Pre_tick_count = ticks // pre_tick_count is static Uint32_t ticks = (ccr_msb<<16) + ccr_lsb Interrupt looks like: uint32_t period_ticks = 0 Master timer running at 36Mhz (72Mhz / 2).Ĭaptured data processed in TIM3(master) capture interrupt. Capture signal is connected to both timers input (CH2 for TIM3 and CH1 for TIM4). TIM3 as master timer and TIM4 as slave timer clocked by TIM3 overflow event (TIM4 works in external clock mode 1). In my project two 16 bit timers chained together to achieve 32bit capture resolution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |