JJ's neattools modules, some for Viz build 13 modules

Download January 2000 modules and NTLs, unzip to neattools directory

Download Viz VRML files that go with above NTLs, unzip to viz directory

Visualizer documentation is separate, look here for Java 3D visualizer documentation.

01/25/00 additions

01/22/00 additions

01/13/00 additions

Added JTTSObj for text-to-speech output, requires Microsoft Speech SDK (probably only needs subset, but I have whole thing installed, not sure which part is absolutely necessary)

01/12/00 additions

01/06/00 additions

01/04/00 additions

12/10/99 additions

12/01/99 additions

11/22/99 additions

tMonitor Instructions

1. Unzip dtmf.zip into the neat directory.
2. If you want tMonitor to send DTMF to another computer on the network, edit the file connect.txt to have a single line with the name of the remote computer.

   For example, to send tMonitor digits to neattools on computer JJworkstation, edit connect.txt to have a single line:

   JJworkstation
   

3. By default, tMonitor hangs up phone when a * DTMF is detected. To override this, start tMonitor with a command line sequence that should cause it to hang up.

   For example, to cause the sequence "##**" cause the hangup, start tMonitor as follows:

   tMonitor "##**"
   

4. run neattools, load file DTMF.ntl. This file lights up LED display for each DTMF pressed.

When not connected to tMonitor, DTMF module has fuzzy unreadable red letters. The red LED modules to the right are attached in same order as digits on telephone touch tone interface. Pushing a digit on telephone makes LED module go on.

And here is how it looks when connected to tMonitor

Module changes associated with Viz Build 13

JTrans2 now saves names of DEFs as received from viz loading world, and uses this name as name of module, rather than using name "JTrans2". Name can be used later to synch up changes with VRML file (currently if vrml file adds DEFs, the NTL gets out of synch).

Module changes associated with Viz Build 11

Starting with build 11 of viz, neattools and viz are more tightly integrated. The following behavior is supported:

1. neattools JViz2 module can instruct viz to load a specific VRML file when the NTL file is loaded.
2. viz sends neattools a list of DEF names for the VRML file loaded. This list is used by the JTrans2 module to allow "by-name" changing of properties of visual objects displayed by viz.
3. neattools automatically sends calibration information to viz when it first connects to viz, or when it loads a new NTL file
4. viz requests new calibration from viz when it loads a new VRML file

The end result is that viz should be totally controllable from the NTL file of neattools. Loading a NTL file can cause viz to load a VRML file, and once viz automatically receives the calibration information, viz should be modifying the visualization under control of neattools.

Example NTL files

• JViz2.ntl -- simple demonstration of single signal grid control from neattools. The mouse X/Y location are sent to the viz for the X/Y location of the signal, and the Y location doubles as the signal value.
• 1ball.ntl -- recording movements of a single ball in viz, pressing the space bar to insert "pause" markers in the recording. Playback with 2ball.ntl to see playback pause and to have it continue with collisions.
• 2ball.ntl -- load this NTL, then from viz, playback a recording made with 1ball.ntl with pause markers. When live data mixed with recorded data, "pause" can be continued when live object collides with paused recorded object.
• ypw.ntl -- demonstrates text nodes and yaw/pitch/roll control over objects. Note, orientation controls can be combined, they do not have to be one-only as in this example.
• gps.ntl -- shows connection to GPS, tested with Magellan GPS 315 NMEA 0183 version 2.1
• jviz_2plane.ntl -- demonstrates two independent signals displayed on two different planes.
• scale.ntl -- demonstrates scale changes of objects.
• Intersense.ntl -- demonstrates test using intersense device. NOTE: intersense is almost compatible with Polhemus, so Polhemus module is used with Intersense device.
• winamptest.ntl -- demonstrates controlling winamp, assumes winamp already running with a playlist.
• ttstest.ntl -- demonstrates text-to-speech, uses keyboard, keys 0-9 result in phrases 0-9 being spoken. The phrases are properties of the module, so can be changed to anything.

Module Conventions I use:

Static Pattern Module

Static Creator Module

Dynamic Pattern Module

Dynamic Creator Module

Space Marker Module

SPACE.NTL - this file uses the mouse X & Y as the two gesture dimensions, and uses LEFT BUTTON as the gesture defining signal.

Which means CLICK-DRAG defines a gesture.

The space module visualization is proportional to the screen dimensions, so while you might drag a big area of the screen, the gesture appears color coded within the module.

JViz2 -- Interface to 3D Data Visualizer

JViz2 handles the main x/y/z/signals1-5 visualization.

JTrans2 handles property controls of a single object in the visualization. Any control data generated by JTrans is routed through JViz2 to reach the visualizer.

JViz2 - x/y/z/signal visualization

Properties

• fileToLoad -- sent to viz when changed, or when NTL first loaded. Viz then loads this file.

JVIZ2.NTL - to use this:

