beta net2hipsend

[steve232]

Still having the problem with sending zero's.

It seems that in the hipuirt file, a zero is stored as '10'.

Not sure what happens to that 10 when it is parsed through your tool.

The file is attached.

Steve

[pBS]

0 ends up being a 10...so in net2hipsend, i translate 0's to 10's and send to hip..
so however you made those others right, make the 0 a 10.001 as i don't think hip understands a 0.001..

glad you got it working, what happened? just wondering if there's something different about how other blasters are setup, cuz i *can* use the name label instead of the numbers to talk to hip, eliminating this sort of thing..
[telling hip to blast by the 'label' name instead of digits..eg. "one two three"]

[steve232]

OK I have the usbuirt blasting from the built in sender.

What I had problems with, the web page.

http://127.0.0.1:8084/index.htm works.

http://localhost:8084/index.htm and http://192.168.150.120:8084/index.htm doesn't.

As noted above the learned codes were all messed up. I edited the ini file.

Same for the 0/10 issue.

Next is to get the remote ir transmitters working.

Am I correct that you look at the .001 to determine which blaster?
So .002 and .003 should tell hip to send the codes to the different remote blasters.

Steve

[pBS]

close...the .001 is the set of stb codes..so you could blast to more than one stb with same blaster eye..or same stb with different eye..
for 2 same stb's, you'd have .001 for stb#1-eye1 and .002 for stb#2-eye2 even if same stb ir codes..
only 2 blaster eyes, so .003 would have to be different set of stb ir codes..either eye1, 2 or both..
so the .001 suffix is really only the stb ir codeset #. Which eye they blast to is built-into the codeset..

blaster selection is done when you learn codes..on right side, you'll notice ir blaster 1, ir blaster 2 or both as selections in 'edit ir cmds' screen..select there which eye you want to blast to...
then make a new set of same codes and restrict to other eye and label it .002
[you can copy the codes instead of learning again]
so blasting 123 to eye #2 would be 1.002 2.002 3.002
same to eye #1 = 1.001 2.001 etc..
have another type of stb to add? make that 003
the suffix is just the set of blast codes..which eye they go to is built in when they're learned..
[tho can be edited after to change just eye port]

what did your edit ir cmds screen look like? did you select the label and name on right side? was there a name there on right under "label"?
trying to figure out why they are different for you..
if they are, i'll look into using the proper 'name's of the remotes and keys instead of numbers..to prevent this happening again..

[steve232]

Attached is a open office screen shot of the remote learning.

Still get the strange numbers.

The goal is to get 2 dish boxes off the usbuirt.

Not luck yet getting the remote blaster working yet. Even the red led on the blasted doesn't light.

I won't have a lot of time for the next couple of weeks as I heading south to fine some warm weather for R&R.

Steve

[pBS]

hmm, not seeing any attachment...
just use printscreen key and paste it into any image program to save it as a jpg..[even ms paint will do]
crop it to relevant parts or zip it up and attach zip, as forum only accepts jpg's under a certain size..
[much smaller than whole screen size]
that screen should give me clues as to what's happening..select 1 of the numbers when taking screen shot..

so nothing lights up when testing from hip interface after learning?
or just with net2hipsend? i'm not sure the usbuirt has visible response, they don't have to, to work..[it *is* infrared which humans can't see]
you can point a digital camera to see if it's blasting anything..it shows bright red in digital cam viewfinder even if invisible to naked eye..

i have same stb box but i think my mce codes are different than what you send with uirt..

btw, pretty nippy here right now...raining and cold..[upper 40's ha]
tho it was like 70 earlier and sunny..
local saying, if ya don't like the weather here, just wait a few minutes..

[steve232]

I see the file didn't attach, I'll send it tonight.

I've been using a digital camera to see what sensor is lighting up.
The usb-uirt also has a red visible led that lights up when sending to any of the 3 outputs. At least I think it does when I was using the gbpvr changer.

But gb seems to drop the connection to the uirt so often, that is why I'll looking for a different changer.

Steve

[steve232]

I think the files, one old ms word format, the other in open office are attached.

Do all the channels .001, .002, .003 need to be listed under the same remote?

Or do you scan through all remotes?

The reason I ask, is the tool won't let you save the same channel number, even with a different .00x under the same remote name.

Steve

[pBS]

nope, there should be one remote per set of 0-9 codes...
looks like you're almost there..i see how your screen is different..

looks like i'll have to go with using the names instead of numbers to signal hip..shouldn't be too hard..as those numbers it generates are way long and don't seem to follow any logic..
then as long as the 'button' and 'label' are #0 - #9 then it won't matter what the codes are..

check back later today and i'll see if i can't get something working for you..

[pBS]

well i've got a new one ready for testing..it uses the remote name instead of digits..
only problem is, i haven't tested it here and i'm recording so can't for a bit..
i'll upload it as soon as i confirm it's working decently..
then you should be good to blast if your blast codes work..

ahh, after testing and a couple adjustments, working great now..

this takes arguments in any order, all the rest same except remote= where you now must use the remote's "short_name" when referring to it, and there's no default remote name because of this..
oh and you *must* label the ir blast codes "#0" thru "#9" [can't be just 0-9,needs the # in there to differentiate from normal num keys]
what their filenames are, and what code numbers they are [like ###.###] won't matter anymore..
all remotes should have #0-#9 [optionally an "ENTER" code] so we can blast to any digit on any remote name..

So a typical cmdline blast line would look like ' net2hipsend.exe 144 remote=REMOTE_NAME '
and for config: select net2hipsend for .exe changer, use " {channel} remote=REMOTE_NAME" for params...

channel# must always be first, the rest in any order, same defaults apply as before..
let me know if it works for you, but make sure blast codes work within HIP first..