Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

Search the Community

Showing results for tags 'modem_message'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • OpenComputers
    • Announcements
    • Feedback
    • IRC
  • Code Central
    • Support
    • Showcase
    • Tutorials
  • Addons & More
    • Addons Mods
    • Architectures
    • OpenEngineering Task Force
  • General
    • Lounge
    • Forum Games
    • Showcase
    • Servers
  • Archives
    • Public Archives

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Minecraft


GitHub


IRC


Fediverse ID


Location


Interests

Found 3 results

  1. Hello, I need help with seperating modem signals from multiple slave computers on the master computer. I'll attach an image of my current code. Currently it isn't consistent and I want to add more slaves to the system. Also I know in the image in the code, the syntax of the modem information isn't consistent (the c012, a32a, etc). Hopefully the code and the very brief description illustrates what my problem is and I know I've posted something similar before on my profile but still need help. Many Thanks
  2. Problem with receiving multiple signals Hello, I am using nuclearcraft and I want to create a program that visualises the reactor information, this information would include RF stored, efficiency, etc. However, I am using 5 reactors and want all 5 to be shown on one screen, through one computer. I have set up a wired network in which each reactor has it's own computer pulling the reactor information and sending it down the line, through a central relay and to a central computer. My problem is that you have to use event.pull("modem_message") and because of this, you can't differentiate between different inputs. The closest I got was using multiple ports and using if and elseif statements to print depending on the address of the network card that sent the message. This meant that they would takes turns printing their values but not simultaneously. To note: -Using threads or sides is something I thought of -Using a script or, the aforementioned, threads and then calling to them in a main program -I tried using if table.insert() and then printing the table, though this didn't work, the way I did it. Can somebody help me understand a method in which I can differentiate between inputs coming into to one computer. Thanks in advance :)
  3. So i'm working on a rudimentary network system to transmit simple packets of information between computers, ya know a basic network. I've run into the issue however, that its quite simply not working how i'm expecting it too. I've had no problem with OC in the past making several useful tools, but apparently i can't crack wireless networks So here's the current testing environment: Two computers about 5 blocks apart. one is in the lua shell with a simple =event.pull("modem_message") Port 52 is open The other is broadcasting "test" on 52 nothing is happening on the first computer! I'm getting no errors either. and when doing =modem.broadcast(52,"test") it returns true stating that the message was successfully sent. It's just not being recieved for some reason. What could be causing this!!?! D: EDIT: for reference i'm in 1.10.2 and i'm using two addons: Computronics and OCRSDrivers (for refined storage monitoring) both of these are natively supported in 1.11 but not in 1.10 so i have to use the external mods. would they possibly be interfereing? EDIT2: somewhat solved i guess. restarted my client and things seemed to be working all of a sudden. Also mistakenly put event.listen in the title instead of event.pull. my bad!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.