1. calibrate inputs
2. enable socket, if this connects successfully to visualizer, you should see a tiny bright red square in upper left of "Viz Client".
3. from this point on, all location information is transferred over to visualizer, and you should see a "spray paint" effect on the surface.

JTrans2 - single object visual property controls

JTRANS.NTL - to use this:

1. set up JViz (see above), but first disable socket client, and increase the number of channels it can accept. JViz and JTrans both connect to same socket client, but it only accepts these connections of its property N is increased from 1.
2. connect all three inputs to JTrans module, you can decide later what these inputs actually control
3. calibrate inputs
4. enable socket, if this connects successfully to visualizer, you should see a tiny bright red square in upper left of "Socket Client". NOTE: this requires the JJ version of Socket Client!
5. send calibration info to visualizer
6. from this point on, the JTrans continually sends information to the visualizer. To select what it controls, edit properties.

JTransformer properties:

1. transformObject -- refers to which DEF in the loaded VRML file. Transform DEFs are used to control location, orientation, and scale. Material DEFs are used to control color.
2. transformType -- list of types supported:
   • main data -- unsupported at this time, there in case JViz merges into this module (not clear if this is desirable at this point)
   • location -- for controlling a particular transformObject location. In the corresponding VRML file, there is a "DEF xxx Transform".
   • orientation -- for controlling a particular transformObject orientation. In the corresponding VRML file, there is a "DEF xxx Transform".
   • emissive color -- for controlling a particular transformObject emissiveColor. In the corresponding VRML file, there is a "material DEF xxxx Material", and that material is associated with a Shape with PointSet or IndexedLineSet geometry.
   • diffuse color -- for controlling a particular transformObject diffuseColor. In the corresponding VRML file, there is a "material DEF xxx Material", and that material is associated with a solid shape (i.e. a Shape with any geometry except PointSet and IndexedLineSet)
   • scale -- for controlling the size of a particular transformObject. In the corresponding VRML file, there is a "DEF xxx Transform".
3. mapToMinI1, mapToMaxI1
   • objectType location --> min/max X location
   • objectType orientation --> min/max rotation about Y axis
   • objectType emissiveColor --> min/max red color
   • objectType diffuseColor --> min/max red color
   • objectType scale --> min/max X axis scaling
4. mapToMinI2, mapToMaxI2
   • objectType location --> min/max Y location
   • objectType orientation --> min/max rotation about X axis
   • objectType emissiveColor --> min/max green color
   • objectType diffuseColor --> min/max green color
   • objectType scale --> min/max Y axis scaling
5. mapToMinI3, mapToMaxI3
   • objectType location --> min/max Z location
   • objectType orientation --> min/max rotation about Z axis
   • objectType emissiveColor --> min/max blue color
   • objectType diffuseColor --> min/max blue color
   • objectType scale --> min/max Z axis scaling

mapToMinI1, mapToMaxI1, mapToMinI2, mapToMaxI2, mapToMinI3, mapToMaxI3 -- JTransformer always sends three values to associate with a particular object in the visualization. The objectType property determines what visual property these three values are controlling.

Since neattools is sending integer values, there are some conventions (described above with objectType) for mapping integer values into values the visualizer uses.

To change only one attribute, for example, to change only the red color of an object, just set the mapToMinNN and mapToMaxNN values to the same value that you want to be kept constant.

Detailed Examples

JViz2.ntl

Demonstrates

Visualization of a signal value related to an X-Y value. The grid visualizing the signal is an ElevationGrid.

Uses modules

• MouseX - sent to viz (via JViz2) as the X location of the signal
• MouseY - sent to viz (via JViz2) as the Y location of the signal, as well as the signal value
• JViz2 - handles automatic connection to viz, sends location/signal calibration information to viz

1ball.ntl

Demonstrates

Recording a ball position with the ability to insert "pause" markers in the recording. The ball is positioned in viz using the mouse, and the space bar is pressed to insert the "pause" markers in the recording.

After the recording is made, load 2ball.ntl, and play back the recording.

Uses modules

• MouseX - sent to JTrans2, provides X location of ball
• MouseY - sent to JTrans2, provides Y location of ball
• JTrans2 - used to control location of ball. NOTE: JTrans2 can control many attributes besides location. It can control color, orientation, scale.
• JViz2 - handles automatic connection to viz, forwards information from JTrans2 to viz

2ball.ntl

Demonstrates

Playback of a recording with "pause" markers. When playback starts, the ball moves to the first "pause" marker, and the "pause" checkbox is checked.

At this point, there are two ways to get the recording to continue:

1. click pause checkbox to clear it, at which point, the playback continues to the next pause marker
2. check off network data source to allow live input to control the cube. Then move the cube to the ball, to create a collision. The collision then causes the ball to move to the next "pause" marker.

Uses modules

• MouseX - sent to JTrans2, provides X location of ball
• MouseY - sent to JTrans2, provides Y location of ball
• JTrans2 - used to control location of ball. NOTE: JTrans2 can control many attributes besides location. It can control color, orientation, scale.
• JViz2 - handles automatic connection to viz, forwards information from JTrans2 to viz

