text:
Justia Patents Storage Or Planning Of Route InformationUS Patent Application for SENSOR SYSTEM AND METHOD FOR USE WITH AN AUTOMATED GUIDED VEHICLE (AGV) Patent Application (Application #20140244097)
SENSOR SYSTEM AND METHOD FOR USE WITH AN AUTOMATED GUIDED VEHICLE (AGV)
May 6, 2014 - Fori Automation, Inc.
A sensor system for use with an automated guided vehicle (AGV) includes a plurality of sensor units electronically coupled to a sensor control module via parallel communications. Each sensor unit may include a sensor array having a plurality of sensor elements, a conditioning circuit having one or more filter/amplifiers, and a conversion circuit. The sensor control module may be configured to communicate with other AGV components via serial communications. The sensor system is capable of obtaining and storing sensor readings with or without associated offset values and can use the sensor readings to determine the center of a magnetic field using methods that require relatively little processing power. A method of calibrating the sensor system may include determining and storing offset values for a plurality of sensor elements and may be performed with the sensor system installed or uninstalled to the AGV.
Latest Fori Automation, Inc. Patents:
Drive mechanism for automated guided vehicle
Automated guided vehicle (AGV) system
Quick-disconnect work support assembly
Pallet conveyor with corner assembly
CROSS-REFERENCE TO RELATED APPLICATION
This application is a divisional of U.S. Ser. No. 13/196,354, filed Aug. 2, 2011, now U.S. Pat. No. ______, which claims the priority of U.S. Provisional Application No. 61/370,145, filed Aug. 3, 2010. The entire contents of these applications are hereby incorporated by reference.
The present disclosure generally relates to sensor systems and methods of using the same and, more particularly, to sensor systems and methods that provide information relating to the location, position, orientation, heading, etc. of automated guided vehicles (AGVs).
Automated guided vehicles may be used to transport payloads along a predetermined route without real-time human assistance. For example, an AGV can transport items such as heavy vehicle components like engines, chassis, etc. along a route along a manufacturing plant floor to deliver the payload from one location to another or to allow various manufacturing operations to be performed thereon. AGVs may offer the ability to carry payloads too heavy for a person to carry and without the supervision of a person, while also offering the flexibility to be reconfigured to follow a different route or carry different types of payloads. Some AGVs include drive and/or steering mechanisms that can propel, guide, and/or steer the vehicle along the predetermined route.
According to one embodiment, a sensor system is provided for use with an automated guided vehicle (AGV). The sensor system includes a sensor housing that is attached to the AGV and a sensor board that is at least partially located within the sensor housing. The sensor board includes a plurality of sensor units electronically coupled to a sensor control module. Each of the sensor units interacts with an indicating system that follows a pre-determined path along the ground. Each of the sensor units includes a sensor array having a plurality of sensor elements that take sensor readings regarding the position of the AGV with respect to the indicating system. Each sensor unit further includes a conditioning circuit that is electronically coupled to the sensor array. The conditioning circuit includes a plurality of filter/amplifiers that process the sensor readings from the sensor array. Each of the sensor units also includes a conversion circuit that is electronically coupled to the conditioning circuit. The conversion circuit converts the sensor readings from the conditioning circuit for transmission to the sensor control module.
According to another embodiment, a method is provided for operating a sensor system for an automated guide vehicle (AGV). The method includes the steps of: (a) providing a sensor system having a plurality of magnetic sensor elements that interact with a magnetic indicating system that is laid out on the ground and follows a pre-determined path; (b) obtaining sensor readings from the magnetic sensor elements; (c) storing the sensor readings from the magnetic sensor elements at a memory device; and (d) using the stored sensor readings to determine a center of field value that represents the center or centroid of a corresponding magnetic field produced by the magnetic indicating system.
According to another embodiment, a method is provided for calibrating a sensor system for an automated guided vehicle (AGV). The method includes the steps of: (a) initializing a sensor system having a plurality of sensor elements; (b) obtaining and averaging a plurality of sensor readings for each of the sensor elements; (c) using the averaged sensor readings for each of the sensor elements to generate a corresponding offset value for each of the sensor elements; and (d) electronically storing the offset values for each of the sensor elements in the sensor system.
Preferred exemplary embodiments of the invention will hereinafter be described in conjunction with the appended drawings, wherein like designations denote like elements, and wherein:
FIG. 1 is a perspective view of an exemplary sensor system that may be used with an AGV;
FIG. 2 is a perspective view of the exemplary sensor system of FIG. 1, where a sensor housing has been removed to reveal a sensor board;
FIG. 3 is a schematic block diagram of the exemplary sensor board of FIG. 2;
FIG. 4 is a schematic circuit diagram of the exemplary sensor board of FIG. 2;
FIG. 5 is a schematic circuit diagram of an exemplary sensor element and conditioning circuit that may be used with the exemplary sensor board of FIG. 2;
FIG. 6 is a flowchart of an exemplary method that may be used to calibrate a sensor system, such as the exemplary sensor system shown in FIG. 1;
FIG. 7 is a flowchart of an exemplary method that may be used to operate or control a sensor system, such as the exemplary sensor system shown in FIG. 1;
FIG. 8 is a flowchart of another exemplary method that may be used to operate or control a sensor system, such as the exemplary sensor system shown in FIG. 1;
FIG. 9 is a flowchart of an exemplary method that may be used to determine the location, position, orientation, etc. of a sensor system, such as the exemplary sensor system shown in FIG. 1, relative to a magnetic field; and
FIG. 10 is a graphic representation of some exemplary sensor readings and is provided in conjunction with the exemplary method shown in FIG. 9.
The exemplary sensor system and method described herein may provide information relating to the location, position, orientation, heading, etc. of an automated guided vehicle (AGV). An AGV is typically an unmanned and self-propelled vehicle that travels around a guided path or route laid out on the floor of a factory, warehouse, distribution center, graded earth, etc. Some examples of potential AGV applications include handling materials, delivering parts in a warehouse, advancing a work piece or assembly through various stages of a manufacturing process, and moving a piece of industrial equipment (e.g., a drilling or welding device) around a large stationary work piece, to name a few. Skilled artisans will appreciate that there are a number of different types of AGVs used across a variety of industries, including the automotive, aerospace, warehousing, and distribution center industries. The exemplary system and method described below are not limited to any particular type or application of an AGV, and may be used with any AGV known in the art.
Sensor System—
With reference to FIGS. 1 and 2, there is shown an exemplary embodiment of a sensor system 10 that may be used with an AGV and includes a sensor housing 12 and a sensor board 14. Sensor system 10 may be mounted to the underside of an AGV so that it can interact with an indicating system located along the ground. As used herein, an indicating system broadly includes an arrangement of any type of detectable markers, beacons, or guides that can be located along the ground to form a path for the AGV to move along. The indicating system may include active elements, such as RF-transmitting devices, electromagnetic devices, or other powered devices that produce a magnetic field or emit electromagnetic radiation, and it may include passive elements, such as permanent magnets, reflectors, colored tape, etc. Indicating system elements may be provided as strips or wires or other continuous elements, or they may be separate or discrete elements that are arranged along the ground in a pattern such as a path, grid, or array. For example, a magnetic sensor system 10 may be used with an AGV to detect and/or evaluate an indicating system that includes magnetic or electromagnetic elements such as a thin permanent magnetic strip installed on top of or just beneath the ground, or it may be similarly used with an indicating system that includes a plurality of magnets or electromagnetic installed in the ground in a particular arrangement in the area in which the AGV is to operate.
According to the exemplary embodiment shown in FIGS. 1 and 2, sensor system 10 is an elongated device that, when mounted to the underside of an AGV, extends across at least a portion of the lateral width of the AGV so that it is generally perpendicular to the magnetic strip or other indicating system on the ground. Sensor system 10 may be centered or off-centered on the underside of the AGV, it may be located near the front, middle or rear of the AGV, it may extend across the entire lateral width of the AGV or only a portion of it, and it may be by itself or used in conjunction with other sensor systems, to name a few possibilities. While the particular embodiments of sensor system 10 described below are described so that they work with indicating systems that produce magnetic fields, it should be appreciated that sensor system 10 may be configured to work with indicating systems of any type described above.
Sensor housing 12 is a housing or cover that may be used to protect or shield some of the components of sensor system 10. In this particular embodiment, sensor housing 12 is an elongated housing that surrounds and protects sensor board 14 and is made of a material, like an aluminum-based material, with desirable electromagnetic interference (EMI) characteristics that enable proper interaction with a magnetic strip on the ground yet avoid interfering with other operations of the AGV. Sensor housing 12 may include one or more spring-loaded hinges or connections that enable the sensor housing to be pivotally attached to the underside of the AGV. If the AGV runs over debris or other objects, the hinges will allow the sensor housing to pivot out of the way or pivotally breakaway from the underside of the AGV instead of allowing damage to sensor system 10. This pivotal breakaway mounting feature is optional, however, as sensor housing 12 may be fixedly mounted to the AGV instead.
Sensor board 14 is a circuit board to which a number of the components of sensor system 10 may be attached and may be at least partially located within sensor housing 12. According to one exemplary embodiment, sensor board 14 is a thin elongated circuit board that has a number of individual sensors aligned along one edge and snap-in connectors located at one or both ends so that multiple sensor boards can be connected end-to-end. This end-to-end connectivity makes sensor system 10 somewhat scalable, where additional sensor boards 14 can simply be added or removed in order to adjust the overall sweep or length of the sensing area and can be distinguished through the use of dipswitches. For example, if each sensor board 14 is approximately 12″ long and up to eight sensor boards can be connected together, sensor system 10 may have an overall sensing area that is up to 96″ across. Of course, this feature is optional, as sensor board 14 does not have to allow for end-to-end connections. In the exemplary embodiment shown in FIGS. 3-4, sensor board 14 includes sensor units 20-26, a sensor control module 28, parallel communications 30, and serial communications 32.
Sensor units 20-26 may include any combination of hardware and/or software that provides sensor readings pertaining to the magnetic field that is produced by the magnetic strip located on the ground. According to an exemplary embodiment, each sensor unit 20-26 includes a corresponding sensor array 40-46, a conditioning circuit 50-56, and a conversion circuit 60-66, respectively. Sensor units 20-26 may be evenly distributed or spaced along an edge of sensor board 14 so that they evaluate different parts of the magnetic field produced by the magnetic strip; by doing this, the sensor units may provide sensor system 10 with information about the magnetic field, such as the location of the center of the field, the intensity of the field, the width of the field, etc. Because of their similarity, the following description of sensor unit 20 and its components applies to the other sensor units 22-26 as well.
Sensor array 40 is a collection of one or more sensing elements that work with conditioning and conversion circuits 50, 60 to provide sensor system 10 with sensor readings regarding the detected magnetic field. Sensor array 40 may include any number of different sensor elements, components, devices, modules, etc., but the exemplary embodiment shown here includes eight sensor elements 70-84 in the form of Hall-Effect sensors (e.g., ratiometric linear Hall-Effect sensors) that provide signals that are proportional to the detected strength of the magnetic field, as well as the direction of the magnetic field. Sensor elements 70-84 may directly sense a magnetic field, or they may indirectly determine or calculate the magnetic field from readings taken from other sensor elements, components, devices, modules, subsystems, etc. Skilled artisans will appreciate that a number of different types of sensor elements could be used to detect, sense, monitor or otherwise evaluate the magnetic field in question, and that the present system and method are not limited to the exemplary Hall-Effect sensors shown here. One such example is a photo-diode array. Sensor array 40 may be directly and electronically coupled to its corresponding conditioning circuit 50, indirectly coupled via other electronic components, or coupled according to some other arrangement known in the art. It should also be appreciated that the exemplary sensor arrangement described herein (i.e., eight sensor elements per sensor array, one sensor array per sensor unit, and four sensor units per sensor board for a total of thirty-two sensors) represents only one possible arrangement. Other arrangements with fewer, greater and/or different components are certainly possible.
Conditioning circuits 50-56 may filter, amplify or otherwise condition the sensor readings from sensor arrays 40-46 before sending them on to conversion circuits 60-66, respectively. In one embodiment, each sensor element 70-84 is coupled to a corresponding filter/amplifier 90-104 so that each sensor reading is filtered and amplified before being sent to conversion circuit 60. Conditioning circuit 50 may employ any type of suitable filtering and amplifying means (e.g., transistor amplifier, operational amplifier, voltage amplifier, etc.). With reference to FIG. 5, there is shown an enlarged view of an exemplary filter/amplifier 90 coupled to a sensor element 70, where the filter/amplifier conditions the sensor readings from the sensor element by filtering and amplifying the signal before passing it along. Even though this exemplary arrangement shows each sensor element 70-84 being electronically coupled to a corresponding filter/amplifier, other arrangements are also possible. For instance, all of the sensor elements 70-84 in sensor array 40 could be coupled to a single filter/amplifier, which in turn could be connected to conversion circuit 60. Skilled artisans will appreciate that the arrangement shown here, where each sensor element has its own filter/amplifier, may provide a fast response that avoids certain bottlenecks. In addition, connecting sensor array 40 to conversion circuit 60 via conditioning circuit 50 provides sensor system 10 with a stackable and modularity feature which can be customized depending on the specific AGV application requirements (e.g., more sensors per array and/or more sensor arrays/sensor unit may be provided if higher precision is required, and so on). As stated earlier, this description applies to sensor arrays 42-46 and conditioning circuits 52-56 as well.
Conversion circuits 60-66 may act as an intermediary between sensor arrays 40-46 and sensor control module 28 by assisting in the conversion and/or communication of sensor readings. According to one exemplary embodiment, conversion circuit 60 acquires sensor readings or signals from conditioning circuit 50, performs an analog-to-digital (A/D) conversion of the signals, multiplexes the signals, and then sends the multiplexed signals out to sensor control module 28 via parallel communications 30. Thus, it is possible for conversion circuit 60 to include any combination of hardware and/or software components capable of filtering, amplifying, buffering, converting, multiplexing and/or otherwise processing the sensor readings. Conversion circuit 60 may have a processing unit and may be a Data Acquisition System (DAS), or part of a DAS, for example. In the exemplary embodiment of FIG. 4, there is shown a conversion circuit 60 having an eight-channel analog-to-digital converter and multiplexer electronically coupled to a corresponding sensor array 40 and conditioning circuit 50 on an input side, and coupled to parallel communications 30 on an output side.
Skilled artisans should appreciate that even though conversion circuits 60-66 are schematically depicted here as separate entities from conditioning circuits 50-56, they may be included or integrated together within the same circuit or system. It is also possible for the filtering, amplifying, buffering, converting, multiplexing and/or signal processing to actually occur at any of the components in sensor units 20-26, as these processes are not specifically limited to any one particular component or circuit. Other modifications and changes to sensor units 20-26 are also possible.
Sensor control module 28 may include any combination of electronic processing devices, memory devices, communication devices, input/output (I/O) devices, and/or other known components and may perform various processing and/or communication related functions. Even though FIGS. 3 and 4 show sensor control module 28 electronically coupled to four sensor units 20-24, skilled artisans should appreciate that the sensor control module may be connected to more or less sensor units than this. In one embodiment, sensor control module 28 includes a processing device 110 and a memory device 112. Processing device 110 can process information from a number of different sources, including sensor readings from sensor units 20-24, and preferably includes one or more microcontrollers, microprocessors, central processing units (CPUs), application specific integrated circuits (ASICs), or any other suitable processing device known in the art. Processing device 110 may perform a variety of tasks, including executing the method described below which evaluates the sensor readings and provides the output of that evaluation to some other device or system in the AGV. For instance, the AGV's steering system may request information from sensor system 10 regarding the position of the AGV relative to the magnetic strip and, in response to such a request, sensor control module 28 may provide steering system with the requested position information over serial communications 32. This is only one example of the type of task and function that processing device 110 may perform, as it could be used in many other capacities as well.
Memory device 112 may include one or more types of electronic memory (e.g., EEPROM, RAM, flash memory, etc.), and may store different types of information needed for the operation of sensor system 10. For example, the filtered, amplified and digitally converted sensor readings provided by sensor units 20-26 may be stored in memory device 112; the collection of electronic instructions and other data that makes up the present method may be stored in memory device 112; and look-up tables, arrays and other data structures may also be stored in memory device 112, to name a few examples. These are, of course, only some of the items that could be stored at memory device 112, as skilled artisans will know of many other potential uses.
Parallel communications 30 is a parallel connection or bus that may connect the various sensor units 20-24 with sensor control module 28. In this particular embodiment, parallel communications 30 is a single-direction eight-channel bus that conveys information from sensor units 20-24 to sensor control module 28. Sensor control module 28 can request sensor readings from a specific sensor element over chip select lines 120 and address lines 122. In response to this request, the selected sensor element can provide the requested sensor readings back to sensor control module 28 over parallel communications 30. Serial communications 32, on the other hand, is a serial connection that may connect sensor control module 28 with any number of other devices on the AGV, such as a supervisory device 34 like a servo drive of an AGV drive or steering mechanism. In one example, serial communications 32 performs a signal level conversion from a TTL level to an RS485 level. Of course, the serial communications could perform other tasks as well. For communication within sensor system 10, parallel communications 30 may be preferred due to their speed; for communications outside of the sensor system 10, serial communications 32 may be preferred due to their higher resistance to electromagnetic interference (EMI). Of course, other communication arrangements, protocols, etc. are also possible, including wired and wireless communications.
In general operation of sensor system 10, sensor control module 28 may send out a request to one or more sensor elements for sensor readings over chip select/address lines 120, 122. The selected or identified sensor element(s) then takes a sensor reading and passes it to a corresponding filter/amplifier, where the sensor reading is filtered, amplified or otherwise conditioned. The filtered and amplified sensor reading is then provided to a corresponding conversion circuit, which performs additional signal processing steps, such as converting it from analog to digital form. Once the sensor reading has been properly conditioned or packaged for delivery, it may be sent to sensor control module 28 over parallel communications 30 in a multiplexed fashion. At this stage, the sensor readings are processed or otherwise evaluated by processing device 110 according to a method, such as the one described below. The output or results from these evaluations may be stored in memory device 112 and/or transmitted to some other AGV device or system via serial communications 32. Other methods for utilizing or operating sensor system 10 are certainly possible, as the preceding recitation is simply one example.
In one alternative embodiment, two or more sensor boards 14 are aligned and/or connected in a non-parallel fashion; for example, at 90° to one another. By having a first sensor board aligned perpendicular to the magnetic strip on the ground and a second sensor board aligned parallel to the magnetic strip, the AGV may be able to use the sensor system not only for navigating around the path laid out on the ground, but also for parking or docking at different stations along the path, such as an off-line charging station; an activity sometimes referred to as crabbing. In such an arrangement, the perpendicularly aligned sensor board could help navigate during normal forward movement along the path, and the parallel aligned sensor board could help navigate during sideways movement away from the path, such as at a charging or docking station. This is an optional feature and is representative of just one of many potential sensor system arrangements.
Method of Calibration—
Turning now to FIG. 6, there is shown a method 200 that may be used to calibrate the exemplary sensor system 10. Before operating sensor system 10, it may be desirable to calibrate the system in order to take into account slight discrepancies that may exist between the different sensor units, sensor arrays, sensor elements, conditioning circuits, filters/amplifiers, etc. The electromagnetic interference (EMI) in the surrounding environment can also affect sensor readings. For example, it is possible for sensor elements 70 and 72 to output or generate different sensor readings even when they are exposed to the same magnetic field. Such discrepancies may be due to inherent differences in the components themselves and may be within allowed tolerances. Calibration method 200 is designed to take such discrepancies into account and may include electronic instructions that are stored in memory device 112 and are executed by processing device 110.
The method starts with step 210, which may initialize sensor system 10 by performing one or more initialization or start-up tasks. In one embodiment, step 210 is automatically executed after a power-up sequence of the AGV; in another embodiment, step 210 is executed in response to an initialization or calibration command that is sent to sensor system 10 from some other device on the AGV over serial communications 32. Sensor system 10 is designed such that an external tool or device (e.g., an external computer coupled to the AGV or some supervisory device on the AGV) can initiate a calibration operation simply by sending an appropriate command signal to the sensor system. Skilled artisans should appreciate that other options for initiating the calibration method are also possible. According to one embodiment, step 210 may: initialize a number of ports or connections of sensor system 10 (e.g., parallel communications 30, serial communications 32, chip select lines 120, address lines 122, etc.); enable a watchdog timer within sensor control module 28; initialize global data; and put the sensor system in a raw data mode where sensor readings are provided without adding any type of offset or normalization value. Other initialization or start-up tasks could be performed as well.
Next, step 220 obtains sensor readings from the various sensor elements. In an exemplary embodiment, each sensor element 70-84 of each sensor array 40-46 is instructed to take a certain number of sensor readings (e.g., fifty readings/sensor element) and to provide those sensor readings to sensor control module 28. The sensor readings for each sensor element may then be averaged in order to avoid any anomalies that can occur with a single reading. Once fifty sensor readings are taken for sensor element 70, for example, the calibration method advances to the next sensor element 72 so that fifty new sensor readings may be obtained and averaged. This process may continue until averaged sensor readings have been obtained from all of the sensor elements (e.g., thirty-two averaged sensor readings would be obtained for the thirty-two sensor elements of sensor board 14; one for each sensor element). If the sensor elements are all exposed to the same magnetic field, it follows that the averaged sensor readings should be the same; but this is usually not the case. Calibration method 200 uses the discrepancies between the averaged sensor readings to generate offset values that can calibrate sensor system 10, as is described below. It should be appreciated, however, that the sensor readings do not need to be averaged in this exemplary way, as other techniques are certainly possible. It may be preferable to perform step 220 in an environment that is void of any significant magnetic fields, such as the one produced by the magnetic strip on the ground. This way, the discrepancies in the averaged sensor readings are due to inherent differences in the sensor components and not the nearby magnetic field.
Step 230 processes the averaged sensor readings and stores corresponding offset values. According to one embodiment, processing device 110 uses the averaged sensor readings from the previous step to determine a corresponding offset value for each sensor element, and then stores the offset values in memory device 112. As mentioned above, the sensor elements should theoretically behave the same when exposed to the same magnetic field. But in practice a sensor element may have a slight performance deviation from another due to several reasons including sensor element location, degradation over time, inherent differences in the actual components, electrical noise, etc. Therefore, a separate offset value—which is derived from the previously gathered averaged sensor readings—is determined for each sensor element and is stored in sensor system 10. For example, if the averaged sensor readings from sensor element 70 are 0.1 V higher than they should be, then step 230 may generate and store an offset value of −0.1 V for this sensor element. When sensor element 70 is subsequently used in a normal mode, its sensor readings will be adjusted by −0.1 V in order to compensate for its internal bias and provide a more accurate reading. This calibration method enables one or more sensor elements (e.g., an entire sensor array) to be easily calibrated on the fly if new hardware is installed, versus manually calibrating the new hardware by making physical adjustments to components such as potentiometers and the like. Furthermore, it is possible to calibrate a sensor board that is or is not mounted to an AGV. Other benefits will become obvious to skilled artisans as well.
Step 240 puts sensor system 10 back in a normal mode. Now that calibration of sensor system 10 is complete, step 240 may cause the sensor system to exit the calibration mode by changing a setting from "calibration mode" or "raw data mode," as described above, to a "normal mode" where sensor readings are compensated with offset values. In normal mode operation, sensor system 10 may provide sensor readings to other devices and systems around the AGV, where the sensor readings have been adjusted or compensated to take into account the small discrepancies that sometimes exist between sensor elements. Such a process is sometimes referred to as "normalization." Other steps may also be taken to ready sensor system 10 for normal mode operation.
Turning now to FIG. 7, there is shown an exemplary method 300 for operating or controlling a sensor system, such as sensor system 10. In some applications, method 300 may continuously run and collect sensor readings so long as sensor system 10 is activated or turned 'on'. Such a method constantly updates the sensor readings so that if a request for sensor readings is received (e.g., an interrupt signal received from some other device in the AGV over serial communication 32), then sensor system 10 can provide the requesting device with a recent and current set of sensor readings. In an exemplary embodiment, method 300 is executed or cycles on a periodic basis that takes several microseconds per sensor element. Other bases for performing or executing method 300 are certainly possible.
Beginning with step 310, the method may initialize sensor system 10 by performing one or more initialization or start-up tasks. According to an exemplary embodiment, step 310 may: initialize a number of ports or connections of sensor system 10 (e.g., parallel communications 30, serial communications 32, chip select lines 120, address lines 122, etc.); enable a watchdog timer within sensor control module 28; initialize global data; and put the sensor system in a normal operation mode where sensor readings are provided with an offset or normalization value built into the readings, as previously described. Other initialization or start-up tasks could be performed as well.
Next, steps 320-390 may be used by method 300 to cycle through all of the sensor elements (thirty-two sensor elements in the exemplary sensor board 14) and collect sensor readings or other data from each one. As mentioned above, it is possible for sensor system 10 to include multiple sensor boards 14 connected together in an end-to-end fashion; e.g., up to eight sensor boards may be connected end-to-end. The following description is directed to a single sensor board embodiment, however, the process of cycling or looping through all of the sensor elements applies to multiple board embodiments as well. Furthermore, it is not necessary that method 300 begin collecting sensor readings from any one sensor element, or that the sensor elements be selected in any particular order, as the following data acquisition method is simply one possible embodiment.
Step 320 selects the sensor unit from which sensor readings are to be taken. For example, sensor control unit 28 may select sensor unit 20 through the use of chip select lines 120 so that the method can begin collecting sensor readings from the various sensor elements in sensor array 40. Next, step 330 selects the individual sensor element from which sensor readings are to be taken. This selection can also be made by sensor control module 28, for example, which may put the address of the selected sensor element on address lines 122 (e.g., the address for sensor element 70). With the selections made in steps 320 and 330, an individual sensor unit has been identified for retrieval of sensor readings. Other methods for selecting and cycling through the various sensor elements may also be used.
Step 340 gathers sensor readings or other data from the selected sensor element. Continuing with the preceding example, if sensor element 70 is selected then it provides an analog sensor reading to amplifier/filter 90, which amplifies and filters the reading before passing it onto conversion circuit 60. The conversion circuit, in turn, can convert the analog reading into digital form and then send the amplified, filtered and digitized sensor reading to sensor control module 28 over parallel communications 30. In one embodiment, sensor element 70 provides a voltage output that is related to the strength and/or direction of the magnetic field that it senses; but other techniques for representing the detected magnetic field may be used instead. Once the sensor readings are received at control module 28, step 350 may store the sensor readings for the selected sensor element at memory device 112 or some other suitable location.
Step 360 determines if the last sensor element of that particular sensor unit has been selected. If the last sensor element has not been selected, then step 364 increments a sensor element counter and the method loops back to step 330 so that sensor readings may be gathered from the next sensor element. If the last sensor element has been selected, then the method proceeds to the next step. Continuing with the preceding example, if sensor element 70 was selected, then step 360 will recognize that this sensor element is not the last element of sensor unit 20 and that other sensor elements still need to be queried. Step 364 will increment the sensor element counter from sensor element 70 to sensor element 72 and the process will be repeated. This looping sequence continues until step 364 encounters sensor element 84, which is the last sensor element of sensor unit 20. At which point, the sensor element counter is reset (step 370) and the method proceeds to step 380, which checks to see if the last sensor unit has been selected. In the example above, sensor unit 20 does not represent the last sensor unit (sensor units 22-26 still need to be queried), so step 380 passes the method along to step 384 which increments a sensor unit counter to point at sensor unit 22. Sensor readings may then be gathered and stored from the various sensor elements of sensor array 42 (which is part of sensor unit 22), as described above. This process continues until sensor readings have been gathered from all of the sensor elements of all of the sensor units (thirty-two in the present example), at which point the sensor unit counter is reset in step 390 and the method generally ends until it is time for method 300 to cycle again.
Skilled artisans will appreciate that other embodiments and techniques for selecting sensor elements are certainly possible. For example, it is possible for sensor elements to be randomly selected in any order instead of being selected in a chronological order, as described above. It is also possible to gather sensor readings from every other sensor element or to use some other partial data gathering method in order to increase the speed of data acquisition and/or to reduce the amount of memory required. It was mentioned above that multiple sensor boards 14 may be connected end-to-end so that the overall sweep or length of the system is increased. Method 300 may be adapted for such a system by including an additional loop sequence that checks to see if the last sensor board has been selected and if it has not, then increment a sensor board counter and advance to the next sensor board. If the last sensor board has been selected, then the method may end the operation. Such a compounded loop sequence could continue until all of the sensor elements of all of the sensor units, and all of the sensor units of all of the sensor boards have been selected.
Turning now to FIG. 8, there is shown an exemplary method 400 that may be used by a device or system in the AGV to gather sensor readings from sensor system 10. For example, if a drive system in the AGV required information regarding the position and/or alignment of the AGV, then that system could use method 400 to acquire such information from sensor system 10. Sensor system 10 may operate according to two main execution paths: a first path is method 300, which is periodically gathering sensor readings and is continuously running whenever the sensor system is "on;" a second path is method 400, which provides sensor readings from sensor system 10 to some other device or system and is executed on an interrupt basis (e.g., it can be executed whenever serial communications 32 receives data).
According to an exemplary embodiment, processing device 110 executes method 300 such that it continuously gathers and updates sensor readings from the various sensor elements, as already described. This continuous and periodic process carries on until serial communications 32 receives an incoming message, at which point the processing device ceases execution of method 300 and begins executing method 400 in order to determine the nature of the incoming message. Once method 400 is performed, processing device 110 resumes executing method 300 until another message is received at the serial communications 32. Skilled artisans will appreciate that the "interrupt-style" interaction between methods 300 and 400 just described is only one possible arrangement, as methods 300 and 400 are not limited to this and may be activated or executed according to other arrangements as well. For instance, method 400 could be executed on a periodic basis, as opposed to an interrupt basis.
Beginning with step 410, the method may initialize sensor system 10 by performing one or more initialization or start-up tasks. According to an exemplary embodiment, step 410 may: initialize a number of ports or connections of sensor system 10 (e.g., parallel communications 30, serial communications 32, chip select lines 120, address lines 122, etc.); clear or set buffers, variables, etc.; and set a message watchdog timer within sensor control module 28. The message watchdog timer may be used to monitor the period or time lapse between bytes of the incoming message, in order to ensure that the incoming message on serial communications 32 is intact. Other initialization or start-up tasks could be performed as well.
Step 420 determines if the incoming message is valid, and may use a number of different techniques for doing so. One or more checks may be performed to determine the validity of the incoming message, including checking the message's structure integrity (i.e., syntax) and/or its content logic (i.e., semantic). In one embodiment, step 420 determines the syntax validity of the incoming message by validating, for example, its checksum or message length. This validation process may include using a parity byte or word, modular sum, position dependent checksum (e.g., Fletcher's checksum, Adler-32, cyclic redundancy checks (CRCs)), or any other suitable technique for checking syntax. Step 420 may also check the validity of the semantics of the incoming message. This may include, for example, checking to make sure that any sensor element numbers are valid, board numbers are valid, etc. If the request is invalid—such as the case of a corrupted or erroneous incoming signal—then method 400 ends at this step; otherwise, method 400 proceeds to the next step. It should be appreciated that while exemplary method 400 is shown having three function calls or sub-routines (440, 460, 480), the method is not limited to this and is flexible such that function calls or sub-routines can easily be added or removed. For instance, additional function calls could be included for controlling LEDs or other visual indicators on the AGV, for retrieving or modifying configuration settings, or for any function that is appropriate for sensor system 10 to perform.
Step 430 evaluates the contents of the incoming message and determines if there is a request to calibrate sensor system 10. One instance when such a request is likely to be used is if one or more pieces of hardware in sensor system 10 have recently been replaced but have not yet been calibrated. If step 430 determines that the incoming message does in fact contain a calibration request, then step 440 performs the requested calibration. The calibration may be for an entire sensor system 10 (all thirty-two sensor elements), a particular sensor unit (eight sensor elements), or one or more individual sensor elements, depending on the contents of the incoming message. Step 430 may perform or execute the calibration method 200 that was previously described In another embodiment, step 430 may simply inquire as to the calibration status or offset value of one or more sensor elements; this information may then be transmitted back to the requesting device over serial communications 32. If step 430 determines that the incoming message does not contain a calibration request, then method 400 proceeds to the next step.
Step 450 evaluates the contents of the incoming message and determines if there is a request to read one or more sensor elements. For example, a supervisory device in the AGV (e.g., a servo drive) may require sensor readings from one or more sensor elements in order to operate properly. In such a case, the incoming message that the device sends to sensor system 10 over serial communications 32 may include a request to read out certain sensor elements. Such requests may specify a single sensor element (e.g., sensor board 14, sensor unit 20, and sensor element 78), or they may specify a range or group of sensor elements. If step 450 determines that there is a read sensor request, then step 460 may retrieve the requested sensor reading(s) from memory device 112, package the sensor reading(s) into a suitable message format, and send the packaged sensor reading(s) to the requesting device over serial communications 32. The use of specific address locations in memory device 112 tied to specific sensor elements may be used during step 460. It should be appreciated that the read sensor request may further contain additional data, information, settings, etc. that affect the request. For example, the read sensor request may indicate whether the sensor readings are to be provided in a normalized state (i.e., with offset values built in) or in a raw data state where no offset compensation has been applied. Other settings and parameters are also possible. If step 450 determines that there is no read sensor request within the incoming message, then method 400 proceeds to the next step.
Step 470 evaluates the contents of the incoming message and determines if there is a request to analyze the sensor readings. Such a request may include any solicitation for analyzing, evaluating and/or performing various calculations on the sensor readings, and any number of different techniques may be used. For instance, a supervisory device on the AGV may want to know the current position of sensor system 10 (and hence, the position of the AGV) relative to the magnetic field that is generated by the magnetic strip laid out on the floor. A number of different methods and techniques may be employed in order to determine this position, including the exemplary "center of field" analysis described below. Other requests for analyzing sensor readings may include requests for determining: magnetic field presence or absence, magnetic field width, minimum and maximum magnetic field strengths or direction, the number of maxima or minima field strengths of a magnetic field, the presence of docking or charging stations, or the presence of "work zones" or any other specific locations or location markers along the guided path where the AGV is expected to perform some specific function. Other requests are certainly possible. The request for analysis may include one or more parameters to be used during the analysis or evaluation (e.g., identification of sensor board that is to be used, left- or right-hand sensor sweep direction, north or south magnetic field polarity, minimum threshold or noise value, minimum width threshold, etc.).
If step 470 determines that there is a request to analyze sensor readings, then step 480 is performed; if step 470 determines that there is no request to analyze sensor readings in the incoming message, then the method proceeds to step 490 where output from method 400 can be sent to some other device within the AGV (e.g., the device that sent the incoming message to begin with). Although step 490 may transmit output via any type of communication port, serial communications 32 may be particularly well suited for this. In one embodiment, the output or response may include a confirmation that a request has been fulfilled successfully or unsuccessfully; for instance, if a calibration request has been requested then upon successful calibration of sensor system 10, a confirmation message could be sent indicating as much. In other instances specific data may be requested. For example, if a specific sensor element offset value is requested then this value would be transmitted in the output or response message. Skilled artisans should appreciate that the particular order or combination of steps in method 400 is not limited to the exemplary embodiment shown and described here, as other combinations and sequences may be used instead.
An exemplary step 480 is described in more detail in conjunction with FIGS. 9 and 10. In this particular embodiment, step 480 performs a "center of field" analysis of the most recent sensor readings in order to determine the center or centroid of the magnetic field. Other output, like field width and maximum field strength, may also be generated during this step. Beginning with step 510, the method initializes or establishes one or more parameters that may be needed for the analysis. According to an exemplary embodiment, step 510 establishes the following parameters: a sensor board number (e.g., 0-7) if multiple sensor boards are being used; a minimum sensor reading threshold (typically the threshold is set just above the noise floor so that noisy sensor readings can be discarded); a sensor sweep direction (e.g., from a leftmost sensor element to a rightmost sensor element, or vice versa) that dictates the direction of polling across the linear sensor array; an expected field polarity (e.g., north, south, etc.) of the magnetic field; as well as any other suitable parameter used for sensor reading analyses. Any of the parameters established in step 510, including the minimum sensor reading threshold, may be static (e.g., determined during manufacture, determined during system installation, etc.) or dynamic (e.g., modified daily, modified every work shift, etc.). For example, a supervisory device could send a message to sensor system 10 over serial communications 32 instructing it to increase its minimum sensor reading threshold from a first level to a second level, or to decrease the threshold by 10%. This adjustability feature may be particularly useful in environments where the electromagnetic interference (EMI) is variable or where the magnetically sensed material varies. Clipping or adjusting the minimum sensor reading threshold up or down may cause "regions of interest" to emerge, as will be explained in more detail. Step 510 may also perform other setup tasks including clearing buffers and counters, initializing variables, etc.
Next, step 520 determines if a sensor reading is above the minimum sensor reading threshold. As suggested above, the sensor reading threshold may be set slightly above the minimum noise level that sensor readings should be at in order to be taken into consideration. FIG. 10 shows a graphical representation of an exemplary magnetic field 600, where various sensor elements (70-84) are represented on the X-axis and sensor readings (620-690) in terms of magnitude or intensity of detected magnetic field are represented on the Y-axis. Dashed line 610 represents a minimum sensor reading threshold. Sensor element 70, which may be the leftmost sensor element in this particular example, generates sensor reading 620, which is below sensor reading threshold 610; thus, step 520 sends control of the method to step 524 to see if a first edge has already been stored. "Edges," as used herein, generally describe the edge of the magnetic field; that is, the points along the curve in FIG. 10 where the detected magnetic field strength or sensor reading crosses over some sensor reading threshold (around points 640, 670 in this exemplary graph). The "first edge" corresponds with the first sensor reading that crosses over sensor reading threshold 610 and generally represents the beginning of the magnetic field, and the "last edge" corresponds with the last sensor reading that was above the sensor reading threshold and generally represents the end of the magnetic field. The reason that step 524 checks to see if a first edge has been stored is to determine if the current sensor reading is before the beginning of the magnetic field (sensor readings 620, 630) or is beyond the end of the magnetic field (sensor readings 680, 690). Since a first edge has not yet been stored in this example (no sensor reading has yet to exceed threshold 610 in this particular left-to-right sweep of the sensor elements) and sensor element 70 is not the last sensor element to be polled, the method ignores sensor reading 620 and step 560 passes control to step 564.
Step 564 retrieves a sensor reading from the next sensor element, which in this example is sensor reading 630 from sensor element 72. Sensor reading 630 is still below minimum sensor reading threshold 610. Therefore, the method again answers no to steps 520, 524 and 560 and proceeds to retrieve or gather a third sensor reading 640 in step 564. Only this time sensor reading 640 is above sensor reading threshold 610, so that the method proceeds to step 540 which determines if a first edge is stored. The answer is "no" because this is the first time that a sensor reading has exceeded the threshold, and sensor reading 640 is stored as the first edge, step 544. In one embodiment, step 544 stores the value associated with sensor reading 640 and/or the identification of sensor element 74 in memory device 112, but other embodiments are possible. The method proceeds to step 550 where a center of field analysis may be performed to determine the center or centroid of the magnetic field, as will be explained below. In the case of sensor readings 650, 660 and 670, the readings are above threshold 610 (step 520), a first edge has already been stored (step 540), and the last sensor element has not yet been reached or polled. Therefore, the method continues to perform a center of field analysis or calculation in step 550 (this can be a reiterative calculation). When step 520 compares sensor reading 680 with threshold 610 and determines that the reading is below the threshold, it will send the method to step 524 which will determine that a first edge has already been stored. Step 528 will then determine if a last edge has been stored (in this case the last edge is simply a second edge). And since a last edge has not been stored, step 532 will store one (again, this could be stored in memory device 112). Because sensor readings 680 and 690 are below minimum sensor reading threshold 610, they are not included in the center of field calculation.
When step 560 encounters sensor reading 690, it will determine that this reading corresponds with sensor element 84 which is the last or rightmost sensor in this particular example. The method may be set up so that the last sensor element in a particular sensor array constitutes the "last sensor element," or it could be set up so that the last sensor element in a particular sensor board constitutes the "last sensor array," to cite several examples. It is even possible for the first and last sensor elements to span several different sensor boards, as they are not limited to a single board. Now that the last sensor element is reached, the method proceeds to step 570 so that one or more calculations, analyses, evaluations, etc. may be performed. As mentioned above, method 680 may conduct any number of different analyses, and is not limited to the center of field analysis mentioned above. For instance, step 570 may determine if a magnetic field is present (because multiple sensor readings exceeded threshold 610, a magnetic field is likely present). Step 570 could determine a magnetic field width, which in this case is represented by distance 612. Magnetic field width may be provided in one of a variety of units, including numbers of sensor elements (three sensor units wide in the present example). Step 570 can provide a maximum magnetic field strength, which in this case may be the magnitude or Y-axis value of sensor reading 660. Extrapolation techniques may even be used to try and derive the maximum magnetic field strength value that lies between sensor readings 650 and 660. Other analyses, determinations and output may be generated at step 550.
Returning to step 550, there is provided a brief explanation of an exemplary "center of field" calculation that may be used to determine the center or centroid of the magnetic field that is produced by the magnetic strip on the ground that the AGV is following. The center of the magnetic field (CG), also referred to as the center of magnetic influence or center of gravity, may be determined by using Equation 1:
C   G := ∑ n = 1 N  m n · r G n ∑ n = 1 N  m n ( Equation   1 )
In the above Equation 1, (CG) is the center of field value or the center of the magnetic field, (mn) is a sensor reading for sensor element (n), (rGn) is a lateral distance from a fixed point on the AGV (e.g., the center of sensor board 14 or the center of the AGV) for sensor element (n), and (N) is the number of sensor elements included in the calculation (N would be 32 or less in the example described above). Summing the products of each sensor element location and the value of the corresponding sensor reading (i.e., the numerator), and then dividing by the sum of all the sensor reading values (denominator) may result in an ideal location or center location of highest field strength. This efficient approach weights the locations of the different sensor elements with the magnitude of their sensor readings, and is different from curve fitting approaches which may require much more processing resources and take more time to calculate.
In certain applications, the minimum sensor reading threshold 610 may be adjusted up or down and may allow other "regions of interest" to emerge. Equation 1 may be used as part of a method that can determine CG for all sensor readings, or for a subset of sensor readings corresponding to specific regions of interest. In one example, where the magnetic strip or tape laid out on the ground along the pre-determined path is limited to a single polarity (all facing north, south, etc.), individual or separate pieces of magnetic tape having the opposite polarity may be used as location markers. For example, if the main path around a factory floor is determined by a magnetic strip or tape that generates a north facing magnetic field, small sections of south facing tape can be used to identify the positions of docking or charging stations, or the like. Other techniques may also be used in lieu of or in addition to the center of field analysis provided above. t is to be understood that the foregoing description is of one or more preferred exemplary embodiments of the invention. The invention is not limited to the particular embodiment(s) disclosed herein, but rather is defined solely by the claims below. Furthermore, the statements contained in the foregoing description relate to particular embodiments and are not to be construed as limitations on the scope of the invention or on the definition of terms used in the claims, except where a term or phrase is expressly defined above. Various other embodiments and various changes and modifications to the disclosed embodiment(s) will become apparent to those skilled in the art. All such other embodiments, changes, and modifications are intended to come within the scope of the appended claims.
As used in this specification and claims, the terms "for example," "for instance" and "such as," and the verbs "comprising," "having," "including," and their other verb forms, when used in conjunction with a listing of one or more components or other items, are each to be construed as open-ended, meaning that that the listing is not to be considered as excluding other, additional components or items. Other terms are to be construed using their broadest reasonable meaning unless they are used in a context that requires a different interpretation.
1. A sensor system for use with an automated guided vehicle (AGV), comprising:
a sensor housing being attached to the AGV; and
a sensor board being at least partially located within the sensor housing and including a plurality of sensor units electronically coupled to a sensor control module, wherein each of the sensor units interacts with an indicating system that follows a pre-determined path along the ground and each of the sensor units includes: a sensor array having a plurality of sensor elements, the sensor elements take sensor readings regarding the position of the AGV with respect to the indicating system; a conditioning circuit being electronically coupled to the sensor array and having a plurality of filter/amplifiers, the filter/amplifiers process the sensor readings from the sensor array; and a conversion circuit being electronically coupled to the conditioning circuit, the conversion circuit converts the sensor readings from the conditioning circuit for transmission to the sensor control module.
2. The sensor system of claim 1, further comprising:
one or more additional sensor board(s) having a plurality of sensor elements, each of the sensor boards is electronically coupled to the sensor control module and is distinguished from the other sensor boards through the use of dipswitches.
3. The sensor system of claim 2, wherein the sensor boards include a snap-in connector located at one or more end(s) of the sensor board so that multiple sensor boards can be connected end-to-end.
4. The sensor system of claim 2, wherein the sensor boards extend in a generally parallel orientation across at least a portion of the width of the AGV and the sensor boards help the AGV navigate in a forward direction along the predetermined path.
5. The sensor system of claim 2, wherein one or more of the sensor boards extends across at least a portion of the width of the AGV and helps the AGV navigate in a forward direction along the pre-determined path, and one or more of the sensor boards extends along at least a portion of the length of the AGV and helps the AGV navigate in a sideways direction from the pre-determined path.
6. The sensor system of claim 1, wherein the plurality of sensor elements include magnetic field sensing elements that are able to evaluate both the strength and the direction of a magnetic field produced by a magnetic indicating system located along the ground.
7. The sensor system of claim 1, wherein the sensor control module is electronically coupled to the plurality of sensor units via a parallel communications and is electronically coupled with an AGV supervisory device via a serial communications.
8. The sensor system of claim 1, wherein the sensor housing is pivotally attached to an underside of the AGV so that the sensor housing can pivot out of the way when the AGV encounters an obstacle in the pre-determined path.
a sensor board being at least partially located within the sensor housing and including a plurality of sensor units electronically coupled to a sensor control module, wherein each of the sensor units interacts with an indicating system that follows a pre-determined path along the ground and each of the sensor units includes: a sensor array having a plurality of sensor elements for receiving sensor readings associated with position of the AGV with respect to the indicating system; a conditioning circuit being coupled to the sensor array for conditioning the sensor readings; and a conversion circuit coupled to the conditioning circuit to prepare the conditioned sensor readings for transmission to the sensor control module.
10. The sensor system of claim 9, further comprising:
11. The sensor system of claim 10, wherein the sensor boards include a snap-in connector located at one or more end(s) of the sensor board so that multiple sensor boards can be connected end-to-end.
12. The sensor system of claim 10, wherein the sensor boards extend in a generally parallel orientation across at least a portion of the width of the AGV and the sensor boards help the AGV navigate in a forward direction along the pre-determined path.
13. The sensor system of claim 10, wherein one or more of the sensor boards extends across at least a portion of the width of the AGV and helps the AGV navigate in a forward direction along the pre-determined path, and one or more of the sensor boards extends along at least a portion of the length of the AGV and helps the AGV navigate in a sideways direction from the pre-determined path.
14. The sensor system of claim 9, wherein the plurality of sensor elements include magnetic field sensing elements that are able to evaluate both the strength and the direction of a magnetic field produced by a magnetic indicating system located along the ground.
15. The sensor system of claim 9, wherein the sensor control module is electronically coupled to the plurality of sensor units via a parallel communications and is electronically coupled with an AGV supervisory device via a serial communications.
16. The sensor system of claim 9, wherein the sensor housing is pivotally attached to an underside of the AGV so that the sensor housing can pivot out of the way when the AGV encounters an obstacle in the pre-determined path.
17. A sensor system for use with an automated guided vehicle (AGV), comprising:
a pivotable sensor housing being pivotally coupled to the AGV; and
a sensor board being at least partially located within the sensor housing and including a plurality of detachably couplable sensor units electronically coupled to a sensor control module, wherein each of the sensor units interacts with an indicating system that follows a predetermined path along the ground and each of the sensor units includes: a sensor array having a plurality of sensor elements, the sensor elements take sensor readings regarding the position of the AGV with respect to the indicating system; a conditioning circuit being electronically coupled to the sensor array and having a plurality of filter/amplifiers, the filter/amplifiers process the sensor readings from the sensor array; and a conversion circuit being electronically coupled to the conditioning circuit, the conversion circuit converts the sensor readings from the conditioning circuit for transmission to the sensor control module.
18. The sensor system of claim 17, further comprising:
one or more additional sensor board(s) having a plurality of sensor elements, each of the sensor boards is electronically coupled to the sensor control module and is distinguished from the other sensor boards through the use of dipswitches, wherein the sensor boards include a snap-in connector located at one or more end(s) of the sensor board so that multiple sensor boards can be connected end-to-end.
19. The sensor system of claim 17, further comprising one or more additional sensor board(s) having a plurality of sensor elements, each of the sensor boards is electronically coupled to the sensor control module, wherein one or more of the sensor boards extends across at least a portion of the width of the AGV and helps the AGV navigate in a forward direction along the pre-determined path, and one or more of the sensor boards extends along at least a portion of the length of the AGV and helps the AGV navigate in a sideways direction from the pre-determined path.
20. The sensor system of claim 17, wherein the plurality of sensor elements include magnetic field sensing elements that are able to evaluate both the strength and the direction of a magnetic field produced by a magnetic indicating system located along the ground.
Publication Date: Aug 28, 2014
Applicant: Fori Automation, Inc. (Shelby Township, MI)
Inventor: Dean Allen Colwell (Lenox Township, MI)
Current U.S. Class: Storage Or Planning Of Route Information (701/25)
International Classification: G05D 1/02 (20060101);


