UIRT from Luc doesn't work - please help me diagnose it

[Wykat]

Same problem for me :cry:

I have following equipment/software installed;

1 original UIRT (Ruud design, used for reception only)
2 UIRT2 bracket transceivers
Girder 3.0
Girder 3.1
Girder 3.2

The original UIRT design works with all Girder versions as UIR/UIRT

a) I can program the UIRT2b with the 10 MHz version 1.7 (uirt-dp13 as programming software). Verify is also ok

b) there is no plugin yet for the UIRT2b and 3.2 so I couldn't try that. Would it be possible to use the UIRT2b as receiver only with the original UIR plugin ? It claims input device enabled, but doesn't receive any IR signal.

c) Girder 3.0 F9 replies with
"incorrect first character": old uirt plugin
"couldn't open input device's": UIR/IRMan plugin
"no OK uirt reply": UIRT DP plugin
"can't read first character": new uirt plugin

d) Girder 3.1
'Couldn't enable one or more input devices": standard UIR/IRMan/hollywood/etc.
"no OK: UIRT DP plugin

Somehow it looks as if the PIC is not running :cry: . Any idea how to proceed :-?

Wykat

[Wykat]

All those different UIRT drivers and firmware are a little tricky 8)

So the UIRT2b and Girder 3.0 require the new UIRT plugin (92Kb version 1.6) but there is no communication. Since programming/verifying work, cabling and com port setting (COM1) must be ok.

Girder 3.1 and new UIRT (1.6): "can't read 1st character"

I'm using WOL and voltage is 5.01 Volt. I'm only using the UIRT plugin and no GML file loaded at the moment. I've not attached the transmitting LED's yet, but can't assume that is a problem. Is there anything I have to do to the board when I use WOL ? I'm sure it's COM1 and as I said the original (Ruud) UIRT does work with the old UIRT plugin on the same port.

Wykat :-?

[Wykat]

Ok, it's working. :D

Configuration is Girder 3.1 with the new UIRT (1.6 version). I also discovered that after programming the second UIRT2b I placed the jumper back 1 too much (so still open) :oops: . I used the second UIRT2b with all the different plugins before I wrote above summary.

When I switched back to the first UIRT2b it was working immediately now. So it must be caused by the plugin why it wasn't initially working.

I had expected that you would have programmed and tested them :D so it had to be something simple. However programming made me sure that the communication and PIC where working.

Sorry for all the work, but I believe it would be helpful to have a clearly named UIRT2 plugin (since I'm also using Ruud's UIRT and a normal UIR) :wink: .

thx,
Wykat

[Wykat]

It was the wrong UIRT driver. This has now been resolved and everything is working including transmission. Only problem is still WOL, but that's posted in a separate thread.

Many thanks for your help anyway :wink:


Wykat

[Luc]

This is a different problem than the one of JayCee, his uirt communicates but the receiver is probably defective.
JayCee, is it solved already?


c) Girder 3.0 F9 replies with
"incorrect first character": old uirt plugin
"couldn't open input device's": UIR/IRMan plugin
"no OK uirt reply": UIRT DP plugin
"can't read first character": new uirt plugin

The 3 first are normal because you have to use the plugin by Jon wich you did in the 4th: This message indicates that Girder can't communicate with the uirt.

d) Girder 3.1
'Couldn't enable one or more input devices": standard UIR/IRMan/hollywood/etc.
"no OK: UIRT DP plugin

What happens here with the plugin by Jon?

Somehow it looks as if the PIC is not running :cry: . Any idea how to proceed :-?

What are you using to power the UIRT, WOL? Is the +5V supply OK?
Check that the settings for the comm port are correct and that there are no conflicts with other plugins and or programs.

Hope this helps,
Luc.

[Luc]

Yes you need Jon's firmware 1.6.

