Hi, thanks for joining us today at the talk for the OpenEMP project and its working group. We're going to be talking about standardizing interactions between the operating environments in a heterogeneous embedded system. I'm Natalie, open source program manager working with Xilinx open source office and my co-presenter is Stefano who is system software architect and virtualization lead at Xilinx. Both of us were involved with the relaunch as a linear community project. So what are we going to cover today? So we'll talk about what OpenEMP is trying to solve. We'll give you some information about what the project is and how this project that started with a repository of code and some interested collaborators grew into a more mature open source project with working groups that are now tackling a wider scope. We'll cover examples of OpenEMP in industry to give you an idea of the breadth of use cases and of participation. We'll point you to resources where you can learn more and we will let you know how you can get involved. So I'm going to leave this slide up for a couple seconds if you want to take a screenshot or a photo of it. These are the acronyms that we're going to be using later in the presentation and Stefano will take it from here. Hi everybody. I would like to talk to you about what kind of problems OpenEMP was born to solve. Nowadays, system on chips, so SOCs in short, are becoming more and more complex, more and more rich in terms of hardware resources, capabilities and functionalities.  It's not like that anymore. So now, often you have more than one cluster of CPUs. So if we take as an example the Xilinx and PSUC, we have a cluster with four Cortex-A cores and then we have on the side a cluster with two Cortex-R cores. So these are both ARM cores, but actually they support different instructional sets and they're very, very different CPUs. One focus on real-time and small application, the other one can support very rich OSs. We can also, we also have all other kind of cores. We have micro-blaze cores that are not, you know, they're not using an ARM instruction set at all. And we have a lot of programmable logic. So you can deploy multiple soft cores as we say. So CPUs in programmable logic, there can be micro-blaze. It can be other CPUs too, like Cortex-M. So in other words, an SSE of today, it looks a bit like a whole data center on chip. So there are with many clusters of different, very different cores running alongside. Some of them, like the Cortex-A cluster, which is the largest, with multiple execution levels and very different software runs at each level. So you have user space, conos, hypervisors, and secure world with multiple execution level, a secure world too, with secure real zero, secure real one. So it brings us a very rich ecosystem of software and operating system that needs to be installed and run and coordinate across the SOC. So Linux, it's very important especially on the Cortex-A cluster, but it's not the only operating system that runs. So you have Zephyr or Friartus, all the RTOSs on the Cortex-R or the smaller cores. Burmental application is still very popular and used.  So that gives us really a combination of firmware, operating system, larger and smaller real-time and non-real-time that can be very complex to configure, coordinate, and make it work together in an efficient way. So typically people still, without open-arm, there is really no solution for deploying and managing such a complex system. Everybody is really hacking together or cobbling together the system as you can because it's really difficult. So there are a number of difficult problems to solve from just the configuration to resource management, life cycle management, communication, and more. And as you can see, all these problems need to be solved with interfaces. So you cannot really just code away the implementation and expect it to be used by everybody. There are so many different communities, open-source projects with different cultures, proprietary vendors, so many components and pieces that they need to communicate and come together to make the system work. And this is how open-arm was born. To solve these problems through reference open-source implementations, through common interfaces designed by the community and open standards. And by reference open-source implementation, I mean that as the best possible way to get a new interface adopted quickly is to have a reference implementation that anybody can look at, see how it works, and then use it as a reference for the running implementation in Linux, Zephyr, all the rest is really anywhere. And through the proper documentation of these interfaces being introduced and a proper management of these interfaces, then you get to the point that you have a standard, a very strong standard that the community stands behind. So the the vision for open-arm, I'm going to read it out loud, is for the open-arm project to seek the standardized interactions between operating environments in an heterogeneous embedded system through open-source solution for asymmetric multi-processing. This is really the condensed version, the summarized version of everything I said so far. So open-arm, as Natalie mentioned in the beginning, started small, like all open-source projects. It started with a couple of repositories on GitHub, the RP message and remote pro repositories, and they are for to solve very core problems that open-arm is trying to solve. RP message is a protocol based on for communication between clusters. And remote pro is for lifecycle management, so that one cluster can start the other. But open-arm is not just any open-source project, like I mentioned, the key of open-arm is really solving the interaction between different components and the creation of standards through collaboration and community discussions. So since the beginning, open-arm had meetings, regular meetings, a few city con vendors and other companies working together to make the vision a success. Initially, open-arm was under the multi-core association as a working group. Over time, so it grew, it grew a lot more repositories than just RP message and remote pro. We now have different subgroups and we go through them later in details. We also created a bit more structure around the project. So it's normal to start small, but it's good to actually give a little bit of structure to the collaboration as you grow and you grow more members. So one of the first things we looked at a couple of years ago is to move open-arm under a proper foundation or an entity that could actually represent open-arm, something along the line of an open-source foundation, for instance. So we looked at the various options and eventually we started open-arm as a, we relaunched open-arm as a Linaro community project in September of 2019. So Linaro community projects are fully open-source projects for collaboration. A bit like a Lino Foundation project. So they're different from Linaro as an organization that is a much larger organization. So anybody can really join a Linaro community project. You don't need to be a full Linaro member to do it and you just need to join the project itself. And it can be, usually there is a very, very small fee associated that usually anybody can afford. So the good about having open-arm as a Linaro community project, the good thing about it is now we have a legal entity so we can have a budget. So we can pay for testing if required, we have a bit of money to pay for events, for locations or for interns as needed. Aside from the entity, the legal entity, the other thing that we did when we relaunched the project as a Linaro community project was to look at the governance. So I'm an open-source guy as many of you in the audience. So I really dislike, in a way, too much structure or too much bureaucracy or retake. But it's good to have in a project a tiny bit of information and clarity and transparency on how the fundamental processes work, such as in this case, how the budget gets decided and allocated, who decides about the budget. Or more importantly, actually the technical city committee, who is part of the technical city committee, what are the decisions that TSC makes? Or as a contributor, how do you become a maintainer? So these are the very simple questions that we answered with the governance that we introduced in September 2019. And really the idea is to make the process and the community transparent so that anybody can see how it works and can join or can become a maintainer or more involved with the project as they wish. I should say that open-hump is also true, as I mentioned, in sub-projects. It is so, but it still stayed true to the core. So the mission of open-hump is really creating standard and interoperable interfaces so that multiple components on such a complex heterogeneous system can work together and coordinate. And all these sub-projects are related, in a way, to interfaces and standards, including, for instance, just to mention a couple of new ones, the proxy operation work that we are doing, so that one cluster can access files on the file system of another cluster. Definitely requires coordination and very stable ABIs and compatibility interfaces between all these components. I'm going to let Natalie take it off from here and talk about what's the latest on that one. Thanks, Stefano. So right now, with the OpenAMP project, we have some additional working groups, and they build upon the OpenAMP framework that we started off with the multi-core association project with. These are now tackling problems that are related to what OpenAMP framework started with. And as Stefano mentioned, we sort of leveled up in maturity as an open-source project. We now have official maintainer roles, the technical steering committee, the board, the governance, the budget. And I think the part that the group had the most fun with in the relaunch was the logo. So as you can see, we have two P's in OpenAMP. They are different, so it's heterogeneous, and they are connected, and so they can communicate together. So what's really important, I think, is that we have the very diverse member points of view from a technical perspective. So although this is a Lenaro community project, as Stefano mentioned, it's not necessary to be a Lenaro member. Our members represent both ARM and non-ARM use cases. Linux, RTOS, environmental use cases are represented. Use cases with high-performance systems and resource constrained systems are represented. And it's really great that the discussions are very focused on trying to solve technical challenges. So I'll go into a bit more detail about the OpenAMP project working group. And what's really nice is this is an effort by many companies, and so we have different companies leading the different working groups. So the OpenAMP RP working group is the one that focuses on the original parts of OpenAMP, so remote proc, RP message, VertIO, and LibMetal. The main repositories we've got are OpenAMP and LibMetal, which just had a release in April. And then active work that's going on in this group is around big buffers, around improving testing through integration with lava continuous integration. And Lenaro has a lava lab, which is Lenaro Automation and Validation Architecture. That's what that's sent for. The group is working on getting patches upstreamed to the Linux remote proc mailing list for remote proc core. And I guess the most notable recent event is that some of the work on support for 64-bit L files is now part of the 5.7 kernel release. Another working group that we have that is ramping up is the application services working group. So that is led by Martin from One River. Oh, I forgot to mention OpenAMP RP is led by Bill from PI. So for application services, they're focused on what is needed to build on top of OpenAMP. We got together in San Diego at Lenaro Connect last year in the fall and had a meeting and a call with everybody who was interested. And the topics that were application developer issues that resonated most with everyone who was in the discussion was remote file access, so reading and writing files remotely, access of a console of a runtime remotely, proxy ports, and messaging APIs. So Wind River has been working in this area and taken inputs from the working group and they are working to put together example code that can be used as a starting point for more detailed discussions. They're proposing that application services would use operating system drivers for console, socket, file access, and networking from Vert.io largely as is. And then OpenAMP would provide the memory APIs, inter processor interrupts, and remote proc, while Vert.io would provide the runtime integration and collaboration using existing drivers and existing specifications of the driver protocol, which would significantly accelerate development, and also hopefully make adoption easier. And I'll hand it over to Stefano, who is the system device tree working group lead to tell you about the system device tree working group. One of the issues that we have with such complex heterogeneous systems is that we need a way to describe it, or in all its rich complexity and richness of resources. So the system device tree working group aims at extending the device tree to describe such a complex system, such an heterogeneous system. And the way we do it is by adding the concept of multiple CPU cores, multiple CPU clusters and multiple views to the device tree. So the device tree you probably know is a very commonly used standard in embedded to describe the hardware available and typically for one operating system. So one classic usage of device tree is, for instance, to be passed from the firmware from you to Linux, to let Linux know what's available, the device is available, the amount is the number of CPU cores, etc. So we took device tree and looked very closely at it and we tried to extend it so that it's not just the description of what Linux is, but it's a description of everything, including the Cortex-R cores, including microblades, including anything that is on the platform. In order to make this happen, there were a few changes to the device tree bindings, but very, I mean, not very verbose in terms of change, but very meaningful because, as I mentioned, device tree is typically a single view description. So it describes the system based on the view of one OS. Now it's a system device tree, we can describe the system with a multi-view, in a multi-view manner, so that each CPU cluster, for instance, we can describe, can have a different address mapping. So a device could be visible only by one cluster and not by the other, it could be routed in a way so that it's only reachable by one and not the other, or if it's reachable by both, it could be at different addresses. So these are the kind of problem the system device tree is solving. There is another set of problems the system device tree is tackling and is about firmware and software configuration. So firmware and software configuration typically does not belong at large in the device tree. There are some core pieces of it so that they are there, and the one that we are working on are about resource assignments. So you can imagine that in a system with multiple clusters, you're going to have multiple operating systems, each of them with running at maybe a different execution level of these clusters, and also we're going to have a bunch of memory that is their own, they're only going to have some memory to communicate with others, share memory, the interrupts which you send messages across, they're going to have some devices uniquely assigned to them. All these core configuration on basically what the software running on a cluster can see, can access and can use is what we call together an execution domain. So in system device tree, we define the execution domains available on an SOC. So for instance, we define the execution domain running on the Cortex R5 and the execution domain running on the Cortex Z. And then we define which memory is private to both execution domains. So all, you know, it's their own to use. And also the pages that are used for communication between the cluster. We also define the devices that are only accessible by one and not the other. This is really what system device tree as a specification is today. But system device tree is not just a spec, there is also some code and tooling involved. And the main one is called Lopper. Lopper is the English word for, you know, a gardening tool to chop and, you know, a tree or a bush, you know, to reduce the amount of leaves that you have. So it's really, it was a word chosen for this tool because the main goal of Lopper is to take a system device tree as input and chop it into different traditional devices. So system device tree is useful as a description, even at runtime, to pass to an operating system. But it was really never the goal that OpenMP system had to learn about system device tree because, well, why would a system device tree like Linux should know about what's running somewhere else that you cannot really access or add control over? I mean, useful information, but it's really not necessary. So since the beginning, one of the goal is to be backward compatible. So it's to be able to provide as output from system device tree multiple traditional devices. So the idea is you have a full description of the old platform, the system device tree. Then you can use Lopper to cut it down, to chop it to just a single device tree for one execution domain, the one you care about. So you can generate the device tree for Linux, you can generate the device tree for an Arthos, and you can generate the device tree even for a Bermeter application. And then of course, doesn't mean that one day, the thing where like you would or Linux itself might benefit and learn and grow out to learn, out to parse the system device tree and become aware of it. So speaking of Arthos, one of the things that we are seeing is that system device tree and Lopper are being used to generate a device tree not for necessarily the runtime, but also for the build time or very small operating systems or Bermeter application. And the device tree is basically used in this case for configuring the build of the Bermeter app, so that then when it puts up, it already knows all the addresses and what's available. So the latest information on system device tree is, so we have many lists, we have regular meetings, we are definitely welcome to join us if you're interested in this problem and these solutions. So one of the things that we're looking at is bus fireworks. So it's often the case, and it's the case on the board, and it's the case on all the city conbenders as well, that you have tools to actually protect memory accesses from one cluster to the other, so that you can actually prevent, let's say, the cortex A from tampering with the device that was supposed to be uniquely assigned to the cortex A. For instance, on Xilin Sport, this component is called XMPU. On other vendors, there are a very rich ecosystem of these tools to be able to offer protection. So system device tree is really a natural fit for this kind of problem because it does already this concept of resource allocation to different clusters and different operating systems. So it's really natural to add protection to this information. And these are the binding that we're working right now together with ST, micro, electronics, coming up with a definition together and a proposal that will show soon to the community. Hypervisor interfaces is another working group that we're going to start in the near future. Hypervisors, as their main goal in embedded, is to start multiple VMs and assign devices to virtual machine, maybe set up shared memory for communication. So as you can see, the problem space is very similar to AMP, to heterogeneous computing. It's still about giving unique access to devices or setting up shared memory or these kinds of problems. So it's really fitting that open up is also looking at common interfaces for hypervisors in embedded. And what is, let me go a little bit into the detail of what this working group is going to try to achieve. It's getting more and more common for OpenSys project to get used in more and more environment, vertical and markets that were never used before. Some of them require safety certifications, such as, you know, automotive and avionics need safety certification for the software. So in Zen project as well as other OpenSys project like Zephyr, we're trying to work together making the OpenSys software more easily certifiable, providing more of the tools, the artifact, the documents, the tests, so that users can take them and do a certification if they wish to or if they have to. So as part of these safety efforts, for instance, in the case of Zen, we have a special interest group called FUSA, special interest group. So we are trying to produce safety documents. So you should know that safety certifications have very high requirements, very on documentation of external interfaces. So this document needs to be incredibly precise, need to contain all the details analysis interfaces work. In fact, this document, they need to be so detailed that it's common practice in safety that the team working on tests is expected to write a test just looking at the documents of the interfaces, never looking at the implementation, the implementation done by a different team all together. So this is really, when you look at these ways, these documents are really incredibly detailed interface documents. So there is no reason why we cannot come together as a community to standardize these interfaces to work together on these documents so that they can be useful to everybody, not just Zen project, but all the right advisors open source of proprietary, everybody could use them for safety or just as an interface documentation or even maybe just as a standard. So if we work together on this document and we use these interfaces in different projects, and it becomes also easier to have compatibility interfaces to become natural, you can just become just one interface for everybody to work against, become easier to write software and guest operating system running on this hypervisor on switching from one to the other, prototyping with one open source hypervisor, switching later maybe to a proprietary provider, for instance. I think with that, I'm going to leave it to Natalie to continue on examples of open applications. So we have a couple of slides coming up of all the ways that different companies are using and have contributed to OpenAMP, and what this will go to show is how we're really solving problems that are important in industry and that benefit from standardization and collaboration by multiple companies that have a variety of use cases, and it shows the active involvement of the member companies in the project and in using OpenAMP. So at Xilinx, OpenAMP is the default AMP solution for Zinc 7000, Zinc Ultrascale Plus, MPSOC, and Virtual Devices. These devices have a Cortex, a application processor unit, and MPSOC and Virtual Devices have a Cortex, our real-time processor unit, so APU and RPU, which Stefano mentioned earlier in the talk. And so either APU or RPU can act as master. And as Stefano mentioned earlier, we also have microwave soft processors that can go in the FPGA fabric. So there's also microwave OpenAMP support. Mentor graphics, they use OpenAMP as the core for the mentor-embedded multi-core framework and multi-core framework product offerings. They expand upon OpenAMP by adding functionality to support Linux as a remote, large buffer support, zero-coffee proxy support for Ethernet, and additional development tools. And they also created a version that is focused on mixed safety-criticality systems where mentor-embedded multi-core framework handles the communications between the safe and non-safe domains on a single MPSOC. TI has been working in the OpenAMP project to enhance the Linux kernel implementation of Remote Proc and RPMessage, to define the wire protocol between processors, and has contributed a limited scope version of Remote Proc loader into UBoot to handle starting auxiliary cores before main Linux starts. TI uses the OpenAMP implementation for RTOS and for bare metal environments as an interoperability reference for its own implementation. CalRay leverages OpenAMP capabilities as a standard message-passing solution within its homogeneous mini-core architecture on MPPA3 processor. This support works across multiple systems when MPPA3 is used as an accelerator using VerdiO over PCIe, as well as inside the processor itself using VerdiO with shared memory. The Zephyr RTOS open-source project has a general integration to make OpenAMP available. Nordic Semiconductor has an example in Zephyr where they use OpenAMP to provide a Bluetooth host controller interface so that within a single SOC the application core can run the Bluetooth host and interact with the network core running the Bluetooth controller. Linaro hosts the OpenAMP project through their Linaro community projects division and some areas that their engineers are involved are through Zephyr, through the OpenAMP RP working group, and through the Lava testing. ST Microelectronics integrates OpenAMP and its multi-core and multi-SOC STM32 solutions for inter-processor communication between OpenAMP to OpenAMP or Linux RP Message to OpenAMP and ST uses the OpenAMP library with bare metal sorry with free RTOS and with Zephyr. WinRiver provides OpenAMP and participates in the OpenAMP working groups to accelerate the ability of developers to create edge compute applications and ARM has played an active role in the discussions to shape the system device proposal that Stefano talked about earlier. So where can you learn more and how can you get involved? We have a GitHub project so if you go to github.com slash openamp you can check out what we've got there. Also Stefano mentioned Lopper so Lopper lives at devicetree.org's GitHub we have an OpenAMP wiki. If you go there you can check out the notes from previous calls and there's information about features that are being worked on and features that are under consideration for future work. We have a community project website and we have mailing lists so Stefano had mentioned the mailing lists we welcome everyone to sign up you can go to list.openampproject.org we have calls for the technical steering committee and the working groups the call invitations are sent to the mailing list so if you're interested do sign up for the mailing list right now the one that is meeting most frequently is the OpenAMP working group they meet every two weeks and then the other groups TSE and board meet sort of as necessary. We welcome participation it's not necessary to be from an OpenAMP project member company do you please check us out and after you get to know more about the project and what we're working on if your company wants to become an OpenAMP project member it's not necessary to be a Lenaro project member company the member fees support administration for the project and infrastructure and what membership would get each company is a vote on the technical steering committee and a vote on the board so as Stefano mentioned we wanted to make becoming a member company really as easy as possible so all you would have to do is have a company representative sign the membership agreement in charter there's a $2,500 annual fee and this is our list of current member companies so we have ARM, Calray, Lenaro, Mentor, Nordic, ST, TI, Wind River, and Xilinx and hopefully soon we will have a 10th member company that's in the work and I just wanted to also thank everyone from the member company contributed some information towards this project and these slides Hi if you have any questions this is the right time to ask them we will be very happy to take any questions and answer them I can see that we have the first question already the question is about the status of large buffer transfer so I don't know the very latest and we'll have to get back to you on that maybe on the Slack channel after the talk I do know that there was a demo showed based on pre-shared memory and it was not then zero copy per se and I can also get back to you on whether it was using DMA buff I think it's probable that was using DMA buff on the Linux side any other questions on any of the topics I guess while we are waiting for any other questions to come in I just want to mention that the open AMP RP working group they have their next call scheduled for tomorrow morning at 8 a.m. Pacific I guess if anyone is interested in joining that ping me on Slack and I'll forward you the invitation the hi Francisco so there is a question on whether Xen will parse system advisory and that's a good question and yes so Xen should parse system advisory so one of the goals of system advisory is in fact is to make the configuration of an AMP system it's more I mean similar and aligned with the configuration of a static hypervisor so especially the static configuration of Xen wisdom zero less and guests that are pre-defined should work with system advisory same way the configuration of an AMP system would be done with system advisory so for that to happen Xen needs to parse system advisory to understand the virtual machine that he needs to start and you should also know that the zero less work so that the configure the advisory configuration for Xen to start multiple BM in parallel is already in a way a precursor of system advisory because it's following many of the same principles and idea also is not by the letter of system advisory yet so it will need some improvement and adaptation to support the future of the advisory does open AMP suffer from the share cash issues then solve with cash coloring so that's a that's another very good question so it yes whenever there is a share cash and typically when open AMP is used what may be the most classic scenario is between a cortex R and the cortex a cluster or between a cortex M and a cortex a cluster and there is no share cash in this case in these cases so the share the true cash that can be a source of interference inside a single cluster it will not be present in that case however if you're using open AMP to communicate between two virtual machine on the same cortex a cluster that does a share that you cash then yes the cash interfere an issue the cash coloring is addressing will be present so question from Matthew if there's any support from multiple processors or marketing controllers working on the same board but not on the same processor die so ST uses open AMP for their multi SOC solutions so I guess the answer would be yes a question from Andy I like the question when you have a system device tree what do you pass the data structure to if there is nothing running that that's a good question so well then with the premise that one day there might be a runtime usage of system device tree with then the data structure be passed the same way the device tree is passed so today is mostly using beforehand that would be a build time so you pass system device tree to lopper that will then generate normal device tree out of it and the normal device trees are passed as usual to Linux at runtime or for instance at are not those build system that will consume it at build time there are firmware however for instance you know an overall monitor of a platform that could consume system device tree at runtime today because this is one of the few components that actually need a description of everything that's present on the platform so that would be an example of something that could use system device tree right now any other questions from the audience so a question from Drew so in bigger board I am interested in different cores I'll use a communicate with Linux so the communication side of open up it's it's typically solved by setting up shared memory between the let's say the small core a cortex arrow cortex M and the cortex a core the memory is pre-shared beforehand as system configuration also where there is also f board going on in trying to make it more dynamic and flexible so so the mention of view boot so you know open up is looking at a number of interfaces that are useful on in an amp system so I'm so probably you would will not use a ring to communicate with the cortex are for instance it's not really typically needed but it might consume system device tree the system device tree is likely going to be passed to you would because in case of hypervisors or or for that kind of static configuration when there are multiple entities then you would need to be involved you want to pass a richer description of the system and you both is a typical one of the typical component that would need it any last question we still have a couple of minutes if you have any other doubts or question or comments and I guess if you think of any after the talk you can at mention us in the slack channel that was popped up on your screen a short while ago okay I guess thank you everyone for joining our call today and see you on the slack have a great day