text:
Judgment day looms for trademarks law
Only the courts will determine whether the Trade Marks Act offers adequate protection.
By Marketing Week	 25 Aug 1995 12:00 am
If the Yucatan Liquor Stand company has its way it will soon join an eclectic group of brand owners ranging from Coca-Cola to Sumitomo Tyres and AT&T.
The restaurant company has made one of the more bizarre applications to the Trade Marks Registry to have its interior registered. Under previous trademarks legislation it would have had no chance. Under the revised legislation introduced last November it has only a slim one.
Its application is made up of seven different elements: the look and feel of an American diner with exposed brickwork and timber; business cards pinned to the walls; tablecloths made of brown paper; rotating drinks machines dispensing cocktails; fishing nets hanging from the walls; lights in the shape of fish; and all accompanied by the sound of Country and Western music.
It is described as a "look and feel" application. To many it may sound more like their worst nightmare. The Registry concedes that it is the most bizarre application it has received to date.
"The look and feel makes the restaurants distinctive," says Ian Bartlett, a partner at Beck Greener, Yucatan's trademarks adviser. "If somebody copied it and a customer walked into a non-Yucatan restaurant they could be misled."
Ten months after it was introduced, The Trade Marks Act is starting to bear its first fruit. It simplifies registration, allows wider commercial protection to companies through a broader definition of what you can trademark, and makes infringement a criminal offence.
More than 400 applications have now been made to register product shapes, four to register smell, eight sounds and ten colours.
The Coca-Cola bottle will be the first shape to be registered (MW last week) having manoeuvred through a process that includes the initial application, acceptance by the Registry and then a 15-week, plus two days, "period of opposition" while the application is advertised in the Registry's magazine and can be challenged.
Ironically the first registration coincides with the Institute of Grocery Distribution putting the finishing touches to a code of practice on copycat products.
It was the creation of the British Producers Brand Owners Group (BPBOG) and its ensuing battle with major retailers last year that made the legislation controversial.
The brand owners claimed retailers were deliberately copying elements of design and piggybacking on their advertising and marketing spends.
The BPBOG tried to force the Government to beef up the draft legislation and outlaw copycat brands. The Government re-sisted but left the door ajar
by saying that the added protection given by the Act would be monitored.
As a consequence brand owning legal departments throughout the UK will study the progress of the shapes and sounds element of the Act as more products register and legal conflicts inevitably break out.
Rose scented tyres from Sumitomo will be the first smell, AT&T's advertising jingle the first sound, the Cadbury's purple the first colour.
The Derbyshire Building Society will join the fray with a man tapping his nose in a conspiratorial manner as the first registered gesture. All have been accepted by the Registry and now await advertising and the outcome of the opposition period.
Ironically the rose scented tyres have pipped Chanel No5 to be the first smell. The fragrance company's application was rejected on the grounds that it was too imprecise, highlighting the difficulty of describing a smell graphically.
"It (the Act) extends brand ownership rights," says David Rickard at trademark specialists Boult Wade Tennant. "It provides protection for distinctive commercial elements. It is working in terms of what it set out to achieve but it is too early to say how effective the legislation will be in giving full protection."
Other trademark experts are more blunt. "Until it is tested in court the trademark owners and lawyers will not be convinced that it gives protection," says Janet Fogg, managing director at Interbrand, a BPBOG member. "It does not deter unfair competition where specific features of shape, smell, sound or colour are not copied and it does not prevent lookalikes.
"Individual features can be protected but it depends on which aspect is copied. Infringers only have to make limited alterations to avoid being sued for infringement. It highlights a gap in the legal system."
The Act is having an increasing impact on manufacturers' production decisions. In the US Coca-Cola has created a redesigned Sprite bottle with 3D bubbles on its surface which it will test market in the UK and other areas. Sources suggest that one of the reasons for the redesign, apart from making it distinctive on the shelf, was to protect it via the Trade Marks Act.
The Yucatan Liquor Stand has clearly designed its interiors to win the same protection. It is just lucky that the Registry does not base its judgments on taste, and style.

