Mantis Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000200TunixGeneral Featurespublic2011-07-13 00:262012-04-17 09:35
Reporterdandruczyk 
Assigned Todandruczyk 
PrioritylowSeverityminorReproducibilityN/A
StatusassignedResolutionreopened 
PlatformAllOSAllOS VersionAll
Product Version 
Target Version1.0.0Fixed in Version 
Summary0000200: Re-implement network mode to be ECU generic if possible
DescriptionNetwork 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.

TagsNo tags attached.
FirmwareVersionnanana
Attached Files

- Relationships

-  Notes
(0001441)
dandruczyk (viewer)
2012-04-15 19:41

Issue moved to new issue tracker at http://megatunix.com/tracker [^]
User avatar (0001477)
Fred (administrator)
2012-04-17 09:35

Requires link to replacement issue!


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker