Another happy USB customer...

Phriendly · Post by **Phriendly** » Mon Sep 29, 2003 4:54 pm

Mark Pierson wrote: I went back to v0.03A and was able to download and upload without any error messages. It also yielded the same Debug results except that LED P1.0 is unchecked.

I guess it's possible I fried something else when the capacitor went poof (but then why does 0.03A work?). I've got another set of components coming (they should arrive tomorrow), and I'll be building another interface.

Curiosor and curiosor. I keep all the source for the version I upload. I will really have to think on this one.

OBTW if version 0.03A works then I don't think your hardware got fried. I know that unlike what I was taught (that digital electronics would either be good or bad, not in between) that digital electronics can have these fun gray regions. But the simplest explanation is ususlly the right one.

I'll get back to you. In the meantime use 0.03A.

Joe

Mark Pierson · Post by **Mark Pierson** » Mon Sep 29, 2003 6:24 pm

Phriendly wrote:Please ohm out the connections from Delcoms chip p0.0 & p0.1 to the 6 pin connector.

I checked all 4 lines to the JP1 connector and they're all ok. The three 1k resistors all test ok as well.

if version 0.03A works then I don't think your hardware got fried

I also think it's working. As a test, I took a known file ("1994.txt" that comes in the IR archive) and uploaded it to my 1994. I exited and restarted P-USB 0.03, and then did a download. The results match the original file.

In the meantime use 0.03A

I would except it doesn't have the File Save ability!

Also, I've tested on 4 different remotes (1994, 2103, 2104, 8810w), all with the same results (0.03 works, 0.05 doesn't - same error messages).

Phriendly · Post by **Phriendly** » Mon Sep 29, 2003 9:05 pm

Mark,
I'm modifying 0.05 to be more userfriendly and report better errors. I hope this will be able to tell us something re: what your seeing. I hope to have this by tomorow.

Joe.

Mark Pierson · Post by **Mark Pierson** » Tue Sep 30, 2003 5:23 pm

Phriendly wrote:I'm modifying 0.05... I hope to have this by tomorow.

My new components arrived today, and I just finished assembling my second USB interface. Still no luck with 0.05, however. I get the same results ("SendPacket - Read System Variables - ERROR") as the first interface. The old 0.03 version still does up/download on the new interface.

So... I'm eagerly awaiting the arrival of the next version of P-USB.

Phriendly · Post by **Phriendly** » Tue Sep 30, 2003 6:43 pm

Mark,
Since 0.03A worked I figured it was something in my code. Now what????. I'm doing some last things to check the EEPROM then I will put it online. Unless you want to check w/ what I have now. The only difference will be looking at the EEPROM and chip select and reporting the results.

Joe.

Mark Pierson · Post by **Mark Pierson** » Tue Sep 30, 2003 6:56 pm

Phriendly wrote:Since 0.03A worked I figured it was something in my code. Now what????.

I'm wondering the same thing. What changed in the comm routines between the 2 versions? I noticed that the confirmation dialog boxes are different, but I assumed that was just a UI enhancement. I'm also assuming that 0.05 works for you, correct?

Phriendly · Post by **Phriendly** » Tue Sep 30, 2003 7:10 pm

Mark Pierson wrote:I'm also assuming that 0.05 works for you, correct?

Works fine. I'm using both large and small EEPROMS now. I'm test some autodetect options that my give us some info on you problem. This is why I'm waiting to upload it. But the current version is updated to give more info if you want to try it.

Joe.

Phriendly · Post by **Phriendly** » Tue Sep 30, 2003 8:26 pm

Mark,
I've uploaded 0.06A version. Try it. Please note any reported errors. Also chose "autodetect" TAB not button, hit "read addr" and tell me what you get.

Thanks
Joe.

Mark Pierson · Post by **Mark Pierson** » Wed Oct 01, 2003 4:38 am

No go... now any attempt to up/download results in multiple "SendPacket..." errors. The only way to get out of the loop is to abort the program.

When I hit [Read Addr], I get the "SendPacket..." message, but the following eventually displays:

Addr = 0, Cmd = 0xA1 - FAILED
Addr = 1, Cmd = 0xA3 - PASSED
Addr = 2, Cmd = 0xA5 - PASSED
Addr = 3, Cmd = 0xA7 - PASSED
Addr = 4, Cmd = 0xA9 - PASSED
Addr = 5, Cmd = 0xAB - PASSED
Addr = 6, Cmd = 0xAD - PASSED
Addr = 7, Cmd = 0xAF - PASSED

Phriendly · Post by **Phriendly** » Wed Oct 01, 2003 8:01 am

Mark Pierson wrote:No go... now any attempt to up/download results in multiple "SendPacket..." errors. The only way to get out of the loop is to abort the program.

Please give me the full messages, both the heading and the body of the window that comes up. If only one of those changes then please note that. You don't need to give me 300,000 sequential errors, just the trend please.

Mark Pierson wrote:When I hit [Read Addr], I get the "SendPacket..." message,

Again for this one please give me the trend.

Mark Pierson wrote: but the following eventually displays:

Addr = 0, Cmd = 0xA1 - FAILED
Addr = 1, Cmd = 0xA3 - PASSED
Addr = 2, Cmd = 0xA5 - PASSED
Addr = 3, Cmd = 0xA7 - PASSED
Addr = 4, Cmd = 0xA9 - PASSED
Addr = 5, Cmd = 0xAB - PASSED
Addr = 6, Cmd = 0xAD - PASSED
Addr = 7, Cmd = 0xAF - PASSED

Ok Now I'm really confused. At this time I can't figure how one could get this response w/ the internal EEPROM working correctly. But I'm probobly missing something.

Thanks,
Joe.

Phriendly · Post by **Phriendly** » Wed Oct 01, 2003 2:35 pm

Mark Pierson wrote:Also, I've tested on 4 different remotes (1994, 2103, 2104, 8810w), all with the same results (0.03 works, 0.05 doesn't - same error messages).

Can you tell me what size EEPROM these remotes have. I have a 1994 remote so I know it is a 2k. I just know the others.

Joe

Phriendly · Post by **Phriendly** » Wed Oct 01, 2003 2:49 pm

Mark,
I've been doing my testing w/ a EEPROM on the USB board and with my 2116. No problems. But I connected in my 1994 and I see some of what I think you are seeing. Now that I can reproduce this here I can work on it better.

I'll be getting back to you.

Joe.

Phriendly · Post by **Phriendly** » Wed Oct 01, 2003 3:29 pm

Mark,
Tommy Tyler mentioned testing this w/ fresh batteries to see if there would be a problem. I had old batteries in my 2116 which I did some testing w/ besides the EEPROM on the USB board. My 2116 had relativly fresh batteries and it had simular problems as yours. When I put the 'older" batteries from my 2116 into my 1994 it then worked also. I'll have to talk w/ Tommy more about this, but put in older batteries (mine was actuall less than 1VCD per cell, 3.9VDC for 4 cells).

Joe.

Mark Pierson · Post by **Mark Pierson** » Wed Oct 01, 2003 3:46 pm

Phriendly wrote:Please give me the full messages, both the heading and the body of the window that comes up.

Whenever attempting to up/download, I get a messagebox titled "Projectusb" with the following message "SendPacket - Read System Variables - ERROR". It's an endless loop as far as I can tell so I need to terminate ProjectUSB from the Task Manager.

On the Auto Detect tab, when I hit the [Read Addr] button, the following appears "Addr = 0, Cmd = 0xA1 - Failed", followed immediately by the same messagebox error from before ("SendPacket - Read System Variables - ERROR"). Each time I click the [Ok] button, the next line appears in the text window, followed by the error message, until I get all 8 address lines:

Addr = 0, Cmd = 0xA1 - FAILED
Addr = 1, Cmd = 0xA3 - PASSED
Addr = 2, Cmd = 0xA5 - PASSED
Addr = 3, Cmd = 0xA7 - PASSED
Addr = 4, Cmd = 0xA9 - PASSED
Addr = 5, Cmd = 0xAB - PASSED
Addr = 6, Cmd = 0xAD - PASSED
Addr = 7, Cmd = 0xAF - PASSED

Can you tell me what size EEPROM these remotes have.

All the remotes have the standard 2k EEPROM.

Tommy Tyler mentioned testing this w/ fresh batteries to see if there would be a problem.

Good ol' Tommy! The ever-helpful one...

I've tried fresh batteries, old batteries, 3 batteries with a shunt, no batteries... nothing seems to matter.

Not knowing a thing about the hardware, and probably even less about the software, I still can't understand why 0.03 works and 0.05/0.06 doesn't.

Phriendly · Post by **Phriendly** » Wed Oct 01, 2003 4:25 pm

Mark Pierson wrote: Good ol' Tommy! The ever-helpful one... I've tried fresh batteries, old batteries, 3 batteries with a shunt, no batteries... nothing seems to matter.

Not knowing a thing about the hardware, and probably even less about the software, I still can't understand why 0.03 works and 0.05/0.06 doesn't.

Ok you must just live in an alternate reality where the laws of nature are different(argggggg).

To keep things common, for the test just use the 1994 since I have one here also. This should keep the variables to a minimum.

Make sure you have a backup of the 0.03A that you downloaded from the files section. Then download from the file section the 0.03A there. I lost the ZIP file I uploaded and (I still have the source and EXE for 0.03A) and I uploaded the EXE I have here. I would like you to try that "new" one to see if it aggrees w/ the 0.03A that you have been useing. If this "new" one works the same I will start using that as a starting point for sending you some test programs.

Again PLEASE keep the original 0.03A that you have working there.

Joe.