Jump to content




== WiRe == (Redstone Master Control for your base)

lua wireless utility

  • You cannot reply to this topic
117 replies to this topic

#41 oden the fish

  • Members
  • 24 posts
  • Locationmars

Posted 11 July 2014 - 01:04 AM

huh ill make it where it downloads them to your computer but it says open and closed like it would before. every thing looks the same as before but it wont disable the redstone signal from the right side but it happend right after my game crashed (due to some glitch with jabba) and im not sure whats wrong im going to try a redstone wire and some lamps
heres my hopefully fixed dropbox link https://dl.dropbox.c...iGZBvnivda?dl=1

Edited by oden the fish, 11 July 2014 - 05:49 AM.


#42 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 11 July 2014 - 06:52 AM

The new pic is 404, but that's OK - I *think* I have a general idea of what's happening. I've seen similar behavior after a crash. If the terminal screen is correctly indicating the door state, then WiRe is most likely working as expected.

Have you tried breaking and placing the computer again? You might need to break the computer, restart the game, then re-place the computer.

If that doesn't work, I can think of two other things to try:

1. Delete /data/WiReClientCfg, re-download the client and go through first time setup on that client again. This probably won't fix it, but if the problem is with WiRe (and it was working fine before), a corrupted program or config might cause WiRe to behave strangely.

2. Temporarily move the computer to another location and see if it works there. If the problem follows the computer then try replacing the computer with another one and see if the problem goes away.

Let me know how it goes and we'll proceed from there.

#43 oden the fish

  • Members
  • 24 posts
  • Locationmars

Posted 11 July 2014 - 11:27 AM

its like rednet is broken WiRe is working fine but if it uses the red net then it wont work sorry for blaming your program it works fine with normal redstone
EDIT: well its minecraft's pistons that were the problem braking a replacing them worked again sorry

Edited by oden the fish, 11 July 2014 - 11:31 AM.


#44 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 11 July 2014 - 04:31 PM

No need to apologize, WiRe was a reasonable suspect in what was going on. I'm just glad you found and were able to fix the problem. If you have any questions or problems in the future, please don't hesitate to post - I'm happy to help :)

#45 DrikarArz

  • New Members
  • 1 posts

Posted 12 September 2014 - 11:56 PM

Fantastic program, but when I was trying to get WiRe to work on my new world. It has worked on previous worlds absolutely wonderfully. Now when I startup the WiRe server for the first time when I get to the part to select the color to manage I get the error: "startup:720: bad argument: table expected, got nil" The client computers work fine. I've tried with both wired and wireless modems, basic and advanced computers, and controlled for everything else I could think of.

I'm running ComputerCraft 1.63, OpenPeripheralCore-0.3.3, and OpenPeripheralAddons-0.1.3 (I did attempt the program with the open peripheral mods disabled)

Unfortunately I dont know enough coding to really troubleshoot it any further... so any help would be appreciated.

Thanks

#46 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 13 September 2014 - 12:30 AM

DrikarArz - thanks for the compliment - I'm glad you've found WiRe useful :D

My apologies for the troubles you're having. What you're seeing is due to an error on my part when I recently did some optimizations to the code - I've fixed the problem and updated the download. Re-download the server and it should work fine for you. If you have any other problems or questions, please let me know :)

Edited by Dog, 13 September 2014 - 12:33 AM.


#47 KevinsCode

  • New Members
  • 2 posts

Posted 15 September 2014 - 05:38 PM

View PostDog, on 15 June 2014 - 07:47 PM, said:

Getting cc10 and WiRe to talk to each other would be a monumental task - they provide similar functions, but operate very differently.

I am looking into adding pocket computer support for WiRe, but I can't promise it'll happen. It isn't just a matter of adding some code to support pocket computers. A lot of the code of WiRe server (or WiRe client, depending on which way I go) will have to be re-written to accommodate having multiple 'control centers' (in addition to a number of other changes that would have to be made). It also negates the 'single, master control center' philosophy that WiRe was designed around. I, too, like the idea of the convenience, so I'm looking in to it and trying some things out; but I'll only be adding it if I can integrate it in a way that makes me happy and matches the overall design concept of WiRe.

EDIT: After some testing, I've discovered that cc10 and WiRe work together very well, but with limited functionality.

Simply install cc10 Host (named 'cc10host') and WiRe Client (named 'WiReClient') on the same machine and create the following file named 'startup'
shell.run("cc10host WiReClient")

Configure both cc10 and WiRe to use the same side for redstone output and it should 'just work'. cc10 and WiRe will both report status correctly...but, cc10 is not aware of WiRe's 'lock' ability and essentially bypasses it. If you'd like a small layer of protection, configure cc10 to use a password - note that passwords and communications are not encrypted.

When you reboot the machine, this will launch cc10host in daemon mode, which will then automatically launch WiReClient.

