-
|
When I get everything connected and power up aqualinkd, it will read the config and start the daemon. Then aqualink immediately shuts down, as soon as I unplug the aqualinkd device it immediately comes back online. I get nothing in the log, last thing posted is the clock sync. Then it is dead in the water, all pool equipment powers down until it is unplugged. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 10 replies
-
|
Sounds like AqualinkD and Aqualink are using the same ID. Did you run serial-logger to check what IDs are free/being used? (And make sure aqualink wasnt asleep when doing that) |
Beta Was this translation helpful? Give feedback.
-
|
I will try the serial-logger, if I stop aqualinkd before connecting I should be able to execute it. As it seems stable as long as not connected to aqualink. |
Beta Was this translation helpful? Give feedback.
-
|
You can't run serial-logger and aqualinkd at the same time, since they both need access to the USBRS485 converter. By aqualink, I am assuming you are talking about Jandy's Aqualink interfaces (like iAqualink or Aqualink Onetouch etc) |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I meant before connecting the serial interface to the jandy panel. It crashes so fast I wouldn’t have to connect and then stop the service. But I should be able power up, stop the service and then run the serial logger. |
Beta Was this translation helpful? Give feedback.
-
|
So serial_logger just hangs without returning anything so something must be wrong with my serial port connection. Need to look deeper at that. |
Beta Was this translation helpful? Give feedback.
-
|
Re-did my serial connection and successfully tested it with a loopback. I changed the ID to 0x00b, aqualinkd doesn't crash immediately. However, the jandy panel still powers down a minute or so after serial connection. I did verify my wiring is correct. Once I disconnect the serial connection, the jandy panel immediately returns and all equipment is back operational. Serial_logger just hangs at reading information. I am kind of out of ideas. |
Beta Was this translation helpful? Give feedback.
-
|
In your first post, I thought you were saying that AqualinkD was working correctly, but a Jandy interface was shutting down when running. From your last reply that can't be the case that AqualinkD is running correctly. So my initial comments wouldn't help. From your last reply, it sounds like the candy control panel is shutting down? If that's the case, your wiring can't be correct. Let's go back to the basics. This message You mention testing wiring by a "loop back", what do you mean by that, to my knolage a loop back test is serial only, and you have a USB2RS485 adapter (no serial pins you can actually access). |
Beta Was this translation helpful? Give feedback.
-
|
I've tried both, pins and the RS4852USB. Both will show as devices and I can test them. However, once connected to the jandy panel, the panel will shutdown. I rechecked the wiring today and everything looks good including re-wiring and removing some devices to slim down the channel as much as possible. The initial test for the USB device is: goldfish@AqualinkD:~$ sudo -s eval 'stty raw -echo < /dev/ttyUSB0; cat -vte /dev /ttyUSB0' The echo command does nothing, similar to the serial_logger. This behavior is the same with pins and the adapter. I might just start over and rebuild and instead of trying to throw different things at it. |
Beta Was this translation helpful? Give feedback.
-
|
If the command I'd suggest wiring the adapter in to the RS485 bus WITHOUT any power (ie don't connect it to the raspberry pi), as just use data+/- lines no others. If the control panel is still working, then connect it to the raspberry Pi (without AqualinkD running), and check control panel again, as that should power up the adapter. If either of those fail, it's either wiring or a bad adapter. If they work, then try the BTW, what USB2RS485 adapter are you using? |
Beta Was this translation helpful? Give feedback.
-
|
It is the FTDI one linked in the wiki. I will get that test a try. It has to be something simple just haven’t been able to narrow down. |
Beta Was this translation helpful? Give feedback.
-
|
On that adapter, you should only have 2 wires connected to the RS485 buss and all other wires left exposed (not touching anything) for the initial test/setup. |
Beta Was this translation helpful? Give feedback.
-
|
Finally got something: Jul 28 14:57:58 aqualinkd aqualinkd[651]: AqualinkD: Aqualink daemon looks like serial error, resetting. Assumption is the checksums are the result of a wiring issue. But progress none the less. Serial logger output:
|
Beta Was this translation helpful? Give feedback.
-
|
It was the wiring. I started over and examined the wire and notice that the Data+ wire was actually broken in the sleeve. So the connect was intermittent and the large number of checksum errors going back forth would cause the panel to shut down. Once the FTDI connector was removed the panel would come right back online. |
Beta Was this translation helpful? Give feedback.
In your first post, I thought you were saying that AqualinkD was working correctly, but a Jandy interface was shutting down when running. From your last reply that can't be the case that AqualinkD is running correctly. So my initial comments wouldn't help.
From your last reply, it sounds like the candy control panel is shutting down? If that's the case, your wiring can't be correct. Let's go back to the basics.
You have a Jandy RS control panel?
You are using a RS4852USB serial interface?
On RS4852USB interface, you are ONLY connecting 2 wires, (Data+ and Data-) to the RS control panel?
This message
RS Serial: Didn't find valid blocking serial port file descriptermeans aqualinkd did NOT …