JP1 Remotes

Posted: **Wed Mar 07, 2007 8:15 am**

here is what thw batch file reads with the pause,,,,,

c:\documents and settings\lindas\desktop\cap>c:\program files\java\jre1.5.0_03\bin\java -jar c:documents and settings\linda\desktop
cap\captureir.jar
'c:\program' is not recognized as an internal or external command, operable program or batch file.

i tried this on my old crappy computer and my newer desktop and get the same error on each one. any ideas?

Posted: **Wed Mar 07, 2007 8:22 am**

I didn't realize the path to java had a space in it (between "program" and "files").

I think you can make that work in a .bat file using quotes around the whole string "c:\program files\java\jre1.5.0_03\bin\java"

Also, as I said before, I always put the .bat file in the same directory as the .jar file, so I don't need a path to the .jar file.

You have a path to the .jar file, with another space in it. Quotes around the whole string "c:documents and settings\linda\desktop\cap\captureir.jar" would deal with that space, but I'm not sure there aren't other problems with needing a path to the .jar file.

Posted: **Wed Mar 07, 2007 8:33 am**

i was wondering about the path as well. i did try moving the "cap" directory to the root directory of the hard drive,, and changed the path in the batch file.
however,, the path to java still has the space in the directory "program files", and that is the default location for java.

Posted: **Wed Mar 07, 2007 8:59 am**

i tried the parentheses (sp?) around the first part of the string. when i ran the batch file, it didnt pause, but i tried starting captureir. it stayed running that time,, so i ran to get my remote. but the program had timed out by the time i got back. so i clicked on "start capture" again and started inputting signals from my remote. no signals were captured, so i restarted the computer and tried my other probe. this time the program went back to its usual behavoir, and just closed when i clicked on "start capture"
i have not been able to recreate the environment again to keep it running

Posted: **Wed Mar 07, 2007 9:01 am**

ok,, i reread your post to try to figure out if you had the correct spelling of "parentheses", lol,,, and saw that it was supposed to be quotes instead. i will try that now.
sorry about all the confusion on my part
sheesh

Posted: **Wed Mar 07, 2007 9:27 am**

im making some progress here. i moved the whole directory to the root directory of the crappy computers hard drive, changed the batch file to show the new path, added the quotes as you advised and ran the batch file.
the batch file ran, opened "captureir", and stayed running when i clicked on "start capture". it didnt take any readings, but i did get an output script in the dos box.
short of typing the whole message, it reads,,,
portreader: clock=1.19mhz unit=838.095uS gap_limit=477272
portreader: readlen=0
platform_win32_nt: using porttalk
opening porttalk driver
pid = 1544

Posted: **Wed Mar 07, 2007 10:07 am**

i took one of my probes and switched the output pin to number 10 and tried it on both computers. still no samples. i also tried closing all the printing funcntions using task manager.
i have not yet checked the output voltage on the number 1 pin.
if you guys have any other ideas,, im game to try

Posted: **Wed Mar 07, 2007 10:11 am**

OK, those are the printouts I expected (assuming things are working correctly up to that point).

But I'm still confused. Maybe I need a better description of what happened next.

If I understood you correctly earlier, when you clicked "start capture" the program (the whole captureIR GUI) goes away. Is that still happening? Or when did it stop happening? Did using the .bat file stop that?

If the GUI does go away at that point, then there ought to be something else in the printout from the .bat file, at minimum the output from the pause that lets you see what you just quoted.

mikeymike wrote:short of typing the whole message,

I hope you know how to use the edit mark and copy features of that window to copy/paste text to your post here. You shouldn't need to retype any of it. The edit features in a .bat output window are annoyingly different from edit features in ordinary windows, but not too tricky.

If the GUI doesn't go away, then we need to figure out why the probe isn't working.

1) Maybe it isn't getting enough power, as I mentioned earlier.

2) The QSE158 is fairle picky about the distance between it and the original remote. I think two to five inches is best. You may need to experiment.

3) The QSE158 has Polarity active high, and you said earlier you connected the center wire to pin 9. In CaptureIR's File menu there is a preferences dialog, on which there is a hardware tab. Check that for pin 9, and active high. Those should be the defaults, but maybe something changed.

4) You mentioned earlier grounding pin 9. I hope you meant temporarily for a test. If you left it grounded, that would make it not work.

Posted: **Wed Mar 07, 2007 10:50 am**

i dont know how to cut and paste from a dos box, lol,, sorry (but i will try)
no, the GUI didnt close. the program ran as i would have expected, it just didnt take any samples. so at this point,, im assuming the program is running ok.
i checked the power to the number one pin and it is 4.35 vdc and ive tried changing the distance between the remote and probe. ive also tried other remotes. ive checked the preferences, and tried sampling on high and low. im not bad at soldering,, but it is possible that the gun i am using is too hot (its not a pencil style gun, but more of a pistol style), in which case,, i may have burnt out both of the IR sensors.
is there any type of continuity test i can run on the sensor itself?

re: the grounding of pin 9,, that was only as a test for using digitrace, and the test worked. i did get a reading from that in digitrace.

ps,, i also dont know how to do the quotes from within the forum here like you have been doing.

Posted: **Wed Mar 07, 2007 12:37 pm**

mikeymike wrote:at this point,, im assuming the program is running ok.

I still don't know when/why it changed from aborting when you press "start capture" to working, but I guess we don't need to know. Now we need to figure out why no data is seen.

