AQL-PS-8 Remote Emulator App

It sounds like it could be that the controller is not recognizing the default key commands. When I read through the forum comments, I could not find a reference that they are different but I may missed it:


They don't seem to use different logic for either controller so something else might be going on.

The other possibility is that the timing in the controller could be different but again, no one has mentioned that in any of the other posts.

Are you are only trying the keys that are supported in the PS4? Only the Filter, Lights and first 2 Aux keys will work with the PS4 main relays.


If you feel comfortable with using the EW11 tools, I can step you through a process to capture some of the key strokes.

In the troubleshoot section in this document:


It explains how to setup TCPUDPDbg to capture data from the controller. However, in this case, you would select "ShowHex".

View attachment 568422
First, use the main controller display to press a couple of key strokes. Capture and save the hex values into a separate file.

Next, use the app to do exactly the same order of key strokes. Again save hex values into a separate file.

Post both files letting me know which is which and maybe I can figure out what may be going on.

Thanks.
Thanks much!

before I checked the 'showHex' box, I see the display info, afterwards - lots of HEX that I'm not quite following.

I performed a sequence of Filter on, lights on, aux2 on -- aux2 off, lights off, filter off. First file via main control, second via app.

If I read the decoding done on the desert-home post correctly, I can find the 80 00 00 00 string in the capture from the main control, but don't see it from the app routine.
 

Attachments

  • filter lights aux2.txt
    4 KB · Views: 2
  • filter lights aux2_app.txt
    2.1 KB · Views: 2
Last edited:
Did you try to reload the script?
I have, and also exported the script and confirmed it is the same as the load.

Flipped my A/B wires around to confirm that wasn't it - the TCP monitor on that then went to complete ASCII character mess and the emulator would not show the display info, so reverted to what I had done on wiring. It is puzzling, wonder if there is some latency issue where the signal isn't getting sent or not getting through.
 
Last edited:
The files you posted are not in hex mode.
sorry - I wasn't sure how to save them so I added a .txt. Is this better?

Edit - I may have a P4 versus a PS4. I had only pulled the pcb board part number and know I only have 2 aux switches, but the control interface box does look like the p4 version. That might be my issue, seems I read it takes a few more characters or may not work at all
 

Attachments

  • filter lights aux hex1.zip
    3.7 KB · Views: 2
Last edited:
sorry - I wasn't sure how to save them so I added a .txt. Is this better?

Edit - I may have a P4 versus a PS4. I had only pulled the pcb board part number and know I only have 2 aux switches, but the control interface box does look like the p4 version. That might be my issue, seems I read it takes a few more characters or may not work at all
Thanks, that gives me a direction to look into. If you find any info on the P4, please forward it to me.
 
I think I know what might be going on here and yes, it has to do with the control unit being a P4.

Do you also have a wireless remote or a wired remote? Can you do the same key sequence with another file using the remote. Thanks
 
Sorry, I don't have any other remotes. I did copy over and divide the hex out by the start and end codes that I read. Perhaps this helps.

Let me keep looking for where I saw the reference, believe it was part of the home assistant boards for the integration and others that had some similar issues.
 

Attachments

  • hex transmission.pdf
    76.5 KB · Views: 1

Enjoying this content?

Support TFP with a donation.

Give Support
No worries, I think I have a solution anyway that you can try out. Can you use a Windows version first? Hopefully it will be published to the Windows Store soon.

There is a new setting on the settings tab call "P4 Mode" and you will want to check that.

If this works, then I can publish the iOS and Android version. It just may take a day or two.

Windows Version
 
Certainly happy to try whichever, at least for testing purposes. Currently, I get an error on the Windows Version link you posted, but will try again in a bit to see it is live.
It may take until tomorrow to show up. It is currently under review and there could also be a rejection which would delay it further.
 
Try the windows store and search for the app.

I had the same issue with the link. Not sure why.
Troubleshooting success again! I checked the P4 mode box in settings, and am getting the display text coming over. Turning on the filter on the local panel sends the signal that the pump is on, and the Filter button goes bold. I cannot seem to get the windows app to accept input either. Basically same response as my phone - iOS app.

I played around with seeing if I could send a string at it from the TCP monitor, either I didn't get that right - or it would not accept transmission either.

Rechecked the EW11 setup and all seems to match.
 
  • Like
Reactions: mas985
It should be sending the same codes as what the local controller does. The only thing I can think of is the timing is different with that controller.
 

Enjoying this content?

Support TFP with a donation.

Give Support