redpajama_set_name: RedPajamaCommonCrawl


text:
"America's Greatest Comic Book Convention!" returns October 28-30, 2022
COVID Safety Precautions
Exhibit Hall Map
Baltimore Comic-Con Weapons Policy
ASL Services request
Media Guests
Costume Contest Info
Ringo Awards
Tickets on sale now!
BALTIMORE COMIC-CON 2022 GUEST
Steve Conley
Writer and Artist
The Middle Age, Astounding Space Thrills, Star Trek, BLOOP
Long-time friend of the show, Ringo, Harvey, and Eisner Award nominee, and guest since our inception in 2000 (!), artist and writer Steve Conley has contributed to numerous comic titles, both printed and on-line. His Astounding Space Thrills was self-published, published by Image Comics, and collected as a trade paperback by IDW. He has been featured in titles such as JLA-Z from DC Comics, Star Trek: Year Four from IDW, and Michael Chabon's Amazing Adventures of the Escapist from Dark Horse Comics. His self-published BLOOP is available through his online store in print or soft copy editions, and you can find his Ringo and Eisner Award-nominated webcomic The Middle Age on his website, tapas.io, Line Webtoon, and GoComics, and hard copies and digital collections can be purchased from his online store.
https://middleagecomic.com/
https://www.patreon.com/steveconley
https://twitter.com/theSteveConley
https://www.facebook.com/americas.favorite.steve.conley
https://www.instagram.com/steveconley/
More Baltimore Comic-Con 2022 guests...
Klaus Janson
Friday and
Joseph Michael Linsner
Don Rosa
Afua Richardson
Thom Zahler
#baltimorecomiccon
The Baltimore Comic-Con is presented by Cards, Comics & Collectibles of Reisterstown, Maryland.
Copyright Baltimore Comic-Con 2022 - All Rights Reserved