mikeymike wrote:i checked the power to the number one pin and it is 4.35 vdc

By "number one pin" do you mean pin one of the printer port? Or the Vcc pin of the QSE158? The important question, if you mean pin one of the printer port, is did you measure it while the probe was connected?

4.35 vdc on printer port pin one with nothing connected is typical and proves little.

4.35 vdc on printer port pin one with the probe connected is surprisingly high and I think proves there is plenty of power for the QSE158.

Assuming you can check voltages with the probe connected, check the middle pin of the QSE158 connected to pin 9. It should have a fairly low voltage.

Next try checking it while you are sending an IR signal (I know that's a bit tricky, but I'm a klutz and I managed). It should go up a little. It would vary too fast for a dc volt meter to see, but the meter should see the average, which is up a little vs. the baseline.

I expect you were testing with the remote whose signals you want to capture. Maybe that is a problem. To see if the probe is working, test it with your JP1 remote instead. Use some ordinary setup code (not learned signals).

mikeymike wrote:im not bad at soldering,, but it is possible that the gun i am using is too hot (its not a pencil style gun, but more of a pistol style), in which case,, i may have burnt out both of the IR sensors.
is there any type of continuity test i can run on the sensor itself?

I don't think there is. Let's see what Tommy says. He knows a lot more about that aspect than I know.

mikeymike wrote:ps,, i also dont know how to do the quotes from within the forum here like you have been doing.

To start the process, press the quote button within the post from which you want to quote.

If you only want one quote from that post, delete the text you don't want to quote, but not the tags in [] at the beginning and end of the quote. Then add in your reply below the ending tag.

If you want to quote several small chunks you need to copy/paste those tags so each small chunk you want to quote has the beginning tag before it and the ending tag after it.

Posted: **Wed Mar 07, 2007 1:29 pm**

lets try this quote thing,,,

[quote="johnsfine"]

I still don't know when/why it changed from aborting when you press "start capture" to working, but I guess we don't need to know. Now we need to figure out why no data is seen.

Posted: **Wed Mar 07, 2007 1:31 pm**

johnsfine wrote:
mikeymike wrote:at this point,, im assuming the program is running ok.
I still don't know when/why it changed from aborting when you press "start capture" to working, but I guess we don't need to know. Now we need to figure out why no data is seen.
.

Posted: **Wed Mar 07, 2007 1:41 pm**

Maybe you also need to learn how to use the edit button on your own previous posts.

The preview button is also pretty useful.

There is also a X button (next to the edit button) that you can use to delete a post.

I probably should use preview more myself. I usually press submit, then read what I just wrote and immediately press edit to fix it (which is what I'm doing right now to this post).

Posted: **Wed Mar 07, 2007 1:51 pm**

johnsfine wrote: I still don't know when/why it changed from aborting when you press "start capture" to working, but I guess we don't need to know. Now we need to figure out why no data is seen.

i think when i changed the location,, and path,,, to the root directory,, it didnt have the space between documents and settings anymore.

johnsfine wrote:
By "number one pin" do you mean pin one of the printer port? Or the Vcc pin of the QSE158? The important question, if you mean pin one of the printer port, is did you measure it while the probe was connected?

pin one on the probe(qse158) while it was plugged in

johnsfine wrote:
Assuming you can check voltages with the probe connected, check the middle pin of the QSE158 connected to pin 9. It should have a fairly low voltage.

i amy have misread the voltage before,, let me give it to you again. all voltages tested from the sensor end while it is plugged in
pin 1= 4.89
pin 9=4.89
pin 25= 4.35
there is not noticeable variation in voltage from the center pin (pin 9) when i send a signal to the sensor (these reading were take from the above mentioned pin placements to the chassis of the computer)

johnsfine wrote:
I expect you were testing with the remote whose signals you want to capture. Maybe that is a problem. To see if the probe is working, test it with your JP1 remote instead. Use some ordinary setup code (not learned signals).

yes,, i was using the remote i need to decypher, but i also tried other remotes from around the house. i dont have a jp1 remote to try.

i hope these quotes turn out right or it may be confusing to read

Posted: **Wed Mar 07, 2007 3:16 pm**

mikeymike wrote:pin 25= 4.35

mikeymike wrote:(these reading were take from the above mentioned pin placements to the chassis of the computer)

I wonder whether the chassis is a valid ground reference.

Pin 25 is supposed to be ground.

On some printer ports, pin 25 isn't ground, in which case that is likely the problem, and you should connect the ground pin of the QSE158 to some better ground.

But until I know whether your ground reference was OK, I don't want to conclude that pin 25 isn't ground.

Every printer port pin in the range 18 to 25 is supposed to be ground. At least one of those must be ground, or the printer port couldn't work. If your ground reference is good, you should be able to find one of those pins that is ground by checking the voltage on each.

If your ground reference isn't good, you may need to try each of the pins 18 to 25 as a ground reference to see which gives sensible results.

This is another part of the area where Tommy knows more than I know. Hopefully he'll jump in soon with a comment.

there is not noticeable variation in voltage from the center pin (pin 9) when i send a signal to the sensor

There wouldn't be any variation if pin 25 isn't ground, but there also wouldn't be if the chassis point you used for reference is electrically floating.

JP1 Remotes

IR probe & Digitrace questions

this is a test

another test