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

Search the Community

Showing results for tags 'modem'.

  • 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 10 results

  1. I'm writing a simple threaded network messaging script to manage some drones, but the problem I'm having is that once I've spun off a thread to handle a drone it hangs on sending a message. It sends the message and the drone gets it intact, but the modem.send call doesn't return after sending it. Attached is the full code for the drone manager. It hangs on line 23, just before the "Thread sent command to drone" print statement. Any ideas on how to resolve this one? dronecontroller.lua
  2. Hey there, I have a question. I wanted to program something like wireshark for OpenOS, so that i can monitor my network traffic. Is there a way to modify the modem code to collect all data. I want to read all the messages that are send with an address, so not only the broadcasted ones's. I think there could be an way. LuckyCrasher
  3. i have made some code to play around with the modem stuff but for some reason the modem_message event always returns 0 also im am running one of the scripts on a microcontroller and i am running minecraft version 1.7.10 code of the microcontroller: local rs = component.proxy(component.list("redstone")()) local modem = component.proxy(component.list(modem)()) local identity = 1 a ={} d = "id:" f = tostring(identity) a[1] = d a[2] = f modem.broadcast(1234, "id:1 is online") while true do computer.pullSignal(0.5) end
  4. I have developed a sort of DNS server/client system. This is the fifth iteration of this system and finally, one which works and I'm happy with. Here is the link: https://github.com/SpaceBeeGaming/OC-DNS I know there was another "DNS" posted recently but it has not influenced mine (sounds selfish, I know; but true).
  5. 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 ha
  6. Hello In the documentation modem.send() uses an address:string that identifies the receiver's destination. But modem's addresses are lonnng numbers. I've tried sending messages with just the first characters of the address, but that doesn't seem to work. It's impractical to use the long default address created for the modem. Is there a way to set this address to something smaller and more practical? Or do I really have to work with the looong default address?
  7. ComputerCraft does not seem to recognise the OC Relay as any form of peripheral, and so is unable to wrap to it or interface in any way. Context: I'm using ComputerCraft Turtles to swarm mine, and send information/receive commands from a ComputerCraft computer. I placed the CC computer adjacent to the OC Relay and hoped to be able to send messages between them. I wanted to create a user interface to control the turtles on the OC screens because they have a higher resolution and I just prefer OC interface. Any help would be greatly appreciated! Currently running CC[1.80pr0], C
  8. The request-handler is a program to run as a main program on a PC. It holds execution commands from every program that communicates with it. That means I can run multiple programs that run their commands through the request-handler by adding their command and parameters to the request-handler. It also servers as a server for other computers that can send their requests to the server and if that request is allowed it will be processed automatically and the answer is send back. For this I programmed the modem-API that ensures that message networks are received on the target and works together wi
  9. Hey, hope you're having a wonderful day. Gangsir again, back with another one of my small but useful programs. I've written a small user-friendly program to manage modem ports. It has the ability to scan and list all open ports, then gives you the option of opening and closing some ports. A few arguments and switches can be specified, these control what the program does. Syntax: ports [-ns] <minSearch> <maxSearch> -n : No scan, skips scanning and goes right to opening and closing. -s : Silent mode, only scans, no questions asked. <minSearch> : The lower port to search from
  10. Before implimenting higher-level protocols, you'll want a lower-level way to make your messages appear as a stream, just like TCP sockets, right? That's where this comes in. ocsocket makes modems behave like TCP sockets. Functions: ocsocket.socket(port,address) That will return a socket object. Socket object functions: obj.init() Must be called to make a socket work. octcp.isData() Returns true if there is data to be read, false otherwise. obj.read(i) i is a number or character, if it's a number, it will read that many characters. If it's a string, it will read until that character
×
×
  • Create New...

Important Information

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