FOXBOROUGH — Thirty years ago this month, the NFL was in chaos.
In the fall of 1987, the players, seeking unqualified free agency, had decided to go on strike after the second week of games, thinking the move would give them leverage with the networks. The owners would cower in the face of their massive TV contracts and return to the bargaining table. Right? But the owners called their bluff and decided to retaliate by bringing in replacement players, and the networks acquiesced to the idea of replacement football.
Across the league, the battle was on, as the NFL tried to come to grips with a bizarre stretch of football that would, in many ways, come to define the 1987 season. Every team had to find a way to survive through that stretch, one that pitted owners against players, and, in some cases, players against players. What follows is an oral history of the 24 days of replacement football in New England, and all the hoopla that came with it.
When the idea of replacement football was first broached, the Patriots, like everyone else, had to scramble to put together a roster. GM Pat Sullivan, coach Ray Berry and the rest of the New England braintrust ended up finding a handful of players who had either been with them the previous year or two in camp, scout-team types that were hungry for a shot at the big time. That group was soon augmented by a few veterans who decided to cross the picket line. Running back Chuck McSwain, whose brother Rod was already on the roster as a linebacker, was one of the guys who got the call as a replacement. A former fifth-round pick of the Cowboys out of Clemson, he was on the fence -- until he talked to his brother.
Regardless, it became clear the Patriots were in better shape than some other teams around the league. The Giants, who were defending Super Bowl champions, had struggled to assemble a team, and it was soon evident they were in trouble.
But there were still some memorable moments in that one. Defensive lineman Murray Wichard, an undrafted free agent, was fired up to get on the field, and got his first sack against the Browns.
Their next game, a Week Five contest against the Bills at Sullivan Stadium. It was this game where the players started to realize how much the region had started to rally around them. In front of what was the smallest Sullivan Stadium crowd ever —11,878 rain-soaked fans — and while striking players again walked the picket line outside, the replacement guys felt the embrace of the New England fans.
Running back Michael LeBlanc, who was released by Winnipeg of the CFL that offseason, was signed by the Patriots as a replacement, gained 146 yards on 35 carries. The win over Buffalo was the first for the replacement Patriots, and appeared to buy them some goodwill with local fans.
The rest of the NFL raged around them — in Houston, the striking Oilers hurled eggs at a bus carrying the replacements and broke a window with a rock. In Kansas City, some veterans showed up with shotguns. In Washington, regulars belittled replacement players, in some cases, heckling them from outside the fence during practice. And in other cities, angry players stood in front of cars and buses to prevent entry into stadiums. But things were pretty quiet in Foxborough.
The defense was clearly the strength of the replacement team. After having some serious issues in their first game against a Cleveland team that would eventually reach the AFC title game against the Broncos, the Patriots allowed just two touchdowns in their two other contests. They not only had a handful of established players crossing over at that point, but the defensive players there became adept at camouflaging some of their weaker aspects.
Others weren't so fortunate, especially on defense. Belichick's Giants gave up 85 points in the three games.
For the Patriots, things came together nicely for them on both sides of the ball in their last game for a few reasons, not the least of which was the fact that they added Flutie to the roster. The former Boston College star had fallen out of favor in Chicago, but had still publicly taken a strong stand against players who crossed the picket line. But the opportunity to play for his hometown Patriots proved too great to pass up.
GM Patrick Sullivan: "His overriding concern was to come home. We knew he wanted to come back to Boston, and he felt this was his opportunity to prove he could play in the NFL."
Flutie had to learn the offense quickly — four days, to be specific.
The players agreed to return to work after the second game, but because the players ended their strike on a Thursday, they were told by the owners they had missed the deadline for being eligible to play in Week Six by one day. That would mean one more week of replacement football. And so, with four days of practice under his belt, Flutie and the Patriots took off for Houston to face the Oilers. Of their three games, it would be the only road contest for the replacement players.
In the win over the Oilers, Linne was the offensive star with four catches for 81 yards and a touchdown. He also caught Flutie's first pass with the Patriots.
Flutie finished with 242 total yards of offense (199 passing, 43 rushing). He was the unquestioned star of the show, both during and after the game.
With the end of replacement football was in sight. Flutie was still clearly unsure if he did the right thing by crossing the picket line. "What I'm doing is something I still think is not right. But it's a move I feel I had to make," he said. "Three years down the road, if I'm still with the New England Patriots, it'll be the best decision I've ever made." Some of his teammates shared the same sentiment.
A handful of the replacement players used it as a way to gain a foothold in the league, and several of them ended up sticking around Foxborough in some form or fashion. But for many of the others, it was the last chance to put the pads on. Thirty years later, they look back on their experience with great fondness.
Thirty years later, the replacement Patriots remain a footnote in franchise history. But many of them remain fans of the franchise and would love an opportunity to come back and thank the ownership and fans for their support through that memorable stretch.