ypw.ntl

Demonstrates

Orientation control provided by JTrans2 module. There is a single JTrans2 module for each viz object being controlled. Look in the properties of each JTrans2 module to see what object is being controlled and the type of control.

Each object should have a name, "Yaw", "Pitch", or "Roll". These names correspond to names loaded from the corresponding VRML file "ypw.wrl". If viz is not running, you will see "??" for names, since it is viz that provides these names based on the file it loads.

For type of control you will see orientation, the three min/max values correspond to yaw/pitch/roll. To handle Yaw, but leave pitch and roll unchanged, the min/max for pitch/roll are all set to 0.

Uses modules

• MouseX - sent to JTrans2, provides yaw/pitch/roll control over each text word showing in viz
• JTrans2 - used to control orientation of each text word in viz.
• JViz2 - handles automatic connection to viz, forwards information from JTrans2 to viz

The initial orientation of text in Viz looks like this:

As the mouse moves, it changes to something like this:

gps.ntl

Demonstrates

Neattools connecting to a GPS device that sends NMEA output out serial port.

Uses modules

• JCOMObj - GPS device is connected to COM port. In this NTL, the GPS 315 was used set to NMEA 0183 version 2.1 mode. Uses default GPS 315 com port settings, 4800 baud.
• JGPS - accepts data sent to COM, and decodes assuming NMEA format

jviz_2plane.ntl

Demonstrates

Neattools sending 2 signals to viz, viz displaying these signals on two different planes.

Uses modules

• JViz Client -- used to connect to viz, and tell viz to load jviz_2plane.wrl.

Here is how it looks from neattools:

Here is the corresponding VIZ, showing two different planes:

scale.ntl

Demonstrates

Neattools changing the location and scale of objects in viz.

Uses modules

• JViz Client -- used to connect to viz, and tell viz to load jviz_2plane.wrl.

Here is how it looks from neattools:

Here is the corresponding VIZ, the first picture shows the objects at the start:

The next picture shows the objects as they change scale depending on their location

Intersense.ntl

Demonstrates

Neattools reading data from intersense tracker.

NOTE: this is a little tricky to start up. Here's how I get it going:

1. hook up hardware
2. turn on Intersense, wait until red light stops blinking
3. start neattools, if no data coming through, click on continuous mode button and try again (if it doesn't work at first, it will after a few times

The tricky startup only occurs when Intersense first turned on. Once its on and running, everything works smoothly.

Uses modules

• JPolheumsObj -- intersense is almost compatible with Polhemus Fasttrak format. Had to modify polhemus module slightly to support it.

Here is how it looks from neattools:

winamptest.ntl

Demonstrates

Neattools controlling winamp MP3 player.

Uses modules

• JwinampObj -- has controls for next/prev track, play, pause, stop, and volume.

Here is how it looks from neattools:

dialertest.ntl

Demonstrates

Neattools outdialing telephone.

Uses modules

• JDialerObj -- collects integer digits to dial, has controls for backspacing, resetting, and "dial now".

Here is how it looks from neattools:

ttstest.ntl

Demonstrates

Neattools speaking arbitrary text using Microsoft Speech text-to-speech.

Uses modules

• JTTSObj -- when enabled, input 0-9 results in phrase 0-9 being spoken.

Here is how it looks from neattools:

The JTTSObj module has 10 properties, each is a text phrase, which can be spoken when the corresponding integer input is received. Here is a view of the properties:

speech.ntl

Demonstrates

Neattools recognizing arbitrary words using Microsoft Speech SDK.

Uses modules

• JSpeechRecognizerObj -- when enabled, has option of recognizing digits 0-9, and up to 10 phrases. The phrases are entered as text properties.

Here is how it looks from neattools:

The JSpeechRecognizerObj module has 12 properties, 10 of these are text phrases to recognizer, one is a boolean which turns on and off single digit 0-9 recognition, and one is a debugging boolean. Here is a view of the properties:

ntlfetcher.ntl

Demonstrates

Neattools loading NTLs from a remote web server.

Uses modules

• JNTLFetcherObj -- which uses web server to take a remote NTL file (in HTML format) and convert it to a local NTL file. When it is done, it sends out the local NTL file name
• JJNTLFileObj -- a slightly modified JNTLFileObj (Yuh-Jye says this change will eventually go into built-in JNTLFileObj), which takes a JString input and loads that file.

Here is how it looks from neattools:

When the fetch url button is pressed, it activates the JNTLFetcherObj, which has an input NTL path on the left side, and properties indicating the site to fetch from. The www.trapezium.com:80 means it will fetch from the web server at www.trapezium.com using port 80 (which is the standard web server port).

NOTE: the files fetched from the web server are HTML files. These HTML files are converted from NTL files using a program ntl2html.exe