Vgreen 270 Automation with Jandy Aqualink?

Jump to latest Follow Reply
S

sihey11

Member
Apr 9, 2022
5
Los Angeles
Good day. Wanting to see if anyone has had any success getting their Vgreen 270 to work directly with their Jandy Aqualink? Thanks to @MSchutzer's great work here, I have been able to work out how to get my pump to respond to various commands from a laptop but haven't made any progress getting the pump to talk in the Jandy protocol. The previous successes seem to be on the Vgreen 165 model which one would think is the same as the 270 but does not seem to be. Before I go and drop $200 on a he automation adapter thought I would ask around.

Thanks!
Simon
 
Simon,

Were you able to find the protocol variable and update it? We’re you able to save the flash configuration and then read back that variable and verify it changed?

The thing that switched the modes between the modbus and Jandy command set was a DIP switch position on the Vgreen165.

Does the Vgreen270 have any dip switches on it? Have you searched the manuals for Jandy 2.7 HP epump? Try and find one that matches the motor that you have, it may be an older model as the Vgreen motors came out several years ago.

I know I was initially disappointed when I changed that protocol variable and nothing happened at first. It was only after I found the Jandy Epump manual and set the DIP switches how they had them did it wor.

There might be something like that on the Vgreen270 also?

Good luck,

Mark
 
Yes the 270 has 4 rather than 5 dip switches but as you say I was able to work out the correct (hopefully!) positions from a Jandy epump manual.

The issue I have run into is that I’m unable to read or write to the config address that has the pump protocol variable. The address (Configuration page 10, address 0x05) responds back with an error message “out of allowed range”. I can read other config pages which perhaps suggests the 270 doesnt have the protocol in the same address
 
That’s a bummer, are you sure you are sending hex address values? Are you using the same terminal program that I used, or are you using something different? That terminal program has a weird format for sending hex values as you need to use a macro, and then you need to add a $ symbol in front of the value that you want to send.

I’m kind of surprised it’s different as that modbus document talks about motors up to 2.7 HP.

Were you sending the same command strings that I had listed in my earlier posts?

Mark
 
I’m using same terminal program as you. I can get the motor to spin up with various commands so confident I got it wired right and the fact that I get an error response rather than no response says that I got the checksum etc correct. I was surprised too that it’s different as I can read the config and see that it’s a 2.7 motor. Perhaps they got wise and changed the addresses. It’s brand new motor
 
While it’s a long shot have you tried changing the positions of DIP switches 1 and 2 to see if it might work without having to change the configuration variable?


Page 13 of the JandyVS Flopro manual indicates that switches 1 and 2 should be off to talk to any of the Jandy automation systems.

If that configuration variable isn’t there maybe the support for the Jandy protocol is already built in. Like a said a long shot, but that’s all I can think of. They could have also just changed the firmware?
 
You must log in or register to reply here.
Thread Status
Hello , This thread has been inactive for over 60 days. New postings here are unlikely to be seen or responded to by other members. For better visibility, consider Starting A New Thread.
Top Bottom
Back
Jump to latest Follow Reply