What a great venue this is, but it's terrific actually, you know. I was going to start with a joke, but I have to tell you truth first because truth is stranger than fiction because fiction has to make sense. A couple of weeks ago, my wife and I were just packing up her Subaru to go to the airport to fly over to Honolulu for the American Psychological Association Convention, and it was about 95 degrees in eastern Washington at the time, and the handbrake was set on the Subaru with a very, very slight incline on our long driveway. As I put the 65 pound or so suitcase in there, at least it seemed like it weighed that much, I went back in to get more. It slowly began to back itself down the driveway.  Now, it's only about another 75 feet gaining speed before we get to a 20-foot rock cliff that goes onto the highway, so it gets to the rock cliff and off onto the highway. Luckily nobody was there, but according to people who stopped, instead of driving into it, it bounced off the nose, and as it bounces off the nose, the deck lid closes, carefully preserving the suitcase and all the rest of the stuff. It then bounces back on the tail, back on the nose, and parks itself almost perfectly parallel, halfway off the road in the opposite direction, so I get down there and I look at it, and there's no glass, it hasn't rolled over, so I get in, take the break off and drive it back up the house, change the suitcases, so it is total, I might say it is total, it didn't sound too good getting up there, but that's the truth of it all. So anyway, I got interested in REST before it was called REST out of my work in hypnosis. Most of my publications are in hypnosis, but I've been publishing in REST, oh, between the 1970s and early 1990s, roughly, so we're going to go back to the original starting things here and just give you flavor for some of this, because it shows you how hypnosis can improve performance in a lot of areas and how REST itself is adjunctive, not just by itself, in helping precipitate positive effects from other kinds of treatments. There was a time back in the 70s when one of the biggest impediments to using hypnosis with patients was the fact that not everybody is hypnotizable, it's an ability, it's about 70% genetic, and about 5-10% aren't hypnotizable, a bunch of people aren't terribly hypnotizable, most people in the middle, it's almost normally distributed and so on, so the problem is we want to increase hypnotizability. Well, a guy named John Zubeck at McGill University published a book I believe, 1969, Peter Zubeck will correct me if I'm wrong on remembering that date, University of Manitoba, thank you, thank you, that was, and that had a little section in it on how sensory deprivation would increase responsiveness to suggestion. Of course, it didn't actually measure hypnotizability, so I thought, well, you know, I've got to do this. Unfortunately, at the time, there were a number of studies that came out in the hypnosis literature where it was said that basically if you do an experiment with sensory deprivation, because you call it sensory deprivation, people are going to fake their scores, not intentionally, but it's going to be an effect of the setting it was told, it was sensory deprivation. So I wanted to find a setting that would be where we weren't calling it sensory deprivation, but yet we had an isolation effect. Another thing that was coming out was this idea that there was a correlation between waking eyes closed alpha, and it turns out it's actually high theta and low alpha EEG and hypnotizability, but some guy by the name of Dumas actually working out of Jack Hilgard's lab published this paper on, well, it's entirely due to volunteering, so people who volunteer for studies give you that correlation, but people who are drafted don't. I didn't believe that, but you know, so I thought we better study this. So now I have to find drafted subjects who aren't really drafted, who don't think they're drafted, and I have to find an isolation situation to see whether or not it increases hypnotizability without telling the hypnosis experiment. Now we have this pesky thing in Canada and the United States called the Human Subjects Committee, or the Institutional Review Board or whatever it is, I served on that by the way. What I'm going to do when I retire at 70 by the way is I'm going to take one of the old Nazi experiments, and I'm going to put it in the proper language and I'm going to run it through the IRB and I'm willing to bet that we can get one of those through, but we have trouble getting a sensory deprivation study through. So the answer there was, what I'll do is I'll propose this to the National Science Foundation, so they have this division of polar biology and medicine, and they accept papers from psychologists, and well, they accept the submission, but they actually don't fund psychology. They only fund polar biology and medicine. So I couldn't get NSF to fund this thing. So now I've got to find some place to make NSF fund this because they're the outfit that supplies logistics through the U.S. Navy and so forth to get Antarctica. So the answer is I send my Vita to all of the universities in New Zealand, and curiously enough, the University of Annabarie on the South Island, which is a jumping off point for Antarctica for U.S. logistics, hires me. Little did they know that I was going to be doing this. So shortly thereafter, what I discovered was the fact is that part of the trade for letting them use Christchurch and letting all these yanks invade the place is that they have to give them free logistics for the New Zealand Scott base, which is like only 10 people, 60 people in the summer, as MacBurra was in the U.S. base is 700 to 1,000, but you know, a big difference. It doesn't cost them much. So this was the trick. I put it through the New Zealand process, which was no trouble at all. And because they wanted somebody to do physiological work down there, so I could do that. So that was fine. So they got what they wanted, and I was able to do the hypnosis part at the same time. So this is how we actually forced NSF to fund my project. So it's a... So what we have is, does isolation rest, in fact, as we properly termed it, thanks to Peter Seinfeld, enhanced hypnotizability. It's increased a person's ability to respond to hypnosis, which is great for pain. Hypnosis is NIH approved for pain. It works as well as a lot of chemical analgesics and better than some, for example, and very good for a lot of other things as well. We'll talk to you later about using hypnosis for, adjunctively, as part of the ab reactive cure for PTSD, which we have two placebo controlled studies. We can do it in six hours with hypnosis now. How about that? We'll talk to you about that later. And how can we mask the subject?  So they're already drafted. So they don't even, you know, they have no choice, which is ideal, you know. And we don't have any pesky IRB to put up with either, you know. The only rule is you have to debrief them after the experiment. But curiously enough, at the time, they didn't even say how long after. Some of these people still don't know they're in this experiment, you know. So, anyways, what Scott Base looked like back in 1975, 76. And that's the EEG machine we used to measure the alpha and so forth. And that was supplied by the Sanii company from Japan, who we traded sheep pelts to for this, by the way. And they're very happy to do that. And they still, they advertised all this stuff down there.  And actually, it did survive amazingly well because the U.S. Navy dropped the box off the end of a front loader into a lot of other equipment. And it did actually survive quite well. At least none of the subjects complained about being shocked or anything like that. So that is the hallway on the right, which is about four inches of ice in it. And the labs are, the hallway's not heated, as you can tell. And the labs just go off from one part of the hallway, sleeping areas, and so forth. So basically, you would run on your normal Antarctic clothing, sweaters and wool pants and so on from one lab to the other. And basically, the game was somebody who was fully dressed to go outside would stop and start a conversation up with you and you're supposed to be tough and not be bothered that's 40 degrees below zero. So, and down the lower left hand corner, it was the only country then still using dog sleds. And the passenger there in the huge red outfit actually is, was the secretary of the Navy at the time, Middendorf. And the New Zealanders were going to play. And then we have now 60 photographers. You know, it cost 50,000 bucks then to bring people there. We had 50 plus photographers in the United States taking pictures of Middendorf. So the Kiwis decided, my good friends aside, they're going to set them up and let him try and drive the dog sled. Now our dog, the dog sled people in the zone are terribly great. And he just said, well, I guess I could try. Anyway, he did perfect figure eights that turned out he had spent quite a bit of his life in Alaska. So he had no trouble with dogs at all. He gave up the shrieking whistle. So I clapped for our side and the owners are very depressed about that. And the side on the right there in the bottom right corner, that's me and Gep Nordhill, who is the head of the Detachment Delta. He was also a good fun pilot to fly with. So that's Mount Erebus. That's the huge mountain near Scott Base and McMurdo that New Zealand Airlines crashed a DC-10 full of paying passengers into. I actually wrote an article suggesting that they shouldn't conduct these flights because DC-10s do not make low-level good sightseeing aircraft. But it wasn't, people didn't pay attention to it. That's one of our planes at the C-130 ski plane landing and some little background there. And that's a Waddell seal on the right. And they get fed to the dogs.  And that's the end of that. They have special permission environmentally to do that. So anyway, let's get back to the data here. So the big thing is I won't bore you with all the data because you won't be able to see the numbers anyway there. But Antarctic wintering over isolation did increase hypnotizability and we used a scale that didn't involve direct hypnotic induction with it. It was a significant increase. So we discovered there is a link between isolation and increasing hypnotizability because a person gets to be more internally oriented when they might not be otherwise. That's how they put up with it. Isolation in the winter is basically they're nozmic to all odors except the odors in the base which are cooking odors and some restroom odors if you will. And that's about it really. And they have 24 hours of darkness during the winter. So there is quite a bit of isolation going on. We also did alpha EEG density increases there. I had a really good picture of that but I don't know what happened to it. We actually practiced any prison in New Zealand because the space for three of us to work, my two technicians and myself plus the subject, we had very limited space to work in. So we spent a lot of time doing that. So now that we have it established and we know the drafting doesn't make that much difference, it was now time to see whether we can do something practical that would be useful clinically. So this is my lab at the University of Canterbury in New Zealand. And that's also the EEG machine. So we measured in this particular study. This is six hours of rest. And this is we did this back in the late 70s. And we measured skin conductance and peripheral skin temperature and core temperature. And we did EEG measures so we could do the alpha density and measure theta and a lot of other things like that. And we had my assistant there, Kate Abelson, after we'd closed the door. By the way, we used female subjects because they had better bladder capacity than males. So the ones that can actually last six hours. Great attention to detail here. So we took nursing students and they all did fine with that. And as we closed the second double-handled door, which are basically these are doors they use like on freezers, you know, kind of things. The Kate would look to me and say, well, do you think she'll crack? You know. And so we monitored what the craving for stimulation. They'd push a button if they were getting bored and we'd give them stock market quotes. The same three stock market quotes over and over again. So we had a criteria for moving them from rest in case they were having a real problem. So we had three criteria. They had to show three criteria for craving for stimulation. Some of them would try to count the holes in the acoustic tile. And then the people would go for the stock market quotes. Basically, a remarkable thing is we only took one person out at about five hours instead of six hours. So we didn't have this horrible effect that we were told was going to happen from sensory deprivation, you know, and they came out and said they really liked it. Now the interesting thing here is we measured this with a real hypnotizability scale. One that had just come out at Stanford called the Stanford Hypnotic Clinical Scale. And it was only five points. We embedded that scale in dozens of other measures. So it wasn't like the primary focus, the idea that they couldn't complain about the study. People figured out it was about hypnosis because it was a hypnotizability scale because it was just one of many, many, many scales they took. And then we measured them before and then before we took them out of the chamber. And then we measured them 10 days to 14 days later. And also the idea is well of course anybody can after being saying well in your hands or are feeling like his magnets attracted to each other and they're moving closer and anybody can fake that and they kind of figure out what you want to do. So we thought we better have a real criteria. Well so we added a pain suggestion for increased pain tolerance and used a shock device. And the incredible thing is for pain tolerance that this thing will only go to 900 volts. I mean we're talking, we put them back in the hand, they should go out like this. And we had people that exceeded pain tolerance with the suggestion for increased pain tolerance. They would feel if the hand would be entirely anesthetized be like leather as if the electrodes were sitting on top of leather with that hypnotic suggestion after. So we had the pre and post measures. We also did something called pain threshold which turns out to be a real problem in terms of really measuring it. So here's the data. The scale is the Stanford hypnotic clinical scale, the five point scale. But I wanted to make the graph look really nice. So if you just multiply the pain threshold and tolerance scores by 10, you can put it all in the same graph. The point was the pain threshold, there was no change in pain threshold at all. And that's kind of a bogus measure because we don't know what the pain threshold to one person is not to another person. That's been abandoned literature. We use things called ischemic pain and cold presser pain now. But the thing is hypnotizability went up from 1.7 average score, mean score to in excess of, it was actually 4.2, it says 4.0, there was actually 4.2 in this first study. And it was maintained at 10 days to two weeks. So once they learned the skill, they were actually able to do this, which is pretty neat. Actually, we actually tested me on this, by the way, years later in my lab at the University, at Washington State University, using the 12-point scale. And the scale that's 12 points is, this is the Stanford hypnotic susceptibility scale. And there's a lot of research on this. It's actually the work that Hilgar did over 20 years at Stanford. It helps to be dean first. Then you can do, they made his name in behavioral research in learning theory, became dean and then gave himself the funding and the building to do the hypnosis research.  And so they developed these great scales that are very reliable that you can use, but they're not, they're good for research settings, they're not very good for clinical settings, so they take over an hour. But there's, one of these items is called anosmia to ammonia. And you take this bottle of ammonia and you tell the person in hypnosis, after you've been exposed to hypnosis, and they've already passed these items that they're going to have, they won't be able to smell any odors at all.  But since the sensory deprivation thing worked, I figured, you know, it took me 10 years before I figured I actually do myself, so they ran me as a subject, so we got to that particular item nine on the Stanford scale.  So I thought my graduate students were completely putting me on, so I opened my eyes and sure enough it actually was the ammonia. I was quite amazed, actually, because my expectation was that that was a fake, and it really came out pretty well. So pretty interesting. Anyway, that's the hypnosis part, which we used to call animal magnetism, and so you have, it's a downside of animal magnetism, I guess. So let's move on in time here to dry flotation, use a dry flotation test measures for increasing performance like marksmanship in this particular study. We used 24 students enrolled in a marksmanship training class at Washington State University, and he would nine males and three females in each group, and these folks were pretty much plateaued at a score of very continuous scores before we started them. In other words, it wasn't like an intermural group of people shooting for fun. These are ROTC folks that are really trying to get up, and they pretty much plateaued really good people, bad people kind of between, and so this is where they were, so we were able to match the groups within three points, and then expose them to rest. We used dry flotation. The one advantage of dry flotation rest is that it's a terrific interim method to get people. I have both a wet tank at the time, dry tank, and also we still have a chamber in my laboratory. I'll be retiring soon, so my lab is in the process of closing, so I'm actually selling my dry flotation tank now. The advertisement for that's out there. And the deal with this is the dry flotation tank comes with a lot of frills that people like, which have nothing to do with rest.  It has these fabulous Danish stereo speakers in it. It's a sand-filled wall. It's a sound vibration damping. It's really good. It's a super low-tactile kind of plush material that sits over the top of it. So there are people who would never get into the wet tank. You get into this thing and they say but there's something even more. And by the time they do this they're more likely to get into the wet tank. We've had some of those little transition things. We didn't publish that though. It's kind of interesting. With the dry flotation we actually use, we have to have the, we warm the water to not, not roughly 92-93 degrees we do in wet rest but about, roughly about 95 Fahrenheit for doing that because of the, because you've got more of your bodies exposed to the air. And we use this negative ion generated charcoal filter there just like you do in a lot of the wet tanks as well. So a lot of that's exactly the same. That's what it looks like. And that's finished in lemon oil. So you don't have any petroleum byproducts evaporating inside the, inside the room or inside the actual chamber. And this is a deal for performance on top. It's a, a piece of tempered glass where you can put a video. So if you want to have, demonstrate golf or, you know, proficient race driving and that kind of thing. I, I did that before I ran the Fermilantic race at National Championship Race for myself and actually unfortunately imprinted on a guy that was slower than me. But we won anyway, but nonetheless it was, you know, and that's what it looks like. There's, that's the speakers for the front and as, you know, person, the subject can, can adjust the, the amount of ventilation and can adjust the, they can actually turn the lights on with the dimmer if they want to, you know, anytime. So it's an environment which is a pretty inviting environment compared to some of the other ones. Good transition environment and works, it replicates the results we get with chamber rest, which you cannot obtain with some of the, with, with wet rest in some cases like hypnotizability changes and some other things. Oh, there's the, the Danish speakers in the back end of it. So the control condition, by the way we use, we want to use a control condition which is a really legitimate control condition and I think most people know that hypnosis, although hypnosis does not require relaxation is probably a hundred studies, well maybe 200 now in, in tier one journals like international journal of clinical and experimental hypnosis, journal of abnormality, which is showed that it gives tremendously effective relaxation effects. So our control condition was actually a relaxation condition and then we gave him some BS from how relaxation enhances your marksmanship performance, which isn't really told the BS, which was basically just information on that. And we just used for, so we could replicate this, everybody, we just read the first, the induction from the Stanford clinical scale, which takes less than five minutes to read the hypnotic induction for that.  So it's, it's a lot of effect there. The experimental group was, I'm looking at the salt replica here and it's giving me a PTSD traumatic response to cleaning up my lab every time the pool people come by. We had, Washington State University was plagued by the pool inspection people coming by at random intervals as well, you know. So constantly they're trying to clean up the salt, but hence my fascination with dry flotation rest for a period. And so anyway, we'd orient them to the dry flotation chamber and they were only exposed to 50 minutes of dry rest. And this is, this was in the unlighted condition. There is no attempt to provide video or any of this imagery or any of that other sort of stuff during or after rest. And they were simply assessed within 48 hours. And what actually happened then was the that was all done under the ROTC supervised as instructions. And then we said, you know, is the shots are fired from the same unsupported prone positions, all carefully controlled when you used these national competition targets and so on. Then the targets were scored by these ROTC cadet instructors, but they did not know who was in the experimental group and who was in the control group, you know, which is the way you're supposed to do this. So here's what actually happened is the rest condition, only 50 minutes of rest, one exposure, at least within a couple day period, showed marksmanship improvements in people who had already plateaued on marksmanship. That's the important thing. They're already plateaued, they weren't improving any more as a result of instruction. So that's kind of, that's pretty cool. Peter Sudfeld did a basketball study and we did a basketball study. So this is a dissertation by Jeffrey Wegeman, WSU, and we had 22 expert collegiate basketball players from what was then PAC 10 team WSU and then also the University of Idaho, that's only about nine miles from Washington State University. So we can see these are really expert players. And we had all sorts of objective scores. We had coaches that didn't know who had rest and who did not have have the rest condition. And this is kind of interesting study as well. The student in question wound up being put on probation for doing this. It drew so much excitement that he got a newspaper inquiry and he revealed the name of one of the people in the study. And it turned out to be Brian Quenette. I'm going to reveal it again because it's already been revealed. You know, this is not new news. Who managed to score after one hour in rest 60 points in one game. 60 points. By the way, Washington State University still had the ability to grasp defeat from the jaws of victory by putting in people after that who hadn't been allowed to play before and we still lost by four points. Yes, we can only do that at Washington State University. It's remarkable, you know. Anyway, I think Brian's retired from the NBA now, but he gave any way to releasing was, you know, University of Washington to watch up because WSU has a tank and of course it was downhill from there, you know. So anyway, we did another study. It was a tennis performance study and this was Patrick McElaney was the PhD student on that one and we had significantly improved game performance and this is also measured in intercollegiate competition and we used imagery plus rest versus imagery alone because the imagery condition also had some positive effects as well. So that's pretty neat stuff. Last one. Oops. Oh, here we go. So the dry flotation study, this increased hypnotizability and pain control is the first study that actually used dry flotation rest for increasing hypnotizability. Wet flotation rest did not work for that. We tried it four and four or five different experiments had no significant results. Apparently, wet rest is perhaps too much fun. You know, I don't know. So we tried lighted and unlighted conditions and one of the problems with long periods of rest like six hours in a darkened condition that people fall asleep and you'll lose the rest effects. So we tested lighted and unlighted conditions and we used the stand for hypnotizability test scores again test before and after in a two weeks follow up very much like we did in the New Zealand study and we used a much better measure of pain to use a pain criteria. It's called ischemic pain. This is a deal where you put the blood pressure cuff on the subject and you inflate it to is it 240 millimeters or mercury or something like that. And then you have them squeeze a hand dynamometer to 10 kgs. Anyway, this creates a very painful situation which is considered to be similar to post-operative pain. And you'll ask the person to report over a minute like on a one to 10 where 10 is a point where you'd like us really to take the cuff off. Tell us how you're doing. You know, say one, two. People who are not in the rest condition three, four or five and you know, 10. Oh, please keep on reporting. Most people can do this. 12, 13. People in the rest condition with the pain tolerance increase. We had people that had had these kinds of scores over that minute and a half. You can't leave it on much longer. You do tissue damage. Not a good thing. Blood vessel damage. We try to take good care of our subjects and minimize the tissue damage. The interesting thing is again the dry flotation rest increased hypnotizability and pain tolerance. It had with this idea of pain reduction with rest by itself hasn't been tied into this kind of work. And that was kind of one of the things we're going to do next. So running low on time here. I'll plug my books. The left one is by hypnotherapeutic techniques book which is now the National Text for Medical Schools in Romania as well. You know, translated in Romanian. It's with John G Watkins who a lot of you have heard about just passed away about a year ago at 98. And the next one is the advanced hypnotherapy book which is the more psychodynamic one and then the one that just came out in 2010 is the medical hypnosis primer for people who don't know anything about hypnosis. So there we are.


