|Anonymous | Login | Signup for a new account||2019-06-17 20:48 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000200||Tunix||General Features||public||2011-07-13 00:26||2012-04-17 09:35|
|Target Version||1.0.0||Fixed in Version|
|Summary||0000200: Re-implement network mode to be ECU generic if possible|
|Description||Network mode is currently MegaSquirt specific as MtX implements a subset of the MegaSquirt API as a state machine over TCP/IP. This is great when working with a MS, but isn't flexible to work properly with non-MS devices. |
The design needs to be re-thought to be either:
1. generic so it works with all potential ECU's (tricky as I have no idea of the esoteric types of other ECU's that mtx may eventualy talk to), and distilling to a common interface is likely to be extremely difficult.
2. Per ECU socket implementations, basically. mtx would need to emulate the functionality of the target device. the advantage of this is that it would potentilaly alow piggybacking of OTHER software through megatunix using something liek a serial->TCP bridge device/software. Mtx currrently has this in theory for the megasquirt device family. It should in theory be possible to pipe megatune/tunerstudio through a TCP port to mtx and it should actually work, though it won't receive the updates from the master instance as that uses a separate TCP port for message passing, and is MTX specific.
|Tags||No tags attached.|
|Issue moved to new issue tracker at http://megatunix.com/tracker [^]|
|Requires link to replacement issue!|
|Copyright © 2000 - 2011 MantisBT Group|