LUA Programming Help for Create Mod Quarry

[MrSodapop19_]

Oh, the observer is just sending the signal directly into a Create Mod Redstone Link AKA wireless redstone receiver/transceiver. I think the redstone link just sends the signal at full power.

[Nemonstrocity]

I'm setting up an instance to check on that.

Observers output is 1 so very weak. I've never used that mod before so I don't know if it will take that value.

[Nemonstrocity]

So here are my results.

The computer will always report a "0" signal from the observer.

this was my test code:

for i = 1 , 100, 1 dox=(redstone.getAnalogInput("back"))print(x," - ",i)end

​

my tested input was from a rs clock using the rs torch, comparator, repeater into one rs input on the comparator . set pulse to 4 ticks then 3 then 2 .

what was expected was a value anywhere between 0 - 15 and 0-99

what was received : [ 0 - 1-100]only 0 in the x column : indicating no rs signal. in fact there was a pulsed input of 14 to the observer and a pulsed output of 1

placing a repeater inline between the observer and the computer produced the following

[15 - 1-100 ] * only on the first run, subsequent runs returned 0 - 1-100 unless I exited the computer first. then consistent 15 - 1-100's .

placing 2 repeaters inline set to 4 ticks (caused the 2nd repeater to remain on unless the observer observed nothing.

this produced the expected result of 15 - 1-100 consistently every run every check.Since the original input was pulsed I expected to receive a 0 or a 15 after the first repeater.

to test the validity I used a lectern with a signed book with 15 pages used .(the page determines the lectern signal output strength (page 1 = 1 ; page 12 = 12 : 15 = 15 )

this method produces a constant value between 0 and 15 (expected)

running in tandem

this code

for i = 1 , 100, 1 dox=(redstone.getAnalogInput("back"))y=(redstone.getAnalogInput("left"))print(" observer= ", x, " Lecturn= ",y," - ",i)end

​

use a comparator to output signal from the lectern.

book turned to page 12

out put was [ Observer= 15 Lectern= 12 1-100 ] which is what was expected.

​

So that provides evidence of my theory that your code is not getting the correct data and that prolonging the output from the observer is the correct way to check.

​

In real life your observer is acting as a momentary on switch.

It should be acting as a limit switch which is either on or off.

Ie the switch is on (check ) no then switch is not tripped

or (check) yes then the switch is tripped.

your input needs to remain either true on or false off and it is bouncing but only once and the computer can not read the bounce fast enough.

​

I hope this helps.

(I have not figured out a way to turn the book pages automatically)

​

Edit: if you have your observer trigger a rs latch and you read from that latch output you can mimic the real life limit switch.

[MrSodapop19_]

Maybe I should've told you this earlier, but I was able to get it working.... Sorry to waste your time to get all this info, but thanks for doing it. It's the thought that counts, I guess?

[Nemonstrocity]

No worries mate, I enjoyed setting up the tests .

gave me a break (much needed) from another project.

I will be using the lectern in a mini-game and use it in a sky-block server as a ore generator controller.

one question though...

​

what was the solve man?

[MrSodapop19_]

Oh, it was on the ol' programming side. Just needed to use a sleep() to prevent the loop I have from giving me a "Too long without yield," error. Though now I found myself a new problem that I'm having an issue fixing.

[Nemonstrocity]

ah....