For those of you who prefer to interact comment as questions and basically hear more about me on Facebook and that just seems to be the common trend right. So the Facebook group that I have created, which I guess I can share my screen I never thought about that. I can show you guys what that's all about it's basically for all things dental okay so it's going to be for dental professionals. And students who basically want to learn more, so let me share my screen and show you guys what it looks like. So this is it, it is just called dental little tutoring because that's my company name i'll leave the link for you guys on the bottom I tried to. Change the link to like you know Facebook groups dental l but I couldn't figure out how to do that, have they taken off that capability, I don't know. Look you guys there's two members so far, this is going down in history, me and Sophia I gave her a shout out, she was the first person to join super quick. I posted a link, because I did have or I do have a Facebook page a dental l tutoring Facebook page. But i'm starting to realize I can't hop on live in a page I can't interact with anybody in a Facebook page so it's more for me just posting. And you all watching that's no fun I like to interact, I want to be able to answer questions. I want you guys to comment, I want to be able to come on spur of the moment and do a live video, so I can do that in a Facebook group. So there's going to be incentives as well, so for those of you who are in the Facebook group. You will get certain things that those of you maybe won't get if you're not in the Facebook group i'm going to offer sales i'm going to offer like additional fun stuff. Any of that, but first and foremost, you know the best part I feel is you are all going to get unlimited support by me, I truly. I love mentoring I love teaching for dental professionals students so dental assisting dental hygiene i'm truly here to help because I started off way back in the day, one day to. You know, even me starting my own dental hygiene practice, I started off one day to not knowing what I was doing. I would have loved full support by somebody who had the time to give it to me and answer my questions so a Facebook group like this one here just allows me. To have everybody's questions and comments together, and I can help you guys with that, but don't worry i'm still going to be on YouTube. Just as much I do upload videos at least a couple times a week, please make sure to click like. And make sure to subscribe to the channel that does truly help me it does help to support me so that I can keep on doing this so. Make sure to join i'm going to leave this link for you down below because it's like 5549836 oh my gosh it's a long link. So i'm going to leave it down for you guys below, so you can click on that to join I look forward to seeing you guys inside the Facebook group, you can comment post anytime so thank you guys for watching and i'll talk to you guys very soon.


