cheap single port TCP/Serial?

[Dean Roddey]

You don't want to do it that way. If you just want TCP -> Serial, then you tell CQC that it's a GC-100 serial port, which is completely unrelated to the main GC-100 functionality that the actual GC-100 device driver uses. So they are separately configured things, and they talk to different ports on the device. Do don't try to load the GC-100 driver at all.

[SomeWhatLost]

so, what doc tells me how to do that?
what would it be under?`
I tried looking through the various doc's, but I couldn't find anything... I am guessing I am looking at the wrong thing?

right now, even my existing GC100 serial ports are not showing up in the "select port for driver" area...
this is a mostly fresh install of the MS on a shiny new VM...
well, technically I did move my old CQC folder over and did an "upgrade" so "fresh" may not be the best choice of words... but it is new at least...

[Dean Roddey]

It's just a configuration option in the Admin Intf. In the 4.8 world, it's like Administer -> Settings -> GC-100s or thereabouts.

In the 5.0 world, it's /Configure/Ports/GC-100s.

Just add an entry for your GC-100s, then they will show up as available ports.

[SomeWhatLost]

well, that worked...

seems the Wiznet does seem to work fine... so ther you have it, a relativily cheap single port TCP -> serial that uses CQC built in GC100 com drivers...

one issue I have noticed is it seems to have a fair bit a latency... doesn't appear to be a problem as such, but I will keep an eye on it... just seems odd really...

[SomeWhatLost]

oh, and fwiw, the new 5.0 Admin interface layout is great, once I got over the newness/strangeness of it all, it actually is quite intuitive... and the ports config is right where I would of expected them to be if I hadn't been overwhelmed by all the changes...

[Dean Roddey]

Kewl, that was definitely what we hoped for after all of that work.