Electronic communications form an important part of any advanced society. Mescitadel Think Tank, of course, will have the very best. Such as wired intra-net networks and wireless communications for both personnel and droids. And naturally all realize that reliability of such communications are vital for its usefulness.
Their is more to such communications than just your hard wire interface. The communication protocol employed is what actually determines the transaction performance especially under adverse conditions and the communication environment generally is adverse to one degree or another. Adverse conditions usually force retransmissions to occur and these can rapidly dissipate performance goals and how much so depends primarily on the selected communication protocol.
I encountered these problems front and center when I interfaced my lab node real world interface, based on the 8051 microcontroller, to my PC using the built in UARTs provided in the hardware. I found that some commonly used protocols just weren't adequate for the electrically noisy conditions that it is required to work in. The excessive error rates made the communications vary from too snail slow to impossible.
This is when I developed my new NiComm communication protocol. Absolutely the best you can find anywhere in the world. Bulletproof reliability where you would usually find none. NiComm is excellent in its ability to maximize the communication rate no matter the conditions. This is a technology that will be used extensively in Mescitadel Think Tank communications.
The device I used for this development I call my lab node and it is based on the 8051F120 MCU. It is an in-expensive development kit that can be connected to a PC and includes programming software and such however it does take knowledgeable skill to work it. It is an impressive device for real world interfacing and has all types of D/A and A/D and timers and such and in my opinion it is the best commercially available chip of this type. An excellent choice to connect to a PC as a slave device to give the PC real world interface capability so as to control a wide spectrum of processi.
The documentation is adequate and it is programmed through a JTAG interface and it includes a USB interface. Everything you need to work with it. However I am disappointed about a couple of things with this device. I would prefer it was 16 bit instead of 8 bit and the programming software that came with it had a rather small size restriction however an industrious and determined programmer can work around these handycaps or you can buy software that has no restriction but that can get expensive.
It has several communication options such as RS-232 and if you're really determined you could wire in Bluetooth and Zigbee. But the communication ports of this device is straight hardware and you have to do everything from hardware configuration to software drivers.
The term NiComm is the property of Mescitadel Think Tank. This is an information release describing the progress of the development of a technology vital for the construction and operation of communication systems.
Tuesday, August 21, 2012
Thursday, August 9, 2012
Gizmo Technology Center.
The term "Atlantis" is depricated.
Yes Atlantis Technology Center is what I call the building in which I do all of my research. And this is something I have much ambition in that I want to improve it. Anyone who sees it now knowing what goes on within might wonder if it is like something in a James Bond movie, you know like it looks like a dump on the outside but within it is an impressive facility. Not quite.
In case you're unaware Atlantis is meant to be a place for Messians to live in peaceful existence in the midst of a regressing world.
Actually I do have every intention of constructing an impressive high tech facility for doing most of my Atlantis research and engineering within. And I did say construct because I want to use it as a proving structure for high tech construction technology that I research on. This of course will include a wide variety of man made materials that are far more resilient and fire proof than the usual materials that you would find in a large structure. Of course with a structure such as Atlantis would you expect to find any different?
Of course their is the problem of location and this could actually be anywhere in the world. It just needs to be a place where the work can get done. However I do admit that relocating now sounds good but readiness/finance issues and physical health problems make this option unattractive at the moment.
Then their is the issue of seclusion and privacy. It is my every intention to become totally hidden but considering the size of Atlantis just how long that can be done will remain to be seen. Never the less I'll not rule out the possibility that Atlantis will not be built on the Earth at all.
Developing these technologies is going to take a long time and actual construction will not begin until everything is in readiness. This being so the actual construction of Atlantis should progress relatively quickly. However today's research is centered around fundamental microcircuit construction technologies and software. Technology that is recognized around the world as legitimate and desirable.
God told me that I have a long walk ahead of me. I'm hoping to begin the actual construction of Atlantis by the year 2030. And yes if you are asking I will live long enough.
Yes Atlantis Technology Center is what I call the building in which I do all of my research. And this is something I have much ambition in that I want to improve it. Anyone who sees it now knowing what goes on within might wonder if it is like something in a James Bond movie, you know like it looks like a dump on the outside but within it is an impressive facility. Not quite.
In case you're unaware Atlantis is meant to be a place for Messians to live in peaceful existence in the midst of a regressing world.
Actually I do have every intention of constructing an impressive high tech facility for doing most of my Atlantis research and engineering within. And I did say construct because I want to use it as a proving structure for high tech construction technology that I research on. This of course will include a wide variety of man made materials that are far more resilient and fire proof than the usual materials that you would find in a large structure. Of course with a structure such as Atlantis would you expect to find any different?
Of course their is the problem of location and this could actually be anywhere in the world. It just needs to be a place where the work can get done. However I do admit that relocating now sounds good but readiness/finance issues and physical health problems make this option unattractive at the moment.
Then their is the issue of seclusion and privacy. It is my every intention to become totally hidden but considering the size of Atlantis just how long that can be done will remain to be seen. Never the less I'll not rule out the possibility that Atlantis will not be built on the Earth at all.
Developing these technologies is going to take a long time and actual construction will not begin until everything is in readiness. This being so the actual construction of Atlantis should progress relatively quickly. However today's research is centered around fundamental microcircuit construction technologies and software. Technology that is recognized around the world as legitimate and desirable.
God told me that I have a long walk ahead of me. I'm hoping to begin the actual construction of Atlantis by the year 2030. And yes if you are asking I will live long enough.
Thursday, August 2, 2012
Universal Document Software.
Universal Document (.udoc) is a software concept I originally programmed for use in my Code Toolbox G@ software development platform. It actually is quite simple in construction in that it is actually two documents in one. It is a full function bitmap used as a background and has a full word processor that overlays text in any way over the bitmap background. The two are combined into one file in which a suitable compression scheme is employed for file storage. Magazine quality documents can easily be made with it.
The original purpose of it was the capability to program things such as dialog boxes and have all the image bitmaps right with the code all in the same document. This makes importing and exporting code to different projects a snap being a simple thing to move one single udoc file around instead of the more cumbersome methods typical in programming systems today. How it all got started is from my @on microprocessor concept and how it has a unique instruction set requiring that I write all the programming software for it.
It also uses what I call a black character concept which is useful in program editing. A typical udoc screen background that is blank is usually gray so that editing characters such as return and tab show up as black characters making them easy to see, or avoid, for select, cut and drag operations. Also other colors show up best on a gray background it being the best for enhancing any other color. Foreground characters are normally yellow or green which are colors chosen because of their minimal effects on eyestrain as compared to the tortuous effect on the eyes that a glaring white background and antiquated raster scan video technology can cause.
It contains all of the usual drawing tools and any3bytepicture.bmp can be imported. Furthermore I continue to add tools to facilitate and expedite the production of drawings for inclusion into the vCAD engineering software currently under development. Many such engineering jobs require a unique set of drawing tools tailored to specific requirements and this is met most suitably with the O3S dockable software/tool system.
I'm currently enhancing my Code Toolbox code and my .udoc code so that they will work with my new .box file concept along with enhancements to bring it up to date and compliant with O3S file format requirements along with sundry software reconfiguration and efficiency improvements. Box is an archive type file that I decided would be very useful for combining project files and code libraries and any other groups of like subject data into a single file which has advantages for certain uses. It is easier to keep track of one file instead of dozens of files scattered all over the place. The .box file will be implemented directly into the O3S Media Peruser function. The O3S box archive file system is very flexible and I even intend to use it to store O3S compatible vax multimedia files.
O3S means Object Oriented Operating System and it is being developed by Mescitadel Think Tank and it will become the standard of operating systems like no other. Simple. Reliable. Effective. More than any other out there and believe you me, this I know from experience. O3S treats file and intra-net security very seriously and will eventually make a big difference.
The original purpose of it was the capability to program things such as dialog boxes and have all the image bitmaps right with the code all in the same document. This makes importing and exporting code to different projects a snap being a simple thing to move one single udoc file around instead of the more cumbersome methods typical in programming systems today. How it all got started is from my @on microprocessor concept and how it has a unique instruction set requiring that I write all the programming software for it.
It also uses what I call a black character concept which is useful in program editing. A typical udoc screen background that is blank is usually gray so that editing characters such as return and tab show up as black characters making them easy to see, or avoid, for select, cut and drag operations. Also other colors show up best on a gray background it being the best for enhancing any other color. Foreground characters are normally yellow or green which are colors chosen because of their minimal effects on eyestrain as compared to the tortuous effect on the eyes that a glaring white background and antiquated raster scan video technology can cause.
It contains all of the usual drawing tools and any3bytepicture.bmp can be imported. Furthermore I continue to add tools to facilitate and expedite the production of drawings for inclusion into the vCAD engineering software currently under development. Many such engineering jobs require a unique set of drawing tools tailored to specific requirements and this is met most suitably with the O3S dockable software/tool system.
I'm currently enhancing my Code Toolbox code and my .udoc code so that they will work with my new .box file concept along with enhancements to bring it up to date and compliant with O3S file format requirements along with sundry software reconfiguration and efficiency improvements. Box is an archive type file that I decided would be very useful for combining project files and code libraries and any other groups of like subject data into a single file which has advantages for certain uses. It is easier to keep track of one file instead of dozens of files scattered all over the place. The .box file will be implemented directly into the O3S Media Peruser function. The O3S box archive file system is very flexible and I even intend to use it to store O3S compatible vax multimedia files.
O3S means Object Oriented Operating System and it is being developed by Mescitadel Think Tank and it will become the standard of operating systems like no other. Simple. Reliable. Effective. More than any other out there and believe you me, this I know from experience. O3S treats file and intra-net security very seriously and will eventually make a big difference.
Subscribe to:
Posts (Atom)