Jump to content
43oh

cde

Members
  • Content Count

    940
  • Joined

  • Last visited

  • Days Won

    21

Reputation Activity

  1. Like
    cde reacted to drkm in TI releasing something "game changing" on Sept 16th   
    I heard about this a few weeks ago from our AVNET sales guy. Its super exciting!
     
    Apparently the automotive guys are going nuts over it since they can now get high resolution data with simple/cheap components without having to worry about hi-temp components. Think ABS, brake sensors, sensors closer to the combustion chamber, ect.
     
    Even for motor control/robotics applications this is huge, especially the resolution you get out of this thing!
  2. Like
    cde reacted to Mark Easley TI in NY Maker Faire   
    TI will be having a booth at the World Maker Faire in Queens, NY on September 21 & 22.  We'll be showing off some pretty awesome new additions to the TI ecosystem (*cough* *cough* New LaunchPad *cough*), stacks on stacks of BoosterPacks, Energia demos, and we'll be giving away some cool items. If you are in the area, stop by and chat us up!  Should be an amazing event.
     
    Aside from launching new BoosterPacks, we are working with different 3rd Parties, like our friends at Element14, to enable Makers and 43oh members to design their own.  Look out for new resources available at www.ti.com/byob in the coming months. 
  3. Like
    cde reacted to RobG in Geek Clock BoosterPack   
    Do you know what time it is?
    It's geek time! He, he.
     

     
    rgbClkBP-3.pdf
     
    First, test pattern.
    Red - seconds, green - minutes, blue - hours, runs 20x times faster to show changes.
     

     
     
  4. Like
    cde got a reaction from bluehash in Neat ws2811 "Water Torture" effect   
    Not 430, but the video made it look very cool.
     

     
    Source code available
    http://rurandom.org/justintime/index.php?title=WS2811_%22Water_torture%22
    https://github.com/DannyHavenith/ws2811/blob/master/src/water_torture.hpp
  5. Like
    cde got a reaction from JWoodrell in Neat ws2811 "Water Torture" effect   
    Not 430, but the video made it look very cool.
     

     
    Source code available
    http://rurandom.org/justintime/index.php?title=WS2811_%22Water_torture%22
    https://github.com/DannyHavenith/ws2811/blob/master/src/water_torture.hpp
  6. Like
    cde got a reaction from oPossum in Neat ws2811 "Water Torture" effect   
    Not 430, but the video made it look very cool.
     

     
    Source code available
    http://rurandom.org/justintime/index.php?title=WS2811_%22Water_torture%22
    https://github.com/DannyHavenith/ws2811/blob/master/src/water_torture.hpp
  7. Like
    cde got a reaction from suf in LaunchPad Web Server - control your LP over the network   
  8. Like
    cde reacted to simpleavr in Bug with PxOUT + INPUT_PULLUP?   
    What you are describing (flipping BIT0 only) does not agree w/ your code.
     
    I assume it's the line you commented out that's offending.
     
    i.e
     
    P1OUT ^= 00000011;
     
    This is not binary but decimal. The device sees it in hex as 0x0b or binary as 0b00001011.
     
    This would toggle the bits 0, 1 and 3 which would upset your button.
     
    Or did you paste your actual code accurately?
  9. Like
    cde got a reaction from tripwire in Problem with bit wise operation   
    It's set up that way because it's easier for them to reuse a register, than to have an extra register that's only used if p1ren is set. And because the msp430s have both pull-ups like most mcus, but also have pull-downs, unlike AVRs or PICs. So they need a register to define which level the pin is at, 0 or 1. Since P1Out determines that anyway, they reused the same register.
     
    Setting P1Ren doesn't affect p1out for the same reason, since there is pull ups AND pull downs, they use whatever is in p1out to determine which resistor is used. If setting p1ren overrided p1out, it could cause issues.
     
    As for destroying the pin or mcu, no, because with the r1.5 launchpad, the p1.3 button has no external pull up. Without the external pull up, if you set no internal pull resistor, the line would be either floating (when the button is not pressed) or directly grounded (when the button is pressed). With a pull-down enabled and a button that pulls to ground, the pin would always be at ground, so there is no short circuit. The only way to possibly damage the mcu (Without adding external components) would be to have p1.3 set to output high, then pressing the p1.3 button. Direct short of vcc to ground.
     
    As a note, the r1.4 launchpad does have the external pull-up 47k (and cap) on the p1.3 line. Had you enabled the internal pull-down, which is roughly 50k, the two resistors would have created a voltage divider and the voltage at the pin would have been roughly half VCC (~1.85v), which might not be enough to trigger the voltage level change at that pin.
  10. Like
    cde reacted to roadrunner84 in Problem with bit wise operation   
    There are five properties of a digital I/O pin:
    PxIN: the input value PxOUT: the output value PxDIR: the pin direction (input/output) PxREN: the resistor enable PxSEL(2): the special function First and foremost, the behaviour of the pin can be different for every pin when it is in second/third/fourth function mode, so the rest of the story only holds when PxSEL is 0 and if it exists PxSEL2 is also 0.
    Now then, PxIN holds the read back value, it always does, no matter the other three properties. However, when the pin is set as output PxIN will hold the output value, not the actual level of the pin.
    PxDIR | PxIN ------+----- 0 | Pin level 1 | PxOUT level PxREN enables the resistor, this means that the pin is connected via a resistor to PxOUT. As a consequence the voltage on the pin can be overridden by external driving high or low. Contrary to intuition (at least mine), PxREN does not change behaviour depending on PxDIR.
    PxOUT determines the output drive level, this value is ignored if PxDIR is 0 and PxREN is 0.
    PxDIR is the direction, 1 is output, 0 is input. When PxREN is low, this changes the pin from diriving high or low to the pin being a floating (high impedance, HiZ) input pin. However, if PxREN is enabled, PxDIR does not change the pin from driving to floating. If PxDIR is 1 however, PxIN will hold the value of PxOUT, not the actual pin level!
    PxOUT PxDIR PxREN external | PxIN external ---------------------------+-------------- 0 0 0 0 | 0 0 0 0 0 1 | 1 1 0 0 0 HiZ | ? HiZ PxIN logic may become unstable; undesired power dissipation 0 0 1 0 | 0 0 0 0 1 1 | 1 1 0 0 1 HiZ | 0 0 Pull-down enabled 0 1 0 0 | 0 0 Driving an output pin; not recommended; may damage circuit 0 1 0 1 | 0 short High current influx; may damage circuit 0 1 0 HiZ | 0 0 0 1 1 0 | 0 0 0 1 1 1 | 0 1 Pin voltage ignored; PxIN equals PxOUT 0 1 1 HiZ | 0 1 Pull-up enabled. Pin voltage ignored; PxIN equals PxOUT 1 0 0 0 | 0 0 1 0 0 1 | 1 1 1 0 0 HiZ | ? HiZ PxIN logic may become unstable; undesired power dissipation 1 0 1 0 | 0 0 1 0 1 1 | 1 1 1 0 1 HiZ | 1 1 Pull-up enabled 1 1 0 0 | 1 short High current outflux; may damage circuit 1 1 0 1 | 1 1 Driving an output pin; not recommended; may damage circuit 1 1 0 HiZ | 1 1 1 1 1 0 | 1 0 Pin voltage ignored; PxIN equals PxOUT 1 1 1 1 | 1 1 1 1 1 HiZ | 1 1 Pull-up enabled
  11. Like
    cde reacted to spirilis in New Hercules LaunchPads   
    I think the dual cores are meant to run in lock-step, for redundancy & accuracy-checking purposes.  Also has ECC (error correction) for its flash & SRAM.  Probably massive overkill for the vast majority of applications but when you want that extra bit of assurance that your MCU application will WORK, (basically) no matter what (firmware bugs notwithstanding)... sounds like this is a good choice for the job.  Design an electric car's control systems around something like this.  It adds extra measures to help dial out hardware externality-induced failure modes.  I think the temperature tolerances are wider too, so this is immediately useful for extreme temperature applications.
     
    I'm guessing not too many hobbyists will have immediate uses for these features, but if anyone does it will make for a very fascinating hackaday article
     
    If Iron Man used a TI microcontroller for his suit, this would probably be it....
  12. Like
    cde reacted to chicken in New Hercules LaunchPads   
    @@cde @@simpleavr re differences
     
    More RAM (12-32KB vs. 32-256KB), more flash (32KB-256KB vs. 256KB-3MB), more speed (80 vs. 80-220MHz, single vs. dual core)
    http://www.ti.com/lsds/ti/arm/overview.page
     
    But I guess the big differentiator is compliance with various industry, medical, automotive standards (not really relevant to hobbyists).
  13. Like
    cde got a reaction from Fabinhou in Problem receiving ACK on I2C communication [MSP430g2553]   
    7 bit address 0111101 or 0x3D, 8 bit 01111010 write 0x7A 01111011 read 0x7B
  14. Like
    cde got a reaction from Fabinhou in Problem receiving ACK on I2C communication [MSP430g2553]   
    The USCI system is smart. It handles the read/write bit itself. You would still give the slave address of 0x3C for reads.
  15. Like
    cde got a reaction from Fabinhou in Problem receiving ACK on I2C communication [MSP430g2553]   
    Is this OLED have a schematic? Is it a pre-made board?
     
    Just double checking, on the OLED the Bus Select pins BS0 and BS2 are tied low with BS1 tied high right? Otherwise it is not in i2c mode. And is the OLED 5v or 3.3/3.6v logic? The IC has options for both. Is CS#, R/W#, E and D7-D3 pulled low? This is required for i2c communication. Is D2 and D1 tied together? These two pins are the SDA line. D0 is the SCL line.
    Do you have external pullups on the d2/d1/d0 lines?
     
    If the SDAout pin (I think D2) isn't connected, you won't get any acks. Meaning it would be write only with no i2c acks, not standard, you would have to code around that. (See the pdf 5.1.4 ( for info on that, it won't let me copy and paste the info)
     
    The Slave address you use is 0x78. That's Binary 0b01111000. That indicated that the D/C# (SA0) line is tied low, is that correct?
    That's an 8 bit address, including the write/read bit. The 7 bit address is 0x3C (0b0111100). I Think the USCI system requires a 7 bit address, not including the write/read bit, to be used. In that case, you are trying to write to the wrong address. Googling shows this to be correct. Try the 7 bit address, that might be the problem.
     
    Make sure you have the i2c pins correct. P1.7 is SDA, P1.6 is SCL
  16. Like
    cde got a reaction from abecedarian in Please do not steal articles messages   
    Try changing your browser user agent to something like firefox or safari, see if you get the same message. If a script thinks your useragent is a bot that copies pages, that would explain it.
  17. Like
    cde got a reaction from calin in Has TI 's samples policy changed ?   
    You have to put "Independent Designer", unless you work for a big company or something. The 5 items, y number per items depending on which category they decided you are is still the same for two three years now (for example, 2 limit of any individual microcontroller, 5 for some individual regulators, 1 of any regulator module, etc if you are an independent designer/regular student). It used to be 8 quantity of any 8 parts, but that was years ago.
  18. Like
    cde got a reaction from GeekDoc in Has TI 's samples policy changed ?   
    You have to put "Independent Designer", unless you work for a big company or something. The 5 items, y number per items depending on which category they decided you are is still the same for two three years now (for example, 2 limit of any individual microcontroller, 5 for some individual regulators, 1 of any regulator module, etc if you are an independent designer/regular student). It used to be 8 quantity of any 8 parts, but that was years ago.
  19. Like
    cde reacted to mbeals in Wireless model rocket telemetry   
    This is a continuation of a thread I made here: http://forum.43oh.com/topic/3973-mcu-wireless-networking-question/#entry36033
     
    Since we ordered hardware, I figured it was time to start documenting the build.
     
    Background:
    We applied for (and received) a small grant from NASA to build an educational activity for high school kids about the physics of rocketry.   The idea is to allow the kids to design, build and test their own rockets and provide them real time feedback on the performance.  Using this, we will teach them about the concepts of ballistic motion, force, impulse, thrust, etc...
     
    We want a way to measure, log and graph the various forces acting on the rocket during flight without the measuring, logging and graphing getting in the way.  So we decided the best way was to wirelessly transmit a data stream from the payload to a base station which could read, process and graph the data in real-time, maximising the time the students have to conduct experiments.
     
    Design:
    There are two main components to this project, the payload that is contained in the rocket and the base station;
     
    The payloads:
    The current plan for the payloads is going to be a TI sensor tag (thanks @cde) with custom firmware broadcasting a data stream over a Xbee-Pro XSC radio back to the base station.  The payload will be mounted in the nose of the rocket, so room is going to be tight.  I am planning on making an adaptor board to connect the two modules together along with an extended battery pack.
     
    The sensor tag contains:
    IR temperature Sensor On chip temperature Sensor Humidity Sensor Pressure Sensor Accelerometer Gyroscope Magnetometer  This is information overload, but should allow the kids to have tons of room to experiment.  The extended range of the radio will also allow the payloads to be used in other experiments or possibly even in higher altitude rockets.  With a little hacking, the sensor tag should also be able to be modified to break out the i2c bus for adding additional sensors (e.g. GPS).
     
    The Base Station:
    To keep it simple and safe, we decided to forego traditional chemical motors and instead use a compressed air system that will consist of a small compressor attached to a pressure vessel.  Attached to the vessel will be an electric solenoid and a length of PVC pipe.  The rockets will be modified (by removing the engine mounts) to slide down over the PVC pipe, and will be fired by opening the solenoid valve. 
     
    The base station will have dedicated electronics to monitor and control the pump and solenoid, and we are considering a stepper driven belt drive to adjust the launch angle.  Even though it is a low pressure system and there will be interlocks and blow off valves in place, we want to operate it from a safe distance.  Currently we are planning on using a Phidget board controlled by labview to run everything on the base station.  The idea is that the students can adjust the launch angle and pressure, launch their rocket, and see in real time what those changes made to the launch characteristics.  The pressure based launcher also limits the range to several hundred feet, so we don't need to worry about recovery systems or losing rockets when it is windy...and it will be usable in large lecture halls.
     
     
    Communication:
    To communicate with the payloads, we will have a stellaris launchpad with another Xbee-Pro radio mounted on the base station that will act as a hub, aggregating data streams from all transmitting payloads and rebroadcasting them over serial to the main computer, which will handle logging and display.  Because the sensor tag unit in the payload is low power BT enabled, we plan on having a BT dongle on the base station to detect and identify the rocket loaded into the launcher.  This info will be read by the computer logging the data and used to automatically bring up that rocket's data stream.  The BT connection might also be used to wake up the radio out of sleep mode, so that the modules conserve power when not in use. 
     
     
    Right now the project is still in the planning stage.  Parts have been ordered and should be here on Monday except for the sensor tag boards, which are backordered for another 2 weeks.  Once the radios are here, we will start prototyping the network building the base station.  I will update with pictures and updates as the project progresses.
     
     
  20. Like
    cde got a reaction from mbeals in (MCU) Wireless networking question   
    Not personally, but the CC2541 SoC used on the chip is an 8051 compatible chip. (The CC2541 chip comes in a QFN-40 package and not only implements Bluetooth Low Energy, but has a internal  MCS 8051 micro-controller, general purpose timers, accurate RSSI support to allow range determination, two USARTs, 23 general purpose digital IO pins, 12-bit ADC with eight channels, I
  21. Like
    cde got a reaction from mbeals in (MCU) Wireless networking question   
    Nice. Why not the TI bluetooth sensor tag? You could reprogram it so you have all the sensors, and use it with a simple radio VHF module.
  22. Like
    cde got a reaction from swampdonkeykami in Hydraulic anti-jam control   
    Or if they rotate that transistor 180 degrees, you don't have to route around d2, and everything is neater.
  23. Like
    cde got a reaction from bluehash in radioshack clearance   
    Just a heads up, with the radioshack clearance event they are having, not only do they have some new electronics parts and kits (like smd tact switches, and phirrahna like leds) but some neat stuff has come down.
     
    Mainly, the official arduino brand ethernet shield for 19.99 (or cheaper) and the arduino brand motor shield for 9.99 (or cheaper). This might be ymmv, but someone might benefit from these for a one off project. (The boxes are white and yellow, official arduino brand, not the make or seeed or other brand ones)
  24. Like
    cde got a reaction from cubeberg in radioshack clearance   
    Just a heads up, with the radioshack clearance event they are having, not only do they have some new electronics parts and kits (like smd tact switches, and phirrahna like leds) but some neat stuff has come down.
     
    Mainly, the official arduino brand ethernet shield for 19.99 (or cheaper) and the arduino brand motor shield for 9.99 (or cheaper). This might be ymmv, but someone might benefit from these for a one off project. (The boxes are white and yellow, official arduino brand, not the make or seeed or other brand ones)
  25. Like
    cde got a reaction from GeekDoc in radioshack clearance   
    Just a heads up, with the radioshack clearance event they are having, not only do they have some new electronics parts and kits (like smd tact switches, and phirrahna like leds) but some neat stuff has come down.
     
    Mainly, the official arduino brand ethernet shield for 19.99 (or cheaper) and the arduino brand motor shield for 9.99 (or cheaper). This might be ymmv, but someone might benefit from these for a one off project. (The boxes are white and yellow, official arduino brand, not the make or seeed or other brand ones)
×
×
  • Create New...