i cant seem to get this working, it opens as a receiver for the redstone not a controller, unless this is how its supposed to be

#48 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 15 September 2014 - 06:21 PM

I'm not sure what you mean, KevinsCode. What, exactly, opens as a receiver and not a controller? Which program is not working as expected - cc10 or WiRe?

#49 ChocoPuppy

  • Members
  • 3 posts

Posted 04 March 2015 - 10:24 AM

View PostDog, on 15 September 2014 - 06:21 PM, said:

I'm not sure what you mean, KevinsCode. What, exactly, opens as a receiver and not a controller? Which program is not working as expected - cc10 or WiRe?
I think he made the same mistake I did, he thought that you use the instructions for the pda by downloading the things on the pda, you didn't specify (always a good thing to specify even if it seems painfully obvious)

also the reason why I came on here: can you make it so clients and servers can be in two networks? I want to make something like multiple terminals controlling multiple networks but then one master one that controls all doors

#50 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 04 March 2015 - 04:42 PM

Heya ChocoPuppy,

Thanks for the clarification - I'll see what I can do about making the OP more clear and easier to understand.

Right now you can do multiple 'networks' - they are defined by the color you choose during setup. All matching colors are on the same network. I'll see what I can do about clearing that up in the OP as well.

As for a master control station that controls ALL networked clients regardless of color - I'll have to see if that's something I can work into the program.

#51 BreeOge

  • Members
  • 20 posts

Posted 05 March 2015 - 06:20 AM

I have a suggestion, anyway we can have it so that upon a reboot it goes to last state, instead of just On/Off Open/Close ect.. Last state would be great, that way if the minecraft server crashes, when it comes back up, everything will be like it was.. instead of having to log on and re set all switches..

Thanks

#52 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 05 March 2015 - 06:55 PM

That's a good idea, BreeOge - thanks for the suggestion. I'll see what I can do about that :)

EDIT: I've added the feature, but you'll need to run your clients through first time setup again to take advantage of it. To re-do first time setup on each client, delete "/data/WiReClientCfg" then restart the client program. The option can be selected when choosing default startup (select [p] Previous state).

Edited by Dog, 05 March 2015 - 08:08 PM.


#53 BreeOge

  • Members
  • 20 posts

Posted 05 March 2015 - 07:48 PM

Thanks, maybe you could make it write another file, and in that file put the current state.. then if you select last state as startup.. it would look at the file and pull the last state.. I know a little programming but not a lot... Thanks for trying to work it in.. great program..

#54 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 05 March 2015 - 08:39 PM

Thanks for the compliment - those are always welcome :) I'm glad you like the program.

The feature is in and I made a pre-emptive change to locking as well. I've removed default lock and default unlock states - now when you lock a device it will remain in whatever state (on/off/open/closed) it was in before it was locked. That way you can choose to lock a door open or closed as opposed to being stuck with whatever default lock state you chose during setup.

EDIT: Found and fixed a small bug - redownload if you downloaded it before the edit time of this post.

Edited by Dog, 05 March 2015 - 09:21 PM.


#55 BreeOge

  • Members
  • 20 posts

Posted 05 March 2015 - 11:24 PM

I am getting "Looking for WiRe Server . . .Startup:1012:Expected String, Boolean"

Deleted Config, and ran new install.. both server and clients..

#56 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 05 March 2015 - 11:35 PM

Ugg...I found and fixed that error *after* you downloaded the client :/ Unfortunately that means you have invalid data in your config file (because of an error of mine). Apologies for the problems. Redownload the client, delete "/data/WiReClientCfg", and go through setup one more time. Let me know if that works for you.

#57 BreeOge

  • Members
  • 20 posts

Posted 05 March 2015 - 11:45 PM

Will do.. ahh no big deal, i am just happy you put last state in lol..

Same thing, now it says line 967 same error..

#58 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 05 March 2015 - 11:54 PM

Did you delete the file "/data/WiReClientCfg" ? That's the line I'd expect that error if you still had a config with invalid data, but I can't recreate the problem on my end with a fresh install.

What options are you selecting during setup? That'll help me nail it down.

EDIT: OK - I was able to duplicate the problem - working on it now - should have a fix up shortly.

EDIT2: OK - finally fixed - redownload the client and run it, it *should* work fine now. Again, my apologies for that - glad you like the new feature :)

Edited by Dog, 06 March 2015 - 12:13 AM.


#59 BreeOge

  • Members
  • 20 posts

Posted 05 March 2015 - 11:56 PM

Yea, I deleted it.. its for a door, options are D, N, P, Yellow, top, No GPS

#60 Dog

  • Members
  • 1,179 posts
  • LocationEarth orbit

Posted 06 March 2015 - 12:16 AM

It's fixed :) Redownload the client and that problem shouldn't bother you any further. Thanks for your patience!





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users