[Coco] Drive Wire 4.3.4E - Multi Instance How ?

[Aaron Wolfe]

Autostart just makes the instance start when you open Drivewire instead of
waiting for you to manually do it.  You probably want that on for all of
them.

The tcp client and server ports only matter if you're actually using those
modes in that instance, otherwise they are ignored.  I think you're using
serial ports so not a factor.

The log should provide clues to why things aren't working out.

On Sat, Jun 16, 2018, 9:24 PM <coco at jechar.ca> wrote:

> Ok I tried that but it is still not working do I need to change
> port numbers ect I am using local host.
>
>   I hust did a cut paste and changed a few things I do not know
>   if AUTOSTART can be on for both and I am using TCPIP Client 65503
> TCP/IP Server 65504 for both should I change the second
> to something different ?
>
> On 2018-06-16 20:08, Aaron Wolfe wrote:
> > Sure, you can have as many <instance> sections as you like in the
> > config
> > file.  I usually just copy one and edit to taste.
> >
> >
> > On Sat, Jun 16, 2018, 8:06 PM <coco at jechar.ca> wrote:
> >
> >>
> >>   I wanted to create a second Instance but Instance Manager
> >>   does not seem to work in Linux can a second instance be created
> >>   by editing the XML in config.xml - The original 4.3.4E I
> >>   downloaded was setup for MS Windows and TCP/IP but I am running
> >>   ubuntu and a coco on a USB port.
> >>   It took a few edits to the config.xml to get the system working
> >>   at all, it runs fine now but I would like to have my second coco
> >>   attached to a com port as a second instance so I could switch
> >>   between the two systems quick.
> >>
> >>   I can send you the current XML code if that helps let me know.
> >>
> >>   Charlie
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> https://pairlist5.pair.net/mailman/listinfo/coco
> >>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>