Hello
I have a zodiac pump which uses the Jandy rs485 protocol.
I want to throw away the controller and control the VSP pump directly from a home automation system and read back the RPM and power.
There are heaps of old threads on this topic refering to the Jandy pump protocol which someone reverse engineered and created a PDF for, but all the links to this document are dead.
I found a couple of bits of code which refer to a 'set demand' message and a 'go' message and using this I can start and stop the pump at full speed.
send motor the "set demand" command in Jandy format
10 02 78 44 00 10 00 27 05 10 03 - Jandy command
10 02 00 1F 44 00 10 27 00 AC 10 03 - Motor responds!!!
then
10 02 78 41 CB 10 03 - go command
10 02 00 01 41 00 54 10 03 - motor's response and motor starts!!!!
This works great
But what I really need is to find the document or some code which explains what each byte is for so that I can send a customized demand request and calculate the correct CRC to tag on the end of the message.
I am sure someone has this document lying around and could upload it or may be has some code running in their own system so we can keep links to this information alive and people can continue to develop their own solutions without having to reverse engineer the protocol every time.
Cheers
I have a zodiac pump which uses the Jandy rs485 protocol.
I want to throw away the controller and control the VSP pump directly from a home automation system and read back the RPM and power.
There are heaps of old threads on this topic refering to the Jandy pump protocol which someone reverse engineered and created a PDF for, but all the links to this document are dead.
I found a couple of bits of code which refer to a 'set demand' message and a 'go' message and using this I can start and stop the pump at full speed.
send motor the "set demand" command in Jandy format
10 02 78 44 00 10 00 27 05 10 03 - Jandy command
10 02 00 1F 44 00 10 27 00 AC 10 03 - Motor responds!!!
then
10 02 78 41 CB 10 03 - go command
10 02 00 01 41 00 54 10 03 - motor's response and motor starts!!!!
This works great
But what I really need is to find the document or some code which explains what each byte is for so that I can send a customized demand request and calculate the correct CRC to tag on the end of the message.
I am sure someone has this document lying around and could upload it or may be has some code running in their own system so we can keep links to this information alive and people can continue to develop their own solutions without having to reverse engineer the protocol every time.
Cheers