Posted 17 January 2013 - 05:57 PM
hello again,
i have a lift program that has the up and down functions defined in it.:
——————————————————————
DOWN:
local function down()
m = peripheral.wrap(sSide)
m.setFreq(downFreq)
rs.setOutput(sSide, true)
sleep(3)
rs.setOutput(sSide, false)
sleep(3)
UP:
local function up()
m = peripheral.wrap(sSide)
m.setFreq(upFreq)
rs.setOutput(sSide, true)
sleep(3)
rs.setOutput(sSide, false)
sleep(3)
end
——————————————————–
variables: sSide = "left"
upFreq = 2
downFreq = 3
——————————————————-
If I run down() on its own it seems to ignore the sleep(3) and just spams the Output until it hits the ground, it is the same with the up() (but it goes up)
BTW/FYI: the computer is on redpower frames if that makes a difference
i honestly have no idea how to fix this and i need some help.
thanks
kingcoon
i have a lift program that has the up and down functions defined in it.:
——————————————————————
DOWN:
local function down()
m = peripheral.wrap(sSide)
m.setFreq(downFreq)
rs.setOutput(sSide, true)
sleep(3)
rs.setOutput(sSide, false)
sleep(3)
UP:
local function up()
m = peripheral.wrap(sSide)
m.setFreq(upFreq)
rs.setOutput(sSide, true)
sleep(3)
rs.setOutput(sSide, false)
sleep(3)
end
——————————————————–
variables: sSide = "left"
upFreq = 2
downFreq = 3
——————————————————-
If I run down() on its own it seems to ignore the sleep(3) and just spams the Output until it hits the ground, it is the same with the up() (but it goes up)
BTW/FYI: the computer is on redpower frames if that makes a difference
i honestly have no idea how to fix this and i need some help.
thanks
kingcoon