Skip to main content

duty cycle testing



Now that I saw a physical response, I should try to make it similar to how a servo should be controlled.

Servos are actuators that receive (expect) position input (as opposed to motors, which receive speed/intensity input). Simply put, it registers input as pulses, decoding the ratio of high (a "on" signal) to low in a given period as a position value. 

As I am waiting for my servo to be shipped, I will continue to work with the LED light. 

As opposed to my previous setup of having the light turn on every time the request is given, I will have the light turn on and off in a regular pattern until a request is given, upon which the pattern will change for one "cycle" (on-and-off pair).

The on-and-off logic (previously the LED control logic) will be run in a separate thread:

def dCycle(*args):
   global dCVal
   var = 1
   while var==1:
     dutyCycle = dCVal
     GPIO.output(17, GPIO.HIGH)
     time.sleep(dutyCycle)
     GPIO.output(17, GPIO.LOW)
     time.sleep(2-dutyCycle)

This code says that the total "cycle" will be 2 seconds, with "dutyCycle" being the length of time that the LED will be on. The global value "dCVal" will contain the length of time the light will be on. 

In the beginning, "dCVal" will be set to 0.15 seconds:

if __name__ == "__main__":
   global dCVal
   dCVal = 0.15
.
.
.
  thread.start_new_thread(dCycle,())

Every time the request is received, the value of dCVal will be changed to give it a different cycle pattern:

(in request received logic)
     dCVal = 1
     time.sleep(2)
     dCVal = 0.15

The LED will be on for a solid second when requests are received then return back to the short length once that is achieved. 

The time.sleep value of 2 somewhat resembled a setup/hold time in digital logic (reminded me of it, at least)... but not really at the same time. 
Labels:

Comments

Post a Comment

Popular posts from this blog

finally getting back to it

Things went by pretty quickly this month, and I was not able to play around with this project much.  I did tinker with it every now and then, but I was never able to get myself past the residing issue of compiling the RF library in the Raspberry Pi. It seemed people are generally interested in the project linked in the previous post, as people were actively posting comments on it.  Couple of days ago a user posted a solution to the compile issues (changes to method names and usage of pre-defined values for parameters), and I thought I should try following it to see if it works.  The code indeed compiled, and I was able to change it a little more to be more fitting to my project.  On the Arduino side, it might be a premature assumption, but it seemed like the Arduino was unable to handle messaging through the RF and controlling the servo at the same time. My assumption is that the inability to control them in separate threads is causing some timing issues, but I mig
Post a Comment
Read more

finally got around to it (nrf24l0+ and servo)

On a previous post , I used the nrf24l01+ wireless chip to communicate between the Raspberry Pi and an Arduino, but only got lights to turn on. I remember being confused as to why servos would not work, and somewhat left it there. I started messing around with it again, and I am concluding that it might have been just a power issue. Here is the servo moving properly: The Arduino is on the ground due to the short length of the wires powering them. Just as a recap, what is happening is: - a C++ program using the RF24 library is compiled in the Raspberry Pi (connected to an nrf24l01+ chip) to broadcast a message. When executed, it will broadcast the message. - the Arduino (connected to another nrf24l01+ chip) programmed to receive messages receives the message, and upon receipt sends a signal to an Arduino that is wired to the servo to move the servo. Two separate Arduinos are used, as it seems that the servo library and the RF24 library do not seem to run properly toget
Post a Comment
Read more

GPIO testing

Since the environment of the client-server-target is currently quite functional in the messaging standpoint, I decided to try connecting a simple LED light to the Raspberry Pi to see if it could "open" a door when the command is received. Installed the RPi.GPIO module (a Python module that gives the user command of the GPIO--General-Purpose Input/Output--ports in the Raspberry Pi) and connected the LED light to a GPIO pin. When the target received a request message, it would signal the GPIO pin to drive a current to the LED to light it up for 2 seconds. in main: if __name__ == "__main__":   GPIO.setmode(GPIO.BCM)   GPIO.setup(17, GPIO.OUT) in the on_message's request-received logic:      GPIO.output(17, True)      time.sleep(2)      GPIO.output(17, False) The video is a weak visual result. You can a click when the LED lights up; that was the sound of the key being pressed that sent the request message. Now, time to get (think up of ) some a
Post a Comment
Read more