September 2019 Update

New! We're moving to the new forum, eventually it will replace this blog. Please join us there.

View the Most Recent Feature Sheet by clicking HERE!

Wednesday, June 19, 2019

GBW Serial Terminal - Update #1

Lot's of improvements...

I've added more options, and whenever you change one of those options, they are saved using the properties.settings   It also saves the form size if you change it...

During the handshake with the module, it will receive the modules name, and put it on the form title along with the com port. This helps when you have many terminals open to different modules...

I also added a {{CLS}} tag to clear the screen...  I'm sure I'll be adding many more....

Here's the latest....


This terminal offers all the features (and baud rates) that the Arduino IDE Serial Monitor does...
and more!

I still want to try making it work across the network and allow me to connect to my modules hooked up to another laptop....

You may have noticed the date, 1970/01/01 on the first line with a date...  That's because this is my development module, and doesn't have a clock on it, it gets the time from the MySql database, so until it gets on the network, it doesn't know the time... You notice the identifier on the left side [M03] is for Module 3, and the first line is [M??] because it hasn't looked itself up in the database to know it's own ID.  It looks itself up using it's MAC address...



2 comments:

  1. In order to connect to any module, anywhere, I need to keep track of where they are hooked up.

    So I created a table to define the RPC Servers, each one gets an RPCServerId, and using that Id, I store the name of the RPC Server (GrowRoom, Development, etc) and it's IP Address and RPC Network Port.

    There is a Module IP table which contains the live IP Address of each Module, so I've added the RPCServerId field, which if > -1 means it is hooked up to that RPC Server via USB.

    The only thing missing is the Com Port for that USB connection. I added a ComPort field to the Module IP table as well.
    Now, you may ask, how can a module know the COM Port it is hooked up to?
    Well, during the handshake between the GBW Serial Terminal and the module, the terminal passes the port name to the module, and the module then updates the table...

    Pretty cool...

    Next step, rather than selecting a com port when using the terminal, I want to make it so I just select a module name, and it will determine how to connect to it... It might be a local com port, or it may have to connect to the com port via the RPC Server on another computer... it will be seamless...

    Granted, this isn't a feature which directly affects the grow room, but it's a cool idea and I just want to flesh it out...

    ReplyDelete
  2. Got tired of waiting 10 seconds every time I rebooted a module... Now, I've rearranged the bottom of the screen, and added a checkbox, "Setup Module Credential on Connect" and if checked, immediately sends a C to enter the configuration, otherwise, it sends an S to skip, which is a new feature as well. Either way, there is no more waiting...



    ReplyDelete

Any comments deemed off topic or offensive will be removed