Archive: 5 posts

---

Is there any way to hook up a counter and a tag sensor so that it counts the number of tags in range rather than just outputting an on/off signal when it finds a tag? The way that I'm doing this currently is to have one sensor per tag (I need to check in 8 directions, so one facing each direction) on a sequencer that checks them one at a time with a slight pause in between, so that it sends a pulse to a counter every time it encounters a tag. Each time the sequence is run, the counter counts between zero and eight, sends the signal to another sequencer set to positional which performs an action and then resets the whole thing. It works flawlessly, but it's messy, unwieldy, thermo-hungry and much, much slower than I'd like (If I run the sequencer too fast it seems to confuse the counter). What I'd like to do, ideally, is have a single sensor simply output the number of tags within range, if I could do that I could more than halve the number of objects needed to make this thing work... but I'm not sure if it's even possible. If not, I'm pretty sure that I can make it neater but it'll still be slower than I'd like... but I thought that someone here might be able to see something that I'm missing? Any ideas? P.S. I'm new here, go easy!

2011-02-01 13:54:00 Author: Unknown User

---

I don't think there is a way to do that. I'd say X copies of the same tag sensor, each with 1, 2, 3, 4, 5 etc tags required. Each sensor hooked to a Selector and the output states of that Selector determines what is shown or done based on which situation occurs.

2011-02-01 14:00:00 Author: Antikris Posts: 1340

---

That might be a more efficient way to do it... I'm guessing I would still need to run them in sequence so that the selector would only output the most recent (i.e. the highest) signal? Hmm, food for thought anyway. If it works it would probably be quicker and take up a bit less thermo. Thanks!

2011-02-01 14:22:00 Author: Unknown User

---

I'm guessing I would still need to run them in sequence so that the selector would only output the most recent (i.e. the highest) signal? You don't need to do that because selector haves a weighting from last to first

2011-02-01 14:31:00 Author: waD_Delma Posts: 282

---

I was just about to come and post that, I hadn't used selectors before so I had assumed that they just output the last signal that they received. Just been playing with this idea and it looks like it's going to do the trick! Thanks! Edit: Yup, that's done the trick. It only takes up about half as much thermo as it did before and I can adjust the speed of each tick, brilliant!

2011-02-01 15:33:00 Author: Unknown User

Posts: 1077139    Threads: 69970    Members: 9661    Archive-Date: 2019-01-19

Aus dem Archiv wurden alle persönlichen Daten wie Name, Anschrift, Email etc. - aber auch sämtliche Inhalte wie z.B. persönliche Nachrichten - entfernt.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.