Skip to content

V2.0.0-RibEye

Latest
Latest
Compare
Choose a tag to compare
@frivolas frivolas released this 27 Jul 15:36
· 5 commits to master since this release
V2.0.0
139ed7d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

TinyTerm

V2.0.0 - Ribeye

This version of tinyTerm has a bit less fat on it, hence the name.

Added:

  • Added reportEvent() method to make the comms to the user much leaner:
    reportEvent();
    replaces:
    myTerminal.append();
    myTerminal.scroll();
    println();

  • Sends a $ej:0 tinyG command upon connection to the tinyG to make sure the comms happen in TEXT mode. If comms are configured in JSON mode ($ej:1), tinyTerm fails to catch the status reports. This is a super annoying bug that still needs to be resolved. But this quick workaround has been implemented.

  • Fully functional homing routines have been implemented. The user can home the machine by sending the following commands:

Command Action
home homes all axes (Z, X, A, in that order)
homea homes axis A (special routine)
homex homes axis X (simple canned cycle
homez homes axis Z (simple canned cycle
  • Fixed some issues with the queue manager that was locking the app if the scripts had comments ( or tinyG commands $ in them. Since the tinyG doesn't send a response for either of these, I now look at the outgoing string and if it's either a comment or a tinyG command I don't add to the buffer. This seems to work pretty good.

TinyTerm V2.0.0 does:

  • Runs a full homing sequence for a DIWire PRO for axes X, Z and A
  • Sends raw GCode and tinyG commands
  • Dumps text files (one line at a time)
  • Dumps init files (configuration files) in JSON format
  • Save log files and make them human readable
  • Allows to send the same file multiple times and keep track of how many times it's done it
  • Reads tinyG status codes, looking for {stat:3} and {stat:6} status reports.

TinyTerm V2.0.0 doesn't:

  • Doesn't run custom homing sequences
  • REMOVED: Runs a custom "measure" sequence that uses the digital I/O pins to detect changes on a probe - Raspberry Pi Only

Compatibility:

  • Windows only

Known issues:

  • The memory issue is still an issue. Haven't looked at it
  • Homing the A axis may be tricky sometimes. Still unknown why the INTERLOCK ($di1fn:2) will be set only sometimes (non-repeatable bug)
  • Equally annoying is that the INTERLOCK HIT (stat:6) seems to not be read sometimes
  • The workaround for this is to send the homea command again, you may need to resend the init file first, but if you try again, it will work.
Assets 3
Loading