Connecting to GenBoard via a 20000 km serial cable - internet
Developers connect to other developer's boxes from time to time. Eg. from Canada to a board running in Hungary 8 timezones away.
Note that for making a base-tuning (eg. for starting an engine for the first time) one does not need such access to the board, because one can just send the config and tables files as on GenBoard/InitialConfig.
There was a GenBoard available on network for some time, to test some comm without real HW.
Anyone who cares can easily plug in a spare VEMS for testing, so turned off (discontinued): telnet cell.dyndns.ws 32001 (or 32000)
and say mcd (or Manmcd if m spits binary data
- although leave-TF command (B1 + [modbus CRC] = B1 7F 34) necessary to leave TF-mode (for quite some time, only CRC-protected commands are interpreted by default, so the chance of accidental noise causing config change is minimal).
- or maybe left menu to compatibility binary 1-letter command more by typing bye. Valid commands are on GenBoard/MenuSystem
TODO:
- export global.h somewhere (though running recent cvs most of the time)
- use some kind of authentication (and maybe stunnel or TLS?)
- do we want RAW protocol or telnet
- patch the tuning-softwares for TCP/IP access ( already done for OtherTuningSoftware/PSITuner )
- document easy way to try tuning-software connected to real AVR (via network)
You are encouraged to hook your GenBoard v2 or v3 to network (remove dangerous parts that can heat intensively: WBO2, sparking equipment, fuel lines :-). Easiest way is to connect to the serial port of a linux box and apt-get install ser2net package. Ser2net also available on platforms other than [Debian GNU Linux].
See also:
- RadioBoard for wireless discussion
- VemsFrontier/Bluetooth Collecting information for BT communication
- CommMatrix for communication protocol interoperability