Store Page
Space Engineers
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Space Engineers

Store Page
Space Engineers >  Workshop > cjb's Workshop
Not enough ratings
Simpler Transmit Receive
Description Discussions0 Comments13 Change Notes
   
Award
Favorite
Favorited
Unfavorite
Type: IngameScript
File Size
Posted
1.879 KB
20 Jun, 2018 @ 5:08am
1 Change Note ( view )
Created by
cjb
Offline
See all 44 collections (some may be hidden)
1,710 Unique Visitors
321 Current Subscribers
23 Current Favorites

Subscribe to download
Simpler Transmit Receive

Description
This version is deprecated because Space Engineers 1.189 made communication much better.

Use Simpler Transmit Receive 2 instead!


**** Only kept for educational purposes ****

All credit to etopsirhc's Transmitter and Receiver script for inspiration and my starting point
Transmitter and Receiver

I really liked etopsirhc's script but I'm lazy and didn't want to configure settings. :)
This script takes his idea and makes it simpler to use.

The enhancements are:
- Automatically selects the best antenna
- The same programmable block can transmit and receive
- No script configuration required


To receive messages:
- Create a programmable block with this script
- Create timer blocks to perform actions that you want to remotely activate
- Create an active antenna
- Assign this programmable block to the the antenna

To send messages:
- Create a programmable block with this script
- Create an active antenna (make sure broadcast is enabled)
- Call this programmable block with the name of a timer block on the _REMOTE_ grid


Note on Multiple Receiving Antennas:
On the receiving craft, you should generally not set multiple active antennas to receive messages for the same programmable block. Each antenna will receive the message and send it to the PB, which will create duplicate runs.

SE Bug Note:
There seems to be a SE bug right now (June 2018) where multiple active antennas always use the longest active range, no matter which antenna you use to transmit.
13 Comments
< >
Raggety 14 Jun, 2019 @ 10:52pm 
@cjb Thanks for having a look. Will check it out.
cjb  [author] 17 Mar, 2019 @ 8:04am 
@Raggety I've rewritten this for SE 1.189+ because of the new communication systems https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1685786559

I'm not sure whether you will need to tweak anything to use it other than to update the PBs on the grids.
cjb  [author] 14 Mar, 2019 @ 5:15am 
Hi @Raggety - I haven't had a look at SE since the release yet, but the release notes say that some sort of communication between grids is builtin now so this script is probably mostly obsolete, but I'll take a look. Probably still be a couple days before I can though.
Raggety 7 Mar, 2019 @ 11:43am 
The code now says |MyRadioAntenna.TransmitMessage(string.MyTransmitTarget) is obsolete. I have no idea how to fix this myself. Is there any chance of an update?
cjb  [author] 2 Jul, 2018 @ 2:14pm 
@Aramil have you already looked at https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=915118478

It looks like it might have a bug related to ships that dock, but it seems like exactly what you're looking for.
Aramil 💢 2 Jul, 2018 @ 2:11pm 
@cjb thanks, I was looking for a script for something like that, couldnt find it to work on two different grids.
cjb  [author] 2 Jul, 2018 @ 1:54pm 
@Aramil that's not the use-case this is set up for; it's to send/receive actions rather than blocks of text.

Remotely duplicating the text of an LCD is interesting though; if no one else has already done it then maybe I'll poke at it and see if there's a robust way to do it that's simple to use.
Aramil 💢 2 Jul, 2018 @ 9:13am 
How would I use this to get lcd inventory information from my other base to my main base? Using MMaster automatic LCDs.
Frayboy15 22 Jun, 2018 @ 3:16pm 
That's an even better idea! I didn't think of that.
cjb  [author] 22 Jun, 2018 @ 2:03pm 
I think if you're comfortable with adding case statements and really want shortcuts, then you're probably already comfortable enough with just adding that switch statement in the existing PB code.

I don't think adding code that would be 99% unused (especially given the intention of the script as a whole) is something I want to build in, since it's opposite the intention of the script.

That said, if I did add some sort of mechanism for alternate names, I would do it via the Custom Data. I'm considering moving the existing _minor_ options into the Custom Data already, because generally speaking I want configuration to be a separate from the script. That way if/when I update the script, no one has to go back and remember all the custom things they changed (which is one reason I end up running old versions of scripts for ages).

I appreciate the feedback though, it's something I'll keep in mind as a potential change if I do move the options into Custom Data.