ISoft Wiki - User contributions [en]

Installing LXW

2013-02-26T22:50:52Z

Dfleischman: Added the Note section

The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.

== Dependencies ==
Besides the regular version of [[MySQL]] used by ITrack Enterprise, LXW requires:
* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
* [http://php.net/downloads.php PHP] 5.3 or higher
* [http://nodejs.org/download/ Node.js] 0.8 or higher
* [http://subversion.apache.org/ SVN] 1.6 or higher

== Installing the server-side code ==
This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

To configure the database connection, edit /lxw/configs/database.php.

== Installing the client-side code ==
This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

== Setting Up the Auto-Updater ==
This is the process that will download updates for LXW and then install them.

[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
#Configure config.json
#Run the .sh files
##install.sh
##run.sh
#Add updater to crontab

===Configure config.json ===
An example of LKQ's config.json

<code>

{
"update_url": "https://isupdate:UpD8Me@www.isoftdata.com:443/autoupdate/update.php",
"product_code": "8298525",
"download_directory": "/var/www/lxw-release/updater/downloaded-all",
"destination_directories": {
"default": "/var/www/lxw-release/updater/downloaded-latest"/*,
},
"extraction_directories": {
"LXW-client.zip": "/var/www/html/lxw",
"LXW-server.zip": "/var/www/lxw-release"
}
}
</code>

After the updater is run properly then a new section will appear below this section and it will look like this.

<code>

"versions": {
"LXW-client.zip": "#####",
"LXW-server.zip": "#####"
}

</code>

===Run .sh Files===
Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

'''install.sh'''
<code>
sudo npm install isoft-updater -g
</code>

'''run.sh'''
<code>
node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

===Add Updater to Crontab===
The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

<code>
crontab -e
</code>

This is what LKQ's crontab looks like for the autoupdater.
<code>
12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

This is the format that crontab uses.

<code>
* * * * * command to be executed
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
</code>

====Note====
Removing the version section in config.json will cause it to redownload the latest update during the next scheduled update cycle or forced update. Can be used to test the process.

== Testing ==
Browsing to the [the URL you would expect to correspond to the client-side files you installed]/server/index.php should show you a snide remark embedded in JSON.

Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).

Installing LXW

2013-02-26T20:34:01Z

Dfleischman: Substituted all sample version numbers with #'s

The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.

== Dependencies ==
Besides the regular version of [[MySQL]] used by ITrack Enterprise, LXW requires:
* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
* [http://php.net/downloads.php PHP] 5.3 or higher
* [http://nodejs.org/download/ Node.js] 0.8 or higher
* [http://subversion.apache.org/ SVN] 1.6 or higher

== Installing the server-side code ==
This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

To configure the database connection, edit /lxw/configs/database.php.

== Installing the client-side code ==
This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

== Setting Up the Auto-Updater ==
This is the process that will download updates for LXW and then install them.

[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
#Configure config.json
#Run the .sh files
##install.sh
##run.sh
#Add updater to crontab

===Configure config.json ===
An example of LKQ's config.json

<code>

{
"update_url": "https://isupdate:UpD8Me@www.isoftdata.com:443/autoupdate/update.php",
"product_code": "8298525",
"download_directory": "/var/www/lxw-release/updater/downloaded-all",
"destination_directories": {
"default": "/var/www/lxw-release/updater/downloaded-latest"/*,
},
"extraction_directories": {
"LXW-client.zip": "/var/www/html/lxw",
"LXW-server.zip": "/var/www/lxw-release"
}
}
</code>

After the updater is run properly then a new section will appear below this section and it will look like this.

<code>

"versions": {
"LXW-client.zip": "#####",
"LXW-server.zip": "#####"
}

</code>

===Run .sh Files===
Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

'''install.sh'''
<code>
sudo npm install isoft-updater -g
</code>

'''run.sh'''
<code>
node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

===Add Updater to Crontab===
The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

<code>
crontab -e
</code>

This is what LKQ's crontab looks like for the autoupdater.
<code>
12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

This is the format that crontab uses.

<code>
* * * * * command to be executed
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
</code>

== Testing ==
Browsing to the [the URL you would expect to correspond to the client-side files you installed]/server/index.php should show you a snide remark embedded in JSON.

Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).

Installing LXW

2013-02-26T20:04:57Z

Dfleischman: Formatting fixes and added crontab format

The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.

== Dependencies ==
Besides the regular version of [[MySQL]] used by ITrack Enterprise, LXW requires:
* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
* [http://php.net/downloads.php PHP] 5.3 or higher
* [http://nodejs.org/download/ Node.js] 0.8 or higher
* [http://subversion.apache.org/ SVN] 1.6 or higher

== Installing the server-side code ==
This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

To configure the database connection, edit /lxw/configs/database.php.

== Installing the client-side code ==
This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

== Setting Up the Auto-Updater ==
This is the process that will download updates for LXW and then install them.

[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
#Configure config.json
#Run the .sh files
##install.sh
##run.sh
#Add updater to crontab

===Configure config.json ===
An example of LKQ's config.json

<code>

{
"update_url": "https://isupdate:UpD8Me@www.isoftdata.com:443/autoupdate/update.php",
"product_code": "8298525",
"download_directory": "/var/www/lxw-release/updater/downloaded-all",
"destination_directories": {
"default": "/var/www/lxw-release/updater/downloaded-latest"/*,
},
"extraction_directories": {
"LXW-client.zip": "/var/www/html/lxw",
"LXW-server.zip": "/var/www/lxw-release"
}
}
</code>

After the updater is run properly then a new section will appear below this section and it will look like this.

<code>

"versions": {
"LXW-client.zip": "27###",
"LXW-server.zip": "27###"
}

</code>

===Run .sh Files===
Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

'''install.sh'''
<code>
sudo npm install isoft-updater -g
</code>

'''run.sh'''
<code>
node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

===Add Updater to Crontab===
The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

<code>
crontab -e
</code>

This is what LKQ's crontab looks like for the autoupdater.
<code>
12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

This is the format that crontab uses.

<code>
* * * * * command to be executed
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
</code>

== Testing ==
Browsing to the [the URL you would expect to correspond to the client-side files you installed]/server/index.php should show you a snide remark embedded in JSON.

Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).

Installing LXW

2013-02-26T02:19:10Z

Dfleischman: Added how to setup the autoupdater

The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.

== Dependencies ==
Besides the regular version of [[MySQL]] used by ITrack Enterprise, LXW requires:
* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
* [http://php.net/downloads.php PHP] 5.3 or higher
* [http://nodejs.org/download/ Node.js] 0.8 or higher
* [http://subversion.apache.org/ SVN] 1.6 or higher

== Installing the server-side code ==
This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

To configure the database connection, edit /lxw/configs/database.php.

== Installing the client-side code ==
This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

== Setting Up the Auto-Updater ==
This is the process that will download updates for LXW and then install them.

[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
#Configure config.json
#Run the .sh files
##install.sh
##run.sh
#Add updater to crontab

===Configure config.json ===
An example of LKQ's config.json

<code>

{
"update_url": "https://isupdate:UpD8Me@www.isoftdata.com:443/autoupdate/update.php",
"product_code": "8298525",
"download_directory": "/var/www/lxw-release/updater/downloaded-all",
"destination_directories": {
"default": "/var/www/lxw-release/updater/downloaded-latest"/*,
},
"extraction_directories": {
"LXW-client.zip": "/var/www/html/lxw",
"LXW-server.zip": "/var/www/lxw-release"
}
}
</code>

After the updater is run properly then a new section will appear below this section and it will look like this.

<code>

"versions": {
"LXW-client.zip": "27###",
"LXW-server.zip": "27###"
}

</code>

===Run .sh Files===
Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

'''install.sh'''
<code>
sudo npm install isoft-updater -g
</code>

'''run.sh'''
<code>
node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

===Add Updater to Crontab===
The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

<code>
crontab -e
</code>

This is what LKQ's crontab looks like for the autoupdater
<code>
12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
</code>

== Testing ==
Browsing to the [the URL you would expect to correspond to the client-side files you installed]/server/index.php should show you a snide remark embedded in JSON.

Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).

TSC tag printers

2012-11-05T16:23:51Z

Dfleischman: /* Setting Up */

==Setting Up==

# Make sure that the customer has calibrated the Tag Printer before beginning.
## The printer's instruction booklet should tell the customer how to do this (it usually involves a series of button presses).
# Download the latest TSC Tag Printer Driver from [http://www.seagullscientific.com/aspx/thermal_95.aspx here] (scroll to the bottom, click the '''TSC''' link).
# Run through the installer
## If you can not find the exact model of printer in the list then you can go to 'Have Disk' and browse to 'C:/Seagull' and select the model from the new list.
# Once the printer is created, open up the properties of the printer
## On the General tab, click '''Printing Preferences...'''
## On the '''Page Setup''' tab click the '''Edit...''' button
## Change the '''Label Size''': Width to 4.00 and Height to 5.50
## Click OK
## Select the radio next to '''Portrait 180°'''
## Click the '''Stock''' tab
## Select '''Labels With Marks''' from the '''Type:''' drop down
## Change '''Mark Height:''' to 0.12in
## Click OK
## In the Tag Printer properties dialog, click the '''Advanced''' tab
## Click the '''Printing Defaults...''' button
## Repeat steps 4.2 through 4.9
# In ITrack, go to Edit > Options
# On the Printers tab, select '''Tag''' from the '''Printer Type''' dropdown
# Select the Tag printer that was just setup, from the '''Printer Name''' dropdown
# Open a part on the Part screen and print a tag
# Confirm that everything is fine and dandy

[[Category:Printing]]
[[Category:ITrack/Support]]

==Problems/Solutions==
===Tags print too light to be read===
A problem that has been experienced before is that tags are printing out too light and the information on the tag can't be read.

To fix this issue:
# Open up the tag printer's properties
# Go to the '''General''' tab and hit the '''Printing Preferences''' button
# The Printing Preferences dialog appears, go to the '''Options''' tab
# Change the print speed to 2.00in/sec and the darkness to 15
# Click Ok
# Make the same changes in the '''Printing Defaults''' on the Advanced tab
# There is sometimes an issue where the print speed won't save
# Reopen the '''Printing Preferences (General tab)''' and '''Printing Defaults (Advanced tab)''' dialog
# Check the Options tab to make sure that the Print Speed is 2.00in/sec
# If it has gone back to 4.00in/sec, see the section below titled '''Removing and reinstalling TSC tag printer drivers'''

===Removing and reinstalling TSC tag printer drivers===
# Take note of the printer model and port that the tag printer is using '''Properties > Ports (tab)
# Delete the printer
# In the Printers windows go to '''File > Server Properties > Drivers (tab) >''' find the tag printer in the list, select it and hit '''Remove...'''
# If you get an error about not being able to remove the driver, hit the properties button and take note of the driver path.
# Delete the directory you took note of in the previous step.
# Repeat the steps in the '''Setting Up''' section above.
# Go to the [printers] section in Host.ini and delete the line that begins with 'tag', then go into Edit >> Options and set the 'Tag' option back to the tag printer.
##If this is not done then ITrack will not recognize the new driver automatically and it will print to the Windows Default Printer.
##Another way fix this problem is to select a new printer in Edit >> Options and select a different printer then reselect the tag printer. This will cause ITrack to recognize the new driver and print to it instead of the Windows Default Printer.
# Tell everyone how awesome you are.

===The tag printer is not spitting the tag out to the black line or going past it===
# Add the printer as local (if the tag printer is physically connected to another computer then create a new port that includes the IP address of the computer it is hooked up to)
# Change the Feed Offset to .5 inches (make sure to change it in both the Printing Preferences and Advanced Settings)
# In the Printer '''Properties''' > '''General''' tab > '''Preferences''' > '''Stock''' tab make sure that '''Post-Print Action''' is set to '''Tear Off'''. Then check the same setting in '''Properties''' > '''Advanced''' tab > '''Printing Defaults''' > '''Stock'''

===The tag printer is hooked up to a computer that doesn't have the version of the driver required for the OS version you're trying to add it on===
# Install the tag printer as a local printer, as if it where physically connected to the computer you are trying to network it to
# Add a new port - make it a local port - and give it the port name "\\<name_of_computer_sharing_printer>\<printer_share_name>"

===Windows does not recognize the Tag Printer===
Things to try:
# Power Cycle the printer: Turn off power and unplug the machine for 30 seconds to a minute, then turn it back on and try to print again.
# Plug the tag printer into another USB port and try to print.
# Plug the tag printer into a different computer and test it.

===TSC TTP 246M User Manual===
The tag printer user manual can be found at: \\file\ITRACK\Tech Support\Drivers\TTP_246M_344M.pdf

===TSC Diagnostic Tool===
The wonderful folks over at TSC have created a diagnostic tool for their printers. This tool can read the printer status and tell you error the LED codes are describing, what version of printer it is, firmware version, driver version, allow you to do printer configuration and initialization without requiring the user to hold down buttons and interpret codes, set the printer settings described above without having to use the properties dialog, and other magical things. You can find it at \\file\ITRACK\Tech Support\Drivers\DiagTool_133.zip. Just transfer the tool over to the client machine and launch it from anywhere. Note the tool may not work with older versions of firmware, on older tag printers. At the very least it works with a TTP TSC 247. Instructions for using the tool can be found in the user manual (TTP_245p_247_343p_345_user_manual_eng.pdf), which you can find in the same directory on //File/ as the tool.