Страница в магазина
Space Engineers
Всички Дискусии Снимки Худ. творби Предавания Видеа Работилница Новини Ръководства Рецензии
Space Engineers >  Работилница > Работилницата на Wicorel
Няма достатъчно оценки
Wico Techniker Custom
Описание Дискусии0 Коментари24 Бележки за промените
   
Награда
Добавяне към любими
В любими
Премахване от любими
Type: IngameScript
Размер на файла
Публикуван на
Обновен на
102.542 KB
20 ноем. 2016 в 0:12
16 февр. 2019 в 17:15
34 бележки за промени ( преглед )
Създадено от
Wicorel
На линия
Вижте всички 19 колекции (някои може да са скрити)
823 уникални посетители
246 текущи абонати
22 настоящи в любими

Абониране, за да се свали
Wico Techniker Custom

Описание
Custom Craft Control.

  • front scanning using camera raycast new in 1.63 DEV
  • uses any number of front-facing cameras for scanning. No naming needed.
  • keeps track of detected entities and reports on GPS text panel.
  • Proximity warning and Emergency stop procedure.
  • reports tool arm position for named rotors (Techniker)
  • 'coast' mode that turns off front-facing thrusters. allows motion to continue like turning off damperners, but keeps steering control from turning.


Naming


Cockpit/Remote Control

A cockpit or remote control is needed to determine the 'direction' of the ship.

The code first looks for a remote control named "Remote Control Techniker"
It then searches for any remote control with "[NAV]" in the name. It will then search for ANY remote control.
And finally it will search for any cockpit

Note: "Front" is determined by the orientation of the cockpit/remote control.

GPS Output LCD
The first text/LCD panel with "[GPS]" in the name is used to output the GPS coordinates.

Cameras

All front-facing cameras are used for scanning unless they have the text "[VIEW]" in the name

E Stop

There are no naming requirements for emergency stop. The front and rear thrusters are automatically determined.

Reporting

The reporting is placed on a text/LCD panel named "LCD Bridge R". If that block is not found, it will use the first block with "Craft Report" in the name.

Name can be changed in the Programing Block's CustomData.

Range Report

The range is placed on a text/LCD panel with "[RANGE]" in the name or CustomData.
Multiple LCDs are supported. Suggest setting text font to Monospace

Name can be changed in the Programing Block's CustomData.

Timer
No Longer needed

The PB needs to be run by a timer. It does not need to be run more than once per second. It should run the main PB with the argument "timer"

FAST Timer
Optionally, a timer can be made to allow the code to be run quickly when needed. For this code, that is only when initializing on each load. This timer must have "[WCCT]" in the name. It should run the main PB with the argument "wcct".

sub-modules
This code is based on my Craft Control scripts and it also supports sub-modules.
See the documentation for Craft Control for specifics.

If you are not using sub-modules, turn off submodule support in CustomData to save performatnce

Name of craft
ADDED 2.0L The script will first check CustomData of the PB for shipname=XXX and use the XXX as the name of the ship.

Otherwise, the name of the craft is determined from the antenna name. Antennas with 'unused' in the name are skipped (Techniker has two antennas).

This name is used in the displays.

Added 2.0L: Setting ship name and long and short range scan values in CustomData.
Example CustomData:
ShipName=Rhino Freighter
ShortRangeMax=1000
LongRangeMax=100000000

V3.2A Added more settings to CustomData. only need lines for items that should be changed from the default

Example:
[TECHKNIKER]
DoForwardScans=true
CheckGasGens=false
TechnikerCalcs=true
GPSFromEntities=true
AirVents=false

shipname=Bob's Big Boat
shortrangemax=1500
longrangemax=15000




24 коментара
< >
Krougal 5 ян. 2018 в 15:18 
Arghhhh....so I hate to be a PITA, but it's also turning on O2 gens (I didn't notice until I installed on series 4 small craft).
Krougal 4 ян. 2018 в 19:52 
Ok, that took care of my antenna problem as well as the batteries. Thanks!
Krougal 4 ян. 2018 в 19:35 
Can hop in my lab if you want to see it in operation?
Still acting a little wierd at times too. It does still need the 1s timer block right? I've also got the WCCT timer and the stored data panel (not really sure I need that for my application?)
Wicorel  [автор] 4 ян. 2018 в 19:31 
I will have a new version in a few minutes to remove the battery thing.

I don't understand where it could be setting antennas back on in this version... But the code IS complex and I may have missed something.
Krougal 4 ян. 2018 в 19:00 
I am indeed using 3.1A
Maybe KSH reintroduced the bug?
Wicorel  [автор] 4 ян. 2018 в 18:56 
Which version are you using?

The current is 3.1A which should no longer have the antenna forcing on (there was a bug in older verisons of SE where the antenna would turn off if you tried to remote control a grid).
Krougal 4 ян. 2018 в 10:40 
My spare antenna keeps turning on also, tried naming it unused & blank (the actual Techniker it's blank...but it's still running version 2.0) going to blame this on you too ;)
Does the stock craft control have the feaures I need?
Krougal 3 ян. 2018 в 22:05 
Yeah, would love that. I'd do it myself, but I couldn't make heads or tails of your code lol. I really don't like anyone messing with my batteries; I either have ships that run entirely off batts or they are just for surge and toggled by keybind.
Wicorel  [автор] 3 ян. 2018 в 21:43 
Looking at the code, it should only be turning a battery's RECHARGE to off when it gets to > 99% charged..

I don't have the NOPOWER option in Techniker, but I could add it if you want it to leave batteries alone.
Krougal 3 ян. 2018 в 20:05 
NM about the timer, somehow the timer lost itself (timer start action had become invalid???) fixed that. The battery thing is still an issue.