Nova greece pvr3001
Moderator: Moderators
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Vicky, you're right. AS USUAL.
After posting my thing, I downloaded the .ict files and saw precisely what you say. If you or Rob want to delete my post, is ok with me, just to keep this thread clean of mistakes.
After posting my thing, I downloaded the .ict files and saw precisely what you say. If you or Rob want to delete my post, is ok with me, just to keep this thread clean of mistakes.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
If I deleted all my posts that had mistakes, it would be about half of them.
This does seem to be an interesting protocol. I'm always amazed at how Rob makes sense of these things.
I hope that Alan can capture the rest of the signals so we can analyze it more thoroughly.
This does seem to be an interesting protocol. I'm always amazed at how Rob makes sense of these things.
I hope that Alan can capture the rest of the signals so we can analyze it more thoroughly.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
I don't know if you guys already looked at this, but if this device is a Nova PVR-3001, then this post:
https://www.hifi-remote.com/forums/viewt ... 6796#p76796
looks like very similar "symptoms" to those you have here, especially this comment:
Interestingly, another part of that post seems to imply that the poster's OEM remote might have been UEI.Unfortunately, IR scope sometimes seems to understand the codes with some buttons (and show a nokia device with some extra codes..) but most times with the majority of the buttons it doesn't seem to work.
If you read down a couple of posts he adds more info: https://www.hifi-remote.com/forums/viewt ... 6805#p76805
in which he says:
Probably you've already seen/remembered that (Vicky and Rob were both involved in the threadXMP1.4 multiplayer asynchronous uni-directional protocol @ 38kHz.
-
alanrichey
- Expert
- Posts: 3533
- Joined: Mon Mar 24, 2008 7:14 am
- Location: UK/USA
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I thought we did, but Jim really nailed the thing with his post, so I have opened the old PVR fileAlanRichie wrote:Do you need some more learned signals from me ? if so what ?
Pvr learns from another thread
Hi Jimjimdunn wrote:
I don't know if you guys already looked at this, but if this device is a Nova PVR-3001, then this post: https://www.hifi-remote.com/forums/viewt ... 6796#p76796
looks like very similar "symptoms" to those you have here, especially this comment:Interestingly, another part of that post seems to imply that the poster's OEM remote might have been UEI.Unfortunately, IR scope sometimes seems to understand the codes with some buttons (and show a nokia device with some extra codes..) but most times with the majority of the buttons it doesn't seem to work.
If you read down a couple of posts he adds more info: https://www.hifi-remote.com/forums/viewt ... 6805#p76805
in which he says:Probably you've already seen/remembered that (Vicky and Rob were both involved in the threadXMP1.4 multiplayer asynchronous uni-directional protocol @ 38kHz.)- but I thought I'd mention it just in case it helps...
My participation in that thread was merely to have the user do the leg work and get the informtion into a form that we could use easier than a PCF file. PCF files are a royal pain for me because I have to reinstall ProntoNG every single time I use it. Something else I do on my PC seems to corrupt the installation between uses .
So I bit the bullet reinstalled prontoedit, opened the PCF file, imported the data into irscope and spit out a timing summary and a exported the pronto to a text file, see link above.
Interestingly I have been following the xmp conversations where we decided we could name ours xmp1 and xmp2 because we'd never see any of those other xmp formats here.
Last edited by vickyg2003 on Sun May 02, 2010 1:25 am, edited 1 time in total.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
I did try to read that discussion, but 99% of it went so far over my head you'd never even see the vapour trail...vickyg2003 wrote: Interestingly I have been following the xmp conversations where we decided we could name ours xmp1 and xmp2 because we'd never see any of those other xmp formats here.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
You are not alone there. I just keep reading and reading and hope it sinks in and I'll come to a aha moment. I got a handle on nokia last month so the hex isn't all that odd anymore.jimdunn wrote:I did try to read that discussion, but 99% of it went so far over my head you'd never even see the vapour trail...vickyg2003 wrote: Interestingly I have been following the xmp conversations where we decided we could name ours xmp1 and xmp2 because we'd never see any of those other xmp formats here.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
I looked at it this morning and think that this is a base 8 signal.
We suspect the leadin timing pair wrong.
Instead of 400,300 I tried 240,0 and got an extra data pair, but that was just to get the numbers to look better when rounding.
I then rounded to 80 and came up with 8 distinct timing pairs. I tried 40, but that gave me 9 distinct timing pairs, so 8 seemed like a better choice.
0=+160,-240
1=+160,-320
2=+160,-400
3=+160,-480
4=+160,-560
5=+160,-640
6=+160,-720
7=+170,-800
I then got this nonsense. But there were different frame endings which might be more of a clue to what is going on here.
11145570
10155570
05504
05545570
04555570
11104002
10114002
01504402
00514402
05414402
05414402
054
05545570
04555570
10104003
07114003
00504403
17514403
04104403
03114403
00504403
11145570
10155570
03504
11145570
10155570
02504
05545570
04555570
05104
05545570
04555570
04104
16445671
15455671
24114121
23124121
14414421
13424421
17114421
16124421
14414421
13424421
17114421
161244
11145570
10155570
0550401
12145771
11155771
We suspect the leadin timing pair wrong.
Instead of 400,300 I tried 240,0 and got an extra data pair, but that was just to get the numbers to look better when rounding.
I then rounded to 80 and came up with 8 distinct timing pairs. I tried 40, but that gave me 9 distinct timing pairs, so 8 seemed like a better choice.
0=+160,-240
1=+160,-320
2=+160,-400
3=+160,-480
4=+160,-560
5=+160,-640
6=+160,-720
7=+170,-800
I then got this nonsense. But there were different frame endings which might be more of a clue to what is going on here.
11145570
10155570
05504
05545570
04555570
11104002
10114002
01504402
00514402
05414402
05414402
054
05545570
04555570
10104003
07114003
00504403
17514403
04104403
03114403
00504403
11145570
10155570
03504
11145570
10155570
02504
05545570
04555570
05104
05545570
04555570
04104
16445671
15455671
24114121
23124121
14414421
13424421
17114421
16124421
14414421
13424421
17114421
161244
11145570
10155570
0550401
12145771
11155771
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Doh! I used my lookup tool for the NOVA and it looks like this could be cable/1559 or cable/1560. That would be bad news for slingbox users, since the protocol is going to be way to large to fit into the sling because of size limits. The protocol alone will be 500 bytes and then there is the device upgrade too.
I'd load it up and take a look, but I managed to get my widget curled around my leg, and when I got up and walked away I jerked it with enough force to pull all of the wires out of the USB end. I've got the wires stripped and ready to solder, but I've moved 2x since the last time I soldered and can't seem to locate it.
I'd load it up and take a look, but I managed to get my widget curled around my leg, and when I got up and walked away I jerked it with enough force to pull all of the wires out of the USB end. I've got the wires stripped and ready to solder, but I've moved 2x since the last time I soldered and can't seem to locate it.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Could somebody with a widget anod one of these remotes; urc-7555, urc-7780, urc-7781, urc-7940 or urc-7750 setup SAT/1560 and take a picture of the number 5 so we can confirm that this is that xmp1.4 signal?
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Here are .ict files for key 5 from SAT/1559 and SAT/1560 devices. The two signals seem to be similar but not identical. Neither DecodeIR nor the new ExchangeIR analysis can make anything of them!
_______________
Graham
_______________
Graham
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Thanks Graham, that helped a lot. This is the same signal structure that we saw from the other sources. This would be the xmp1.4 4 player signal. The protocol is absolutely huge and I see no way to get this down to a size that can be loaded into a sling box.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
I haven't been following this thread, but since Vicky prodded me for a .ict file, I've had a look to see if I can make sense of it. I feel that Vicky is wrong on the base 8 issue. I think it is better not to round, but to look at the raw timings. There is no logical reason why the timings are multiples of a common figure, and indeed in the XMP protocol itself they don't seem to be, they seem to be multiples with an offset. The best sense I can make is that there are four values within each range of 100us, at x13, x40, x67 and x90 microseconds, where x is a digit from 2 to 7 or 8. I'm not sure what the lowest and highest gap sizes seem to be. These figures are very close to uniform intervals of 25 us, but with an offset. However, if I am right then this isn't base 8, or even base 16 (like the ordinary XMP). It would mean at least 20 different values, depending on what the range ends really are, and I can't believe a base 32 protocolvickyg2003 wrote:I looked at it this morning and think that this is a base 8 signal.
I will watch further developments in this thread with interest!
______________
Graham
I am very appreciative of all the effort by all the expert within the forum that have been working on a solution for a bin file for Nova pvr 3001. The box I am attempting to control is for the Greek pay-tv operator NOVA in front of the box the label is Nova pvr 3001 , underneath the box its labeled Panasat pvr 3001 if that helps. I have also tried http://betaremotes.slingbox.com/ with no success