text:
Home Nigerian News Uju Ayalogu's Blog BREAKING: South East Govs Disown IPOB, Say Secessionist Group Not Speaking For Igbos
BREAKING: South East Govs Disown IPOB, Say Secessionist Group Not Speaking For Igbos
Governors in the Southeastern part of Nigeria, under the umbrella of South East Governors' Forum in a meeting in Enugu on Saturday have declared that members of the Indigenous People of Biafra, IPOB are not speaking for the entire region on the call for secession.
However, the governors warned the security agencies in the region to stop killing Igbo youths, and urged them to respect their rights, while condemning the attacks on security infrastructures in the zone.
The meeting was a follow up to the consultation the Presidential delegation, led by the Minister of Defence, Major General Bashir Magashi (retd), had with the Igbo leaders, on June 11, 2023, on the security challenges confronting the region in particular and Nigeria in general.
Chairman South-East Governors Forum and Governor of Ebonyi State, Chief David Umahi, who read the resolutions of the leaders assured all Nigerians living in the South-East region that they have no reason to fear or leave the region.
Umahi in the same vain appealed to leaders of other regions to ensure the protection of Igbos living in their regions, noting that they have uncovered some threats against Igbos living in other parts of the country by their people.
The communique read in parts, "Arising from the meeting of 11th of June 2021, with the presidential team led by the Minister of Defence, Major General Bashir Magashi (retd), we the South-East people agreed to a further meeting with them as requested by them.
"Consequent upon that, we scheduled our own meeting today the 19th of June to enable us discuss as brothers and sisters and articulate our positions to enable us to not only engage the presidential team but also engage our people over all burning issues.
"The meeting set up committees under the Ohanaeze to articulate and address our position on all burning issues to further meet among ourselves and thereafter meet with the presidential team.
"We the Igbos do reaffirm our commitment to one United Nigeria under a platform of justice, equality of rights, fairness, love and respect for one another.
"We have noted threats by some groups in some other regions against our people of South-East while we firmly promise to protect every one either from our own region or other regions living in our places.
"We plead with leaders of other regions to please note the threats to our people and to please address the threats to our people and to protect them.
"We condemn the killing of security agents, the burning of strategic infrastructures and killing of civilians in South-East and even in other regions.
"We request our security agencies to please discharge their duties within the rules of engagement and the law.
"We request our National Assembly members from South East to please support state police creation in the ongoing constitutional amendment.
"We condemn in totality the activities of violence secessionist groups in South East and elsewhere. We firmly proclaim that we do not support them and they do not speak for South-East."
They, however, rejected the impression that the leaders were silent over youths agitation for secession in the South-East, describing such notions as incorrect.
They noted, "South-East Governors, Ohanaeze President, our National Assembly members and notable leadership from South-East had come out publicly many times in the past including Ministers from the South-East to speak against such agitations.
"In order not to mismanage the unfortunate situation we found ourselves, South-East leaders have set up a committee to engage such youths to stop and allow the elders of the south east to address their fears."
He added, "Meeting directed our governors and Ohanaeze Ndigbo to liaise with indigenes of northern part of Nigeria and other indigenes of other regions that are living in the South-East to come out openly and to assured their people of course the nation Nigeria that they are very safe and well protected while living in south east.
"The meeting endorsed our South-East Joint Security outfit 'Ebubeagu' and ask all the personnel of Ebubeagu to work with the security agencies and to respect the rights and privileges of all those living in the South-East and her visitors."
Leaders in attendance are, Governors of Enugu, Ifeanyi Ugwuanyi; Ebonyi, David Umahi; Abia, Okezie Ikpeazu; deputy Governors of Anambra, Nkem Okeke and Imo, Prof Placid Njoku.
Others are former deputy President of the Senate, Prof. Ike Ekweremadu; Senate Minority Leader and the Chairman South East National Assembly Caucus, Senator Enyinnaya Abaribe, Senator Sam Egwu.
Other notable leaders in attendance are Chief Emmanuel Iwuanyanwu, President General of Ohanaeze Ndigbo, Prof George Obiozor; Chief Nnia Nwodo, Minister of State for Steal and Mining, Dr Uche Oga; Minister of Labour and Productivity, Senator Chris Ngige.
Also, Catholic Bishop of Enugu Diocese, Most Rev Callistus Onaga; Bishop of Nsukka Catholic Diocese, Most Rev Geoffrey Onah; Anglican Archbishop of Enugu Provence, Most Rev Emmanuel Chukwuma; Methodist Bishop of Enugu, Dr Christopher Ede; Chairman, Christian Association of Nigeria, CAN, Most Rev Emmanuel Ede among others.


