Good day.

I downloaded the Escient DVDM-100 code from Escient, and inserted into my profile. The power code is NOT discrete. When I hit the "test" button in a stand alone "power on" or "power off" scenario, it always works. However, when I add either to a macro, only "power off" will work. I can NOT get power on to work from within a macro. I tried to add the power on several times in a row, (assuming this would = holding the power button down) even added delays for and aft, and it still will not power up from the macro. Power off works fine... Any ideas? Thanks!!!

MX-700 oem'ed from parasound......

Not sure what the problem is but I've encountered it with some codes also. The discretes for my Pioneer DVD player and my JVC VCR exhibit the same behavior. The on and off codes work fine when initiated from a button containing nothing else but when put into a macro (even one with nothing additional except a delay) they don't work. What's interesting is that the codes exhibiting this behavior are from the database for the MX-3000 but I also have the same codes generated by entering hex data in a Pronto ccf file and then imported through the universal browser and they work without a problem. It seems as though only pre-programmed codes have this problem and it only happens with some as the discretes for my Pioneer TV and receiver work correctly.

Bob

Just for grins, try a .10 second delay before and after the discrete, or try only the discrete command in a macro and see if a 1 step macro works.

Yes, unfortunately, I've tried several different delays, all to no avail...... Not sure if this matters, but its not discrete. Same code for on and off...... What I've noticed, is that it "appears" that when I test the buttons "individually" they "spray" longer. When I put them in a macro, they FLY by.....

Same problem for me using a power on discrete for a Pioneer PDP-50A5HD.

Same problem same unit however it was intermittent so I put the code in multiple times in multiple places and surrounded them with delays, " yes it was a very ugly macro".

dbryant11 are you using the mxeditor, or are you using the parasound editor? the reason why I ask, is that even though both editors and files are interchangable, the power buttons are on the opposite side of each other...ex...on an mx-700/800/850 the "on" button is on the left, and on the parasound button it is on the right...so if you were to go about programming the parasound remote using the mxeditor that was intended for the mx-700 you would have some issues with power commands...no matter what left or right side of either remote, if you put the power on command on the left side...well that is power on, but if you look at the parasound remote...well it is really the off button... I have programmed both the 700 and the parasound remote to control escient gear and have not had a problem, and they do have discrete codes...I hope this helps.

also, if what I have written above is of no use, then move the escient command to the beginning of the macro and give it a try, some device commands will interfere with other devices and cause a macro string to not perform properly.

have you tried to download the codes into the remote instead of using test. I ran into a very wierd situation last week with a mx700 where very few of the codes worked with test but worked 100% when downloaded. Its was strange. I was 100% certain the codes worked because I was using a template from another job that was virtually identical. Pissed away an hour and raised my blood pressure about 200 points but everything was fine at the finish line. I wonder if it was the new editor update? Hmmmm

If both codes are working by themselves, but not in a macro, and it's a toggle anyway...just use the command in the macro that works, or create a shortcut to the functional command from the non-functional.

Let me know if that works.



Thank you,
Damon DG
= = = = =
http://www.ProRemotes.com - Authorized Dealer & Remote Programming Services