In the body, we argue about whether certain spiritual gifts have ceased or whether they have continued. Continuations believe that they have continued, sensations believe that certain gifts have ceased. I am one who stated that I am a biblical continuationist. What does that mean? A biblical continuationist is someone who believes that if someone has a particular gifting by the Holy Spirit, then it is going to continue exactly, and there's a key word, exactly just like it was in the Bible. If you have the gifts of prophecy, it's not a partial prophecy where 20% of it is true or you're right half the time, no. A prophecy is specific, not vague and exact. If you have the gift of healing, well then the person is healed when at that moment someone has the gift of tongues, well in the Bible tongues were languished. Today it's gibberish, no. A continuationist believes that all the spiritual gifts, if they are in play, will continue just like they happened in the Bible. Otherwise, if you think the gifts are different and aren't exactly like that, then you my friend are a sensationist.


All right, lady, let's go right into new products. You ready? That's right.  All right. So first up, it's revision. Yes. This is revision and this, you might say, Hey, wait, you already did this revision. We did do this revision. Who did it? This is the two five nine zeros. This was the Metro mini V one. And then what happened is we couldn't get the package for the Metro mini V one, which was a 32 pin QFN. And so we're like, well, we have to do a hardware revision to get with the 28 pin QFN, which we could get in stock. So we did the V two. And then we finished the V two. And then we're like, well, you know, are we going to make the V one anymore? We finally sold out of the V one and realized, well, no, we're probably just going to sell the V two because it's pin compatible, except it adds USB C, which more people wanted. And Stem IQT, which means you can plug and play sensors onto it like so. And we thought, Hey, let's just make the V two instead of the V one. So if you were going to purchase product number two five nine one, you will no longer get the V one. You'll only get the V two. We're not planning on making the V one anymore because again, this is pin compatible. And we think is an improvement on the design. Yeah. Okay. Okay. Next up, we've got more magnetic cables. These are simplified magnetic cables. We put in the store magnetic cables that were USB C to C, micro B or lightning. These are USB A only. So you can see there's only four contacts. It makes them a little bit less expensive, but they're still really cool magnetic cables. And let me tell you, I use these a lot. So let's go to the overhead and I'll show them off. So we got them in two sizes. We got them. I'll show this. This is the one meter long, but just imagine I have a version that's two meters long. So that would be the other version. So nothing that's nice and not only is it so it's only USB A is sync and power. So you get both. So you get all four signals. Thank you for zooming in. You can see the four signals and then you can get micro USB tip with it. You get a lightning tip and you get a USB C tip. And this is great because I actually have a lot of devices around that. I have a charging station. And so, you know, I plug this in. This actually lights up normally, but I didn't like to bring a USB charging thing here to plug this in. And this is actually reversible too, by the way, so you can go either way for it or backward, but it makes something that's not reversible, reversible. And, you know, you just click to charge it. So like these are these are like my little, you know, like back and body massager thingies and I use these all the time. And so I'm constantly charging them in this way. I don't have to like fiddle. Also in the dark because you need to do stuff in the dark and you can't. I have baby. Yeah. And also, I don't know what it is, but, you know, USB for whatever reason, it takes three times to plug it in. So, for example, I have like my charging cable and it's like sometimes I'm charging my phone and or I'll charge my massager thingy and or like my pumps, you know, same cable, three different ways. So I actually kind of like that it comes with one of each. Yeah. I'll say at this moment, we don't sell the individual chips. We just sell the one with all three tips. If people really demand it, we'll carry the individuals. But I kind of feel like usually want one cable per three devices anyway. Yeah. So next up. This is the two meter version. We have it bigger. So that's the difference. If you can tell, I'll say, you know, if you can get away with one meter, you'll get better charge rate because anytime you have a two meter cable, it is just longer.  So it's not going to charge as efficiently. Also, don't forget, if you look at the quarters on our product pages, it's all the American women quarters that are up. OK. Yes. Next up. OK. Next up. Oh, we have a new product set from Espressif. They kind of sent us these FedEx really fast, which is cool. So this is the ESP32C6. Yeah, this is new because you're like, wait, I don't know. There's a C3 and there's the ESP32S2 and what's the C6? So the C6 is a risk five based ESP32 chip. It has Wi-Fi and Bluetooth and it has Wi-Fi 6 compatible. I'll be honest with you. I don't know exactly what Wi-Fi 6 is. I got to research it. However, this is their new chipset. It's a totally brand spanking new. These are engineering samples. They're not meant to be put into final board designs.  They're cool with using the IDF because you need to use IDF 5.1. We have two version of the modules. We have the eight megabytes and the four megabyte and the photos look identical. But one has four megabytes of flash and one has eight megabytes of flash. These are identical photos. They're identical photos. Look at that. Yeah, sorry about that. Look at that. Look at that. Honestly, we we're waiting for the eight megabytes to come in. The fours are already. They're very similar. They're very similar, basically the same. All right. And then we also have the Valboard, which is over here. Yeah, so I got to. Yeah, it's OK. It's this one that clicked here. Yeah, sorry about that. It's fine. No, because everything looks the same. Everything's like black. It's very similar. OK, so this is the ESP 32C6 module dev kit. So you get the C6 module on the right. That's your risk five chip. Then you've got a power supply. The looks like the LT 1117. You've got a two USB ports. And the reason you've got two USB ports. Oh, great. Yeah, I get two USB ports, but I want to see the overhead here. The reason we get the two USB ports is it has native USB, just like the C3 does, and it also has a built-in like the UART. So there's a CP 2102 USB to serial converter chip. Use that when you want to like do debugging so that you can mess with the native USB on the side and you don't have it like coming and going. Sometimes people find it easier to debugging through the UART because again, there is like a JTAG, but a lot of people don't use the JTAG on these these dev boards. They just use the UART for debugging instead using the IDF debug system. There's also the reset and boot buttons. It's breadboard compatible. Didn't mention this is for engineer and developer use only. It's not it's not for people who are like, oh, I want to have this one Arduino circuit, Python, micro Python. Ain't nothing on it yet. Arduino support isn't even merged yet as of this video. Although I saw there's an open GitHub ticket for it. And I think it'll be added within a couple months. C6 is very interesting. If you're a risk five aficionado or you are interested in Wi-Fi six pick up these or the modules, but I just have to warn people at the time of this video, they're not for beginners. OK, and then the story of the show tonight besides you laid out our team, the customers and more is. The new ESP 32S to reverse TFT feather. That's where the code is. TFT. So this is a lot like our ESP 32 TFT feather, except you'll notice that it's the TFT is on the back of the board, not the front of the board. So reverse. But this also means there's a little bit more space, right? Because I'm not sharing it with the USB and the whatever. And so on the back, you've got the ESP 32S 2. You've got a stomach. You T for it's got a little protector on it. But I think if we, well, look, I'll show it on the overhead. And on the front, we've got the TFT. It's a 240 by 135 pixel RGB TFT with IPS. So it's a very beautiful little display. You communicate with it over SPI. You've got the reset button and three IO buttons and the D zero button is also the boot loader button. So if you ever need to enter the boot loader manually, it's also available. And on the reverse side here, yeah. So you got on the left USB C, you've got another reset button in case you need another reset button. I was like to keep it there. Yeah. Battery charging. Oh, something new is I've updated these feathers. We used to use the LC 709203 as a battery monitoring chip. We've moved to the max 17 048. Shouldn't really matter too much for you. It's just, it's a very nice ultra low power battery monitor. Go back here. I remember there's a neopixel on board. There's a second regulator. So you can turn off power in the neopixel and the static UT port for ultra low power. We're using the RT9080 regulator on these boards, which means that the power goes down to like 30 or 40 microampures when in deep sleep mode. Hackaday has a low power contest with DigiKey. And they have these little, the illustration is these little energizer looking bunnies, but they're robots. Okay. And it's how low can you go? So you could probably look at a bunch of low power stuff from ATV fruit and just win. Win. We're not judging. We have nothing to do with it. Enter and win with ATV fruit stuff. Win, win, win, win, win, win. Do it, do it. We will eventually have an S3 version of this as well, in case you're like, hey, I was going to be S3 version. We will, but we start with the S2. I thought maybe I'd show it on the overhead. Yes, or on the overhead. We have to do some overhead practice. Yeah. So let's go this part. Yes. Thank you for on zooming. Yeah, that's the sound that we're going to do. Okay. So, let me just move this protector. And then I'm going to go zoom in again. Hold on. Let me see. Whoa. That's cool. You're using, you're doing it in Zoom. Can you zoom? ESP32 S2 module. This mini module has four megabytes of flash, two megabytes of PSRAM. It's great for Arduino circuit Python use that PSRAM makes it excellent for IoT projects because you can buffer your gigantic JSON data. Like I mentioned, there's a Max 17 048 battery monitor. It's ultra low power, but you just get really good battery monitoring on it. It'll tell you the percentage and voltage of your LiPo battery when in use. I got these nice big buttons in these days, the new Penguin font. So nice, legible, sans serif font. Secondary regulator for the Stem IQT port so you can have sensors and then depower them for ultra low power usage. This is the main regulator, battery recharging, JSTPH4 battery for portable projects, USB-C, and then as we've mentioned, this beautiful font screen. And three buttons. Let me see if the, I've got a battery here. I can demo it. I do have a battery here. Hold on. Let me see if the batteries are running. Okay. So this is the demo. So if I have I2C devices, the I2C 36, that's the built-in monitor reset button. And then the buttons D0, D1, and D2. What's that spot for a chip? Yeah, I think so. There is a chip. Stem IQT vertical? Yeah, there's a, it's a vertical Stem IQT yet because there's no other way to have it. But this smells so good because it means anything comes out the back. This is for a BME 280, but we don't actually place it on there. It's just sort of a vestigial sensor. One thing just to note for the sensors is the D0 button, when you press it, it shorts to ground the D1 and D2, purposefully short to 3.3 volts. So the reason is, is we learn this with the MAG tag. For the lowest power deep sleep interrupt wakeups, you want to have the power switch connect to power, not ground. And this does a better job of allowing you to have multiple buttons trigger different wakeups. Like if you want to have multiple GPIO trigger wakeups. So that's why they're, if you're like, why is D1 and D2 different? That's why they are. And yeah, we'll also do an S3 version, but I wanted to get this into the shop to start. But I think this would be great for panel mounting or a case, you know, yes, the battery sticks out a little bit, but you can kind of fold this under and it's slim. And you can still use feather wings. You just stack them on top of this way, right? It's, it's stacked backwards. So if you want to add ethernet or whatever, go for it. All the TFT control signals don't go through the GPIO, just the SPI. So you have all these pins available. And that is new FedEx reverse.