text:
Q: classicthesis / A Classic Thesis Style I am trying to use the following LaTeX style that can be seen here classicthesis / A Classic Thesis Style
However, I need to configure to accept the Greek language. I followed the instructions I found here that apparently allow one to write in Spanish classicthesis / SpanishLanguageSupport, but when i try to do the same with Greek, I get a ton of errors !!!
Any, help or pinpointing to the right direction will be appreciated!!!
Many Thanks,
Viktor

A: Since some years, classicthesis can use the book class.
\documentclass[a4paper]{book}
\usepackage[greek]{babel}
\usepackage{classicthesis}
\usepackage{substitutefont}
\hypersetup{unicode}

\substitutefont{LGR}{\rmdefault}{artemisia}

\begin{document}

\mainmatter

\chapter{Αθήνα}

Η Αθήνα είναι η πρωτεύουσα της Ελλάδας από το 1834 και η μεγαλύτερη πόλη της.
Βρίσκεται στην Αττική, στην ανατολική Στερεά Ελλάδα, και είναι από τις αρχαιότερες
πόλεις του κόσμου, με την καταγεγραμμένη ιστορία της να φθάνει ως το 3.200 π.Χ.
Η Αρχαία Αθήνα, αρχικά οικισμός πάνω στην Ακρόπολη, εξελίχθηκε τον 6ο αιώνα π.Χ.
σε μία πανίσχυρη πόλη-κράτος, που αναπτύχθηκε παράλληλα με το λιμάνι της, το οποίο
αρχικά ήταν το Φάληρο και αργότερα ο Πειραιάς. Υπήρξε, κατά την κλασική εποχή,
κέντρο των τεχνών, της γνώσης και της φιλοσοφίας, έδρα της Ακαδημίας του Πλάτωνα
και του Λυκείου του Αριστοτέλη. Αναφέρεται ευρέως ως γενέτειρα της δημοκρατίας.
Συχνά, η Αθήνα, όπως και γενικότερα η Ελλάδα, χαρακτηρίζεται «λίκνο του
δυτικού πολιτισμού», ενώ άλλες φορές, ο τίτλος αυτός αποδίδεται στη Μεσοποταμία.
Η σύγχρονη Αθήνα είναι το κέντρο της οικονομικής, βιομηχανικής, πολιτικής και
πολιτιστικής ζωής της Ελλάδας. Σύμφωνα με την Ευρωπαϊκή Στατιστική Υπηρεσία,
η Ευρύτερη Αστική Περιοχή της Αθήνας, η οποία ουσιαστικά συμπίπτει με την
Περιφέρεια Αττικής, είναι η 7η πολυπληθέστερη στην Ευρωπαϊκή Ένωση, με τον
πληθυσμό της να εκτιμάται το 2004 στους 4.013.368 κατοίκους.

