I have been using SB for a few years now to control my EasyDaq relay boards. Since it runs on Rosetta which may not make it into the next OSX version, I thought it time to see if I could find a replacement and I did with SerialPortX. It allows me to read and write to the EasyDaq board using Applescript.

It is basically an Applescripting Addition to extend Applescripts capabilities. I dropped the osax file into ~/Library/ScriptingAdditions, modified my original SB applescript for SerialPortX and bingo I'm in business.

Available free at http://mysite.verizon.net/vzenuoqe/MacSoft.html

bob

Excellent news - I knew v1.1 had some issues, glad to see they were apparently addressed in v2.0.

Is the latest version 10.6 compatible? You might want to check the console log to see it it is throwing any errors.

I found SB to be more reliable over time then SPX.

I fixed an error I made in my Applescript and now it's working like a charm. I've been using it for a couple of weeks now and the only problem is the one I induced myself. It's running a 24 relay board and a wireless 8 relay board with up to 100 relay cycles/Indigo applescript actions per day.

I am using BTW, the latest version for SL.

bob

Just an update on Serialport X; a few changes to the script and it has been running 100%. I have come up with a script that in the event of a power failure/reboot the script will assign the correct USB port number to my relay board. Previously if the USB port number changed I had to set it manually as you have to do in Serial Bridge.

Soon OS X will not support Rosetta and Serialport X has been the answer for me.

bob

I tried to get it to work with my Jandy. Cannot communicate.


serialport open "/dev/cu.usbserial"
serialport write "&pump?" & return to "/dev/cu.usbserial"
set x to serialport bytes available "/dev/cu.usbserial"
serialport close "/dev/cu.usbserial"


Gers no data from Jandy. Read is 0 bytes

I'm not of an AppleScript expert to understand WHY this is, but you have to assign the open serialport to a name, and then refer to it that way.

Try something like this:

Code: Select all

Set JandyDevice to "/dev/cu.usbserial"
Set Jandy to serialport open JandyDevice
serialport write "&pump?" & return to Jandy
set x to serialport read Jandy
serialport close Jandy

On another note... I'm trying to psyche myself up to do a Pentair Plugin for Indigo 5. This looks like the exact same syntax my Pentair setup uses. By any chance are they the same? Maybe someone else is doing a plugin for Jandy which I can use on my Pentair. Does anyone have a link to Jandy's RS232 protocol?

You need to list the actual USB port number like this;

Code: Select all

set JandyDevice to "/dev/cu.usbserial-A7006BBo"

The USB port number can be found at /Dev

Actually the "/dev/cu.usbserial" is the identifier for my USB/serial adaptor. This is one of the choices on SerialPortX list.

I now have SerialportX working with 10.7 to control my Jandy. Will post revisions to Jandy attachment

I have managed to get SPX working with my KeySpan USB/Serial converter. That's the good news. The bad: the DSC 4401 interface I've been using successfully for years (Serial Bridge ->KeySpan ->DSC 4401) signals my main DSC alarm system if the port the 4401 is attached to isn't "open" on the KeySpan. With Serial Bridge, just having the "connection" document for that port open was fine. But, using SPX, I can't seem to get the 4401 to believe it is "connected", with the result that my main alarm signals a "trouble" event with an annoying beep every 10 seconds. I realize this is a specialized circumstance, but any ideas would be appreciated. Thanks.

Just shooting from the hip, but could it be a CTS/DTR issue?

HFTobeason wrote:I have managed to get SPX working with my KeySpan USB/Serial converter. That's the good news. The bad: the DSC 4401 interface I've been using successfully for years (Serial Bridge ->KeySpan ->DSC 4401) signals my main DSC alarm system if the port the 4401 is attached to isn't "open" on the KeySpan. With Serial Bridge, just having the "connection" document for that port open was fine. But, using SPX, I can't seem to get the 4401 to believe it is "connected", with the result that my main alarm signals a "trouble" event with an annoying beep every 10 seconds. I realize this is a specialized circumstance, but any ideas would be appreciated. Thanks.

If I had any idea what CTS/DTR meant, I might be able to respond appropriately!

HFTobeason wrote:If I had any idea what CTS/DTR meant, I might be able to respond appropriately!

Its a handshaking deal for serial port stuff.
Everything the same hardware-wise, just changed from SB to SPX? (been a long time since I played with SPX, I found it unreliable)