was in 2014. Let that sink in. We never, ever, ever, ever, ever lose. We'll take a massive break from battle. Back, this is the first battle of Don't Flop Small Room Sessions, volume number two. We are here at a tone coffee shop in Wilson. Please make some noise, everybody. 40 tickets for this event, big up. All of the 40 ticket holders, shout out to the guests as well. Like I said, you can come, have a coffee, have some alcohol, have some food, that tone coffee shop makes you check it out in the description. Let's get into battle number one of the day. It's a beat fighter tournament, semi-final.  Left-hand side, please make some noise for my brother, one, four, two, let's go. Yeah, all right, we've got three rounds, shout out to DJ Policy on the decks. Round number one, verse number one, it's on Bilzar. Let's go. Yes, yes. Don't flop. Yeah. Jet me.  Duck down, go get busted at the reddit.  Come through straps and both arms like a rucksack. Shit!  Duck down, go get busted at the reddit.  Come through straps and both arms like a rucksack. Boring. Said this guy's boring.  We don't wanna hear your story, like everybody in the whole place do awkward.  Sad like an orphan. Come with depression whenever he's talking.  So when he's bitch, just ignore him. Also awkward. You want you to pause, fast forward. Skip his bars, eyes showered.  Got a man's watch that'sック and I'm all in the corner. Where's your enroll now? What you gonna call up with your old weirdo, you probably bought in the new dunk flop? Tee Diga bought a batch and a whackt like that.   Have kept the horses, you're never spring drummed.     Me, I would've killed the holder, then brought Danny Jack back from the grave with your tune, that's how I wasted my tune.   What are you enjoying, pleb? You got to take my intercepts, that's about the best. I mean, you're not on the same level as Daidalec, but then we got Matt stuck in the tourney.   And I'm happy to be… The best of me are not on the same level as Daidalec, but then we got Matt stuck in the tourney.   And I'm happy to be snapping these rappers who've grown taller than me, when they haven't done anything better than me on a beat.