I suppose you tried both UIRT's and it would be impossible that they are both bad, they have been programmed and tested here.
The led's and even the receiver do not have to be connected.
A few things you could try:
- Did you replace the jumper to the normal position after re-programming? (silly question I suppose).
- Try with the testprogram http://www.girder.nl/phpBB2/viewtopic.php?t=1855 (thanks Anders)
- Try with the second cable.
- Check the level on the MCLR pin of the PIC, should be 5V.
- Try another comm port or another PC (I know it's almost impossible but you never know....)

Luc.

[JayCee]

I bought an assembled UIRT (bracket design) from Luc and haven't had any success in getting it to work. Here's the situation, maybe someone can point me in the right direction on where the problem is:

- I made an error at first and had the IR receiver connected incorrectly (swapped Vs and Out) - could that have damaged the IR receiver?

- Girder doesn't see any IR codes

- The UIRT testprogram seems to work: It says "sends" and then a number of hex-codes (depending on button press). Should I see anything different? (I'm not sure if the hex-codes I see are the requests to UIRT or the response)

- Daniel Pitcars testprogram gives me an error "OG code not received" (or something similar)

- the UIRT has power. I measured 4.9V between GND and Vs on the IR receiver

Any ideas out there?

thanks for your help
jc

[JayCee]

- [..] that have damaged the IR receiver?
Quite likely, I'm afraid.

OK - Will try to get a new one tomorrow.



- The UIRT testprogram
Which testprogram?

This one: http://www.girder.nl/phpBB2/viewtopic.php?t=1855



- Daniel Pitcars testprogram gives me an error "OG code not received" (or something similar)
Danijel's testprogram and plugin only work with his firmware.

I suspected as much...


If you can activate Jon's Girder plugin with 'Fast UIRT init' unchecked, and get no error codes, the PIC and PC-UIRT communications are most likely functioning correctly.


I get no errors from Girder, but Girder (3.1.3c) crashes more than it did before (actually it started crashing). I get different messages:
- UnHook failed (or similar)
- An XP "send all my information to MS, because an app crashed" error notification

Further ideas?

thanks
jc

[JayCee]

My - has my life been busy....

I haven't had a chance to buy a new IR receiver yet, so couldn't try that.

Andreas: I don't see any REC lines - I only see Send lines in your testprogram - I suspected that there must be a receive also..

I'm using COM1 and I know how to switch comports in your application.

So it seems there's more problems than just a burnt out IR receiver.

I most probably won't have any time to check on this for another two weeks (work, funeral, holidays) but will try again after that...

thanks
jc

[JayCee]

I got two SHF5110-38's from a colleague and soldering them in instead of the broken one - made my UIRT2 work immediately.

The only problem - it seem's I've got myself the -34 version... (A miniature 34 on the IR receiver is visible and I can't go away more than 50 cm from the IR receiver...

But that should be solvable easily. The more important thing is: I can control my other equipment now!

cu jc

[kari]

- I made an error at first and had the IR receiver connected incorrectly (swapped Vs and Out) - could that have damaged the IR receiver?
Quite likely, I'm afraid.

- The UIRT testprogram seems to work: It says "sends" and then a number of hex-codes (depending on button press). Should I see anything different? (I'm not sure if the hex-codes I see are the requests to UIRT or the response)
Which testprogram?

- Daniel Pitcars testprogram gives me an error "OG code not received" (or something similar)
Danijel's testprogram and plugin only work with his firmware. If you bought your UIRT assembled and programmed from Luc, I expect it uses Jon Rhees' firmware, as that is the only one that supports all the features of the hardware (GPIO and WOL). If you can activate Jon's Girder plugin with 'Fast UIRT init' unchecked, and get no error codes, the PIC and PC-UIRT communications are most likely functioning correctly.

-Kári.

[Jas39]

Simple test: Push GetVersion then you should se
Sends:
23,dd;
Rec:
01,04,FB;

Explained as
23,dd; is command 23 (Get Version) plus Checksum dd
01, 04, FB; is the response defined for Johns 1.7 fw.

Guessing from your mail, I would expect that you don't receive anything (no mention of Rec:). To which port is your uirt connected? The test app uses COM2 per default but can be changed by right clicking in the window.

Good luck
/Anders





- The UIRT testprogram seems to work: It says "sends" and then a number of hex-codes (depending on button press). Should I see anything different? (I'm not sure if the hex-codes I see are the requests to UIRT or the response)