\end{document}

You need to substitute the font for Greek, because the standard Palatino font has no support for Greek.
Text is from https://el.wikipedia.org/wiki/Αθήνα

A: Well, let me say it in this way:
Class classicthesis is known to be problematic, it can cause a lot of troubles. For example it uses packages that shoud better not used with KOMA-Script classes classicthesis is based of ...
Because I do not speak greek let us use package blindtext in the following mwe:
\RequirePackage{silence} % :-\
    \WarningFilter{scrreprt}{Usage of package `titlesec'}
    %\WarningFilter{scrreprt}{Activating an ugly workaround}
    \WarningFilter{titlesec}{Non standard sectioning command detected}
\PassOptionsToPackage{greek}{babel} % <=================================
\documentclass[%
  twoside,
  openright,
  titlepage,
  numbers=noenddot,
  headinclude,
  %1headlines,
  footinclude=true,
  cleardoublepage=empty,
  dottedtoc, % Make page numbers in the table of contents flushed right with dots leading to them
  BCOR=5mm,
  paper=a4,
  fontsize=11pt, % Binding correction, paper type and font size
  greek, % <============================================================
]{scrreprt}

\input{classicthesis-config}

\usepackage{blindtext}

\begin{document}
\selectlanguage{greek} % <==============================================

\Blinddocument
\end{document}

Please see that the usage of package silence is to get rid of the warnings resulting in packages better not to use with KOMA-Script.
The resulting pdf of the mwe is then:

I got 37  warning messages (warnings are no error messages!) resulting from blindtext not knowing greek (perhaps you can help there?) and from issues with the used font.
Both issues I can not solve, because you gave no MWE in your question and I do not know which font you are using writing greek and I can not add all needed greek text to blindtext. Perhaps you can help here, that is the part of the documentation of blindtext naming what is needed to add greek to it:

The documentation you can find with texdoc blindtext in your terminal/console, there you find the email to contact the author of that package with needed infos ...
And you can add an mwe to your question with real greek text, showing your used font and resulting in the "tons of errors" you mentioned.
For me it seems you can use greek as I showed you in my mwe, but be aware that template classicthesis is known to produce bad surprises for users. If possible, use another template or be aware of other problems comming up soon!

redpajama_set_name: RedPajamaStackExchange


text:
The Best CRM Systems Of 2020 According To Companies Using Them
76% Of Enterprises Prioritize AI & Machine Learning In 2021 IT Budgets
How Data And AI Can Help Create A Mobility Renaissance
Amazon To Let Automakers Use Alexa Assistant For Cars
Voulez-Vous Parler Social Networks' Content Moderation Policies?
Five New Year's Resolutions For Cryptocurrency
The Top 5 Consumer Technology Trends From CES 2021
How Startup ThreeFlow Is Transforming How Benefits Are Sold Using Machine Learning
Dilemma of Customers' Increased Productivity or Service Providers' Profitability
Covid-19 Offers The Opportunity To Redesign The Physical Office
Nov 12, 2019, 08:27am EST |
Kenyan Public WiFi Sensation BRCK Launches In South Africa
Toby ShapshakSenior Contributor
I write about how innovation is better in Africa.
Facebook CEO is shown a SupaBRCK by BRCK CEO Erik Hersman, while Juliana Rotich looks on.
BRCK
Internet provider BRCK is launching its free internet service in South Africa, having expanded this year to become the largest supplier of public WiFi in Sub-Saharan Africa.
BRCK CEO Erik Hersman made the announcement at the AfricaCom conference in Cape Town, which is the largest telecoms industry conference in Africa.
"I'm excited to be back in South Africa, where the idea for BRCK began, and excited to be bringing equitable internet to South Africa as we have in Kenya," he told me.
Part of this excitement, he says, is because the country has "the most developed country on the continent and represents a business customer market that is a lot further along. At the same time there's a vast number of South Africans with smartphones who can't afford the internet costs, so there seems to be a perfect storm for Moja WiFi to operate in."
BRCK is a remarkable Kenyan company that is bringing internet access to East Africa. Earlier this year it acquired Surf, another internet provider, to become the largest public WiFi network in Sub-Saharan Africa. It is currently in 2,700 locations in East Africa and has 700,000 monthly active unique visitors.
"More than 7 million sessions each month means that we're providing a much-needed service to a market in need of real answers," he says.
BRCK was formed in 2013 by some of the co-founders of Ushahidi and Nairobi's iHub as a means of countering Kenya's notorious power failures with a ruggedized portable hotspot, called BRCK v1. It expanded into education with its Kio Kit that brought multimedia video education into classroom across East Africa. In 2017 it launched a smart system called SupaBRCK which aimed to solve the lack of internet access in Africa by bringing the internet to rural villages. Moja is the operating system and ecosystem that runs the BRCK devices, and provides added value for users.
Although many companies provide internet access – and Google Station launched in Cape Town a week before – BRCK is vastly different because of the Moja business model which gives free internet access.
SEC V. Ripple: The Cryptocurrency Trial Of The Century
Revolutionary NLP Model GPT-3 Poised To Redefine AI And Next Generation Of Startups
China Aims To Dominate Flash Memory
"We work from where the African internet user is, not where we wish they were," says Hersman. "We understand that their wallets are rigid and that they cannot pay, therefore our business model is setup to make our revenue from our business customers and instead have our users earn their internet with time, not money."
SupaBRCK devices are fitted to taxis in Kenya, known as matatu, and provide internet access for commuters, amongst other public spaces.
"Moja differs from other public WiFi as it is free for the consumer. They don't need to pay anything to get online or to access premium content. While most just try to charge less for their service, at BRCK we realized that there just wasn't the ability for the majority of smartphone owners in Africa to pay at all.
"The uniqueness of Moja is found in a business model that monetized people's abundance of time and subsidizes that internet connection with our business customers connecting to our user with some form of digital work.
"Moja monetizes people's time, and creates a marketplace for them to use that value that they've earned for internet, subscriptions for premium content, and even services like insurance. This will only continue to grow as the network and Moja platform proliferates across South Africa."
For Hersman, it's poignant that the announcement was made at AfricaCom because he had the original idea while travelling back to Kenya after attending the conference in 2011.
"As I was leaving Cape Town to head back to Nairobi that I had a conversation that would change the trajectory of my life," he told me. His friend Henk Kleynhans whose startup SkyRove that created software for hotels, cafes and restaurants to get their customers online.
"On the flight home that evening I was sitting on the airplane and I couldn't stop thinking of a specific problem, which was why we were using routers and modems not designed for our African context, and started to wonder if we could build something better."
With no battery left in his laptop or smartphone, Hersman sketched ideas in his paper notepad, envisaging a brick-sized form, with a big battery and redundant SIM for when the ethernet access went down. "It was simple, and I called it BRCK."
South Africa is an interesting market with a wide swath of smartphone users, many who cannot afford data bundles, but is mixed with a more mature business market than is found in any other African country.
"We're already inking deals with some great FMCG suppliers, banks, and insurance companies."
But importantly, he says, Moja is supporting African creatives. "We're onboarding more of the top-level content creators from this hotbed of talent. With Moja I think we've finally found a way to connect Africans to the internet, and a way to monetize Africa's content creators."
Toby Shapshak
I write about how innovation is better in Africa. I define innovation as solving problems, like the real problems we have in Africa. And solving those problems solves
I write about how innovation is better in Africa. I define innovation as solving problems, like the real problems we have in Africa. And solving those problems solves them for the rest of the world. Africa isn't just mobile-first, it's mobile-only. I spoke about this at TED Global in June 2013 ( http://www.ted.com/talks/toby_shapshak_you_don_t_need_an_app_for_that ); and have spoken at various conferences, including SxSW in Austin (four times), Intel's IDF in San Francisco, and The Guardian's Activate: Johannesburg. I'm the editor-in-chief and publisher of Stuff magazine and write a weekly column for the Financial Mail, both in South Africa. As a reporter, I shadowed Nelson Mandela when he was president, and covered the Truth and Reconciliation Commission. I've been writing about innovation, telecoms, and the internet and the impact it has on our lives for more than 20 years, for a variety of publications, including CNN, The Guardian (London), Sunday Times and The Times (South Africa).


text:
Josué Anunciado de Oliveira (*Vitória de  Santo Antão, Brasil, 19 de julio de 1979), conocido como Josué, es un exfutbolista brasileño, jugaba en la posición de mediocampista y su último equipo fue el Clube Atlético Mineiro de Brasil.

Selección nacional

Selección de fútbol de Brasil, ha jugado 28 partidos internacionales y le marco un gol a Chile en la Copa América 2007, además de participar en la Copa Mundial de Fútbol de 2010.

Clubes

Campeonatos regionales

Campeonatos nacionales

Copas internacionales

(*) Incluyendo la selección

Futbolistas de Brasil en la Copa América 2007
Futbolistas de Brasil en la Copa FIFA Confederaciones 2009
Futbolistas de Brasil en la Copa Mundial de 2010
Futbolistas del Goiás Esporte Clube
Futbolistas del São Paulo Futebol Clube
Futbolistas del VfL Wolfsburgo en los años 2000
Futbolistas del Clube Atlético Mineiro
Futbolistas del VfL Wolfsburgo en los años 2010

redpajama_set_name: RedPajamaWikipedia