you guys show day today I know I didn't put out a video earlier but this serving as that video I want to go live with you all and talk to you all about all about what exactly I'm doing so I am here in beautiful New Orleans if you guys can see the background we are at the APA conference it is in New Orleans this year put that for you guys also I can show you my badge that's me hi fancy Nancy and so these are all of the little tabs you can put on for your APA badge but I'm here in New Orleans just kind of having a good time it actually feels really good earlier it felt kind of like humid and warm but it's nice now there's a really nice crosswind and I've just been taking the site but I've also been at the conference and so for those of you who don't know what the conference is about this is an opportunity for the pre like PE students and the PAs that are currently in the profession to meet and greet with each other but also the PAs can at these different conferences there are different sessions going on hi Elijah there are different sessions going on where you're able to do your CME because you have to have a certain amount of CME hours each year which is continue your medical education as a PA so the PAs can fulfill that at APA and then as a PA student myself I'm able to go to all these different spark sessions where I'll learn information about like kind of surviving clinical year which is really big for me because I am a newly mingted PAs too you guys that means I finished my first year of PA school and I'm going on to clinical years so it's very important for me to understand you know how to transition from that didactic year of learning and now go into clinical year of learning and this that's something that they do here as well thank you so much I don't know could you spell could you say how to pronounce your name I think it is just phonetically because you know I don't want to butcher it but I think it was I hope so anyway but thank you guys yeah it's you know it was a long road a really long process look at me I'm kind of that okay I got am I saying right I think I said it right thank you but it was a long process but you know I made it I'm here and I'm able to now kind of to see where I could possibly be in the future by looking at some of these future PAs that have been some of these PAs that have been in the game for a long time thank you so much the PA handyman thanks you want to start your YouTube channel as well on your journey where are you at with respect to your PA school journey are you currently in PA school or your pre-PA student or you know where are you at but you know with respect to YouTube and starting a channel it's just about doing it you just have to kind of do it but yes so I've done these sessions and it's been pretty pretty good hi M8 MD your PA how are you first-year undergrad okay well yeah you know um now's a good time first-year undergrad you can talk about that whole process of like figuring out the whole prerequisites and all of that that's pretty well that those are really good stats so definitely go ahead and try and work something out with respect to that but yeah as far as the conference itself so I have been going to different spark sessions I went to surviving clinical year and I also went to like an emergency medicine one they were very very informative really really good information and I think it's so so so important to understand that you should be prepared you know I'm going into my emergency medicine it's gonna be my first rotation and so getting this information from these well seasoned PA's was very very informative and really essential to me oh I'm the goat okay thank you I appreciate I'm really humbled by that thank you I don't think so but I do appreciate that you know I'm just trying to help you guys out and just document my journey thank you Grant thank you so much applying you're trying to apply this fall I wish you many blessings with that I'm applying this fall but so after those look oh look look at you guys it's up there in the background and to the background hi baby yo she's gonna have a bomb vlog coming for you guys yes we got a very very bomb vlog New Orleans you're gonna love it but yeah apart from those sessions there's also a general session that you go to Elijah what's up and there's also different things that you can pay for like to learn how to teacher and those things like that so it's very it's very it's pretty cool actually and if you guys ever want to attend a conference go on over to a pay it out or our next conference is gonna be in Denver so excited about that and I believe the following conference is gonna be in Nashville and it happens annually so definitely look into that because it's something that you should at least do at one point or time in your EA like career I guess you can see and they do welcome other professors as well physicians and then these are welcome to the conference you would just have a different badge like I have the student badge with my little student in there but you would have whatever your badge whatever your thing is you two little boys let me see if I can see that this is you two little boys how do you do it I do it with the help of aunt and helps me out a whole lot you know having the two girls a lot of like oh guilt that I'm not giving them enough time but you know you're doing this for them as well it's not just for you but it's also for the betterment of your family and it's only for a short period of time you know one year really studying at minimum and then definitely continuing that studying through clinical year but you have a little bit more time to give them in that year so I think it's a good trade-off honestly for a better life spending a little bit of two years out of your life you know studying in me feeling a little bit of guilt I think that that's generally okay and I guess maybe that's what I'm telling myself so I feel good but that's kind of how I do it I have a great support system great vlog coming out about my experience here just meeting all of these different PAs that have been in the game for a minute you know PAs that are in positions of leadership and just networking with them it's been such an amazing experience and I'm so grateful that I was able to do it I wanted to come on and say hey you guys really really quickly and just say thank you guys so much for following me on this journey I don't like I can't believe it y'all we've been on this journey for like a year now I'm in my second year you guys have been with me for a year and it just seemed like it flew by so I just want to say thank you guys for doing that and I will see you guys next week with the vlog hopefully you guys love it and appreciate it and I'll come back and oh guys and I got to interview