|
|
I decided to update the Fireck32 software to use no windows forms, but otherwise it is essentially the same as the previous software. I'm calling this version 1.1.
If you know what the Firecracker module from X10 is, then you can control it from a command prompt or shortcut. See the information reproduced below from the readme file. This version of the software does not include the mscomm32.ocx control or come with an installer. MSComm32 is usually installed on most systems, anyway. If you need it, you can probably get it from many sites on the Internet. No install or uninstall, just unzip and use the .exe file. Source code is also included if you want to mess with it or fix it up.
If you'd like to contact me, you can email scottfisher2002 (AT SIGN) Y! (DOT) com. Hopefully you will be smart enough to realize how to format the previous email address and the bots wont. I don't want to put my email address directly on this site since it would probably get automatically harvested and I'd get more spam. The Y! is a symbol for Yahoo in case you didn't know that.
So you want to download? Go ahead and download the Fireck software, but be sure to read the readme file as a term of using it.
Fireck32 v.1.1
Command-prompt only version (no use of windows forms).
The Fireck32 utility was designed so that you can control X10's
Firecracker module under Windows 9x/ME/2000/XP from either a DOS
prompt or a shortcut. I wanted to be able to do some basic
scheduling of lights and appliances with the Firecracker but did
not want to pay the extra money for the elaborate software that
X10 sells since I really only need basic functionality. I don't
like elaborate software packages that include their own
scheduling utilities sucking up resources in the background since
Windows comes with its own scheduler, anyway. Thus Fireck32 was
born.
Installation
Extract the files from the zip file there is an exe in there called fireck32.exe which is the program.
Usage
The usage for Fireck32 is simple. Look at any of the
following examples to get the idea:
Fireck32.exe /com=2 /house=a /device=1 /action=on
Fireck32.exe /com=1 /house=f /device=9 /action=off
Fireck32.exe /com=4 /house=g /device=12 /action=bright
Fireck32.exe /device=3 /house=b /action=dim /com=3
Fireck32 /c=1 /h=a /d=1 /a=on
If you forget the options, type Fireck32 /? to list the options.
From a DOS prompt (and in the same directory as the Fireck32
file) you may type any of these items and they would take the
appropriate action. Before you try using this program you must
know which communications port your Firecracker is installed on
and which house code your X10 modules are set to (and of course
which device number and action you want to take).
You may also create shortcuts to the Fireck32 file and then add
these switches to the shortcut properties to take a specific
action. If you don't know what a shortcut is, or how to create
one, you may want to do a search on the internet.
Once you've created useful shortcuts (say to turn on and off the
lights you use the most) you can place these someplace convenient
such as on your desktop or in your Start Menu so you can quickly
turn lights on and off from your computer. You might even like to
place a shortcut in your Startup folder so that a certain light
turns on or off once your computer boots into Windows.
The shortcuts are the key to using Fireck32 in a Windows
scheduler--but I will not go into specifics since every scheduler
is different and you will need to check the documentation for
your scheduler yourself.
The switches for Fireck32 are fairly self explanatory--just
substitute the correct values for your situation instead of using
those above. The switches may be used in any order and even may
be abbreviated to just the first letter of the switch (as in the
last example). If you leave out any of the switches or make
errors typing the switches, the defaults will be used for the
missing or wrong switch. The defaults are /com=1 /house=a
/device=1 /action=off.
Disclaimer
Fireck32 worked great for me in the testing I did, but I cannot
guarantee that it will always work. I will not be held
responsible for your use (or misuse) of this software or
guarantee it in any way. I've made attempts to ensure that this
software causes no problems, but this is freeware and so I don't
have the time and money to do extensive testing. USE THIS
SOFTWARE AT YOUR OWN RISK.
Also please note that you should NOT use your X10 modules to
control appliances that may cause problems (such as fires) if
they get turned on accidentally or don't get turned off. X10
disclaims any responsibility for direct and consequential damages
and so do I. If you decide to hook up your iron (or similar
appliance) to an X10 module and your house catches on fire
because of it this is your own fault. YOU HAVE BEEN WARNED.
I've sometimes had things turn on or off randomly with my
X10 modules (maybe stray signals from the neighbors) so you need
to consider safety first and be ready for anything to turn on or
off at random without causing safety concerns.
Use of the Software (Freeware)
Fireck32 is freeware that you may use or distribute as you please
except that you may not charge for this software--except for
reasonable media costs if you are copying it for someone. You
must also leave all documentation and files intact if you
distribute it or bundle it in any way.
If you would like my contact information, check
http://www.scottfisher.freeservers.com/ where you will find this
information in its most up-to-date form. If I have time, I will
also post additional information about this software and other
topics of interest to me. I've included source code for this
project (in VB 6). Feel free to modify it or create your own
program around it, though it would be nice to get a bit of credit
if you base a program off it.
Fireck32 is based not only on my own code, but was originally
based on an .OCX control written by Joseph Sola called
Firecrax0r. You can find his web site at
http://reet.i.am/ and his .OCX can be useful if you want
to try your hand at programming your own utility for the
Firecracker. He includes all source code for his .OCX.
I removed this ocx, corrected a few bugs and just included
everything in an exe for this version of the software, tho.
A note about support: If you have problems or have questions
about this software, you may email me but I can't guarantee any
kind of response time. I will try to answer all reasonable
questions but you may find it faster to have someone else help
you if you know someone who is knowledgeable about computers.
Nothing is too unusual about this software so it shouldn't be
hard to figure out for someone with the background. Also, my
response may be slow to questions since the address listed on the
web site is not my primary email address. If you are not aware,
many advertisers comb the web for email addresses so they can
send junk, unsolicited email to every address they can find.
If you have suggestions or would just like to send feedback (good
or bad), you may also email. Any offensive, harassing, explicit,
erotic, etc. email will be deleted immediately and your email
address may be blocked so I never receive another email from it
again.
Known Conflicts/Problems
Palm Desktop software will interfere with the use of the
Firecracker if it is set to use the same port as your
Firecracker. The solution is to put your Firecracker on a
different port or disable the HotSync software from
automatically starting.
As with any Windows software, Fireck32 relies on Windows
to know about the hardware present in your system to work
correctly. The port that you use to attach your Firecracker
must show up in the Windows Device Manager. I suggest that
you make sure that the Firecracker works with the basic
utility from X10 before you install Fireck32.
Often a port not showing up in Device Manager occurs
because it is disabled in the BIOS setup for your computer.
If you don't have any idea what a BIOS Setup is or how to
get to it, I suggest you check with your computer
manufacturer for assistance.
Basic Info
Filename: Fireck32.exe (with support files) or Fireck32.zip (in
the archive)
Version: 1.1
Author: Scott Fisher (originally based on an .ocx by Joseph Sola)
Note: This is version 1.1 which works from a command prompt and
uses NO windows forms. It may require the mscomm32.ocx control
and also uses the Microsoft Scripting Runtime (Scripting.Filesystem object).
On most computers these libraries will already be present.
The code is rather messy and not elegant. I wrote it early on without
fully knowing how to do things. It does work, however. I made it
work in a command prompt-only environment with little revision Since
I never intend to modify and reuse this code I've left it alone and
haven't spent the time to streamline it. I don't want to fix what
isn't broken, but you can play with the code if you wish to make
it better.