Caller ID would be nice, but haven't figured that one out yet.
Thanks. Sounds like a good project but might be a bit over my free-time availability at the moment. I know pete_c has been working on similar devices.BobS0327 said:Have you considered using one of the single board computers such as the Arduino or RPI as a solution? Here's a link to a project to implement caller id on a SBC.
https://blog.adafruit.com/2014/06/09/make-a-large-homebrew-led-display-for-network-caller-id/
You can also use a open source Java library called JOmniLink on a SBC computer such as the Raspberry Pi to establish communications between the OP2 and RPI. Thus, the RPI can receive OP2 notifications and control your display based upon the received notifications.
The RPI 2 has a wired ethernet connection but a wifi attachment can also be purchased for it.
So, to recap, your OP2 communications and caller id problems can be solved with a SBC.
Yes, it is working in a wired state.pete_c said:I have a Betabrite sign powered by my Omni Pro II which I want to move, but probably can't run wires.
if you have this already set up; then just put wireless RS-232 to replace the wires. I am assuming you already have all of the rest of the pieces already in use and going. Putting in the RS-232 wireless isn't going to change anything really.
Is it just using 3 wires for the Pro-Link versus Omni-Link protocals stuff (versus 6 wires (with voltage).
As per the OP, one end is connected to an Omni Pro II and the other end to the BetaBrite sign. It's not connected to a Windows/linux/mac device, so a set would be required.znelbok said:But do you need one on each end? The OS will use a driver and create a virtual serial port so only one physical unit is required
You are correct sir.Sparkman1 said:As per the OP, one end is connected to an Omni Pro II and the other end to the BetaBrite sign. It's not connected to a Windows/linux/mac device, so a set would be required.
Cheers
Al