On Tue, Mar 14, 2023 at 04:57 PM, XSDS wrote:

kind of defeats the purpose of AES67

But even using Autonomic (or outboard Sonos players, etc.) this is still a very handy function - eliminates the gobs of loop-thru jumpers and allows for de-centralized units to share all the sources...

+1 for Autonomic now that they have the AMB to add Apple Music, etc. - and hopefully they're resolve the MMS HW failure issues that they've had in the past...

As an aside, I'm a fan of using multiple MMS-1e units (ex: one for each user), which among other benefits, eliminates the single-chassis failure issue. if you loose one, you still have the others to keep you going...

On Tue, Mar 14, 2023 at 04:12 PM, Corbin Lovering wrote:

.. the IEC power cable was UNPLUGGED.?

Yeah, we've all had stuff like that happen!!...:)

Honestly we have run into so many issues with the NAX's that we just stopped using their native streams and include an Autonomic in the package.? Sure, kind of defeats the purpose of AES67 built in, but the headaches it was causing because insurmountable.? We will utilize them for NVX systems, but as far as audio streaming, we use all external inputs now.

Hi Jonathan,

Thanks for responding.
I must admit, I've not been setting the port in my simpl logic, although I may give that a go.

FYI, we are using Ruckus throughout with the exception of a temporary Draytek router that will be replaced with a BT Openreach fibre router shortly.

Regards
slip

Slip,

I'm not sure this is the same issue, but close enough to mention. We have had issues on one site where NAX streams will not start. We're using Auto Initiation and if you look at the web UI, NAX Streams/Receivers the Status just says "Connecting" and never changes for the offending zone. Unlike your description, when I've had one of the NAX units in this state, stopping and restarting the stream does not typically make a difference. A reboot typically brings it back at least for a while.

We've worked with TB, ATSG, and Pakedge pretty extensively. I thought we had worked this out by not sending the port analog (5004). It does not seem necessary to send the port. That much does seem to be true, but as the problem and solution for our situation, it doesn't seem to be the case. We just recently discovered the site is still having issues.

At this point, we feel our problem is network related and are planning on replacing the Pakedge switches we've been using with Ruckus.

In your setup, I'd be curious what happened if you turned Auto Initiation On and just sent the multicast address without the port. Like I said, might be a different issue all together, but thought I'd mention it.

Regards,
Jonathan

开云体育

One thing I can offer that may help you is my old programming template that is up on my GitHub.? At this point certain aspects of it, like the hardware that is being controlled, is very out of date (I haven't touched this code in over 7 years).? However, the programming structure is still very sound and will introduce some different concepts to you.?

1) Cross points are embedded inside many of the modules and take care of handling multiple rooms, multiple control devices (tp's and remotes), and multiple sources.? Most people use buffers when they first start programming for this and then move on to cross points as they take some of the more advanced Crestron programming classes

2) Instead of having digital signals running all over the program to handle device and room selections the code leverages a much smaller number of serial signals with commands sent down these serial links.?

3) Since the code was designed as a template, it has a ton of hardware embedded into it.? The idea being that for any given project it is much quicker to delete code that isn't required for a given project than to write new code for that project.

Enjoy

Jay

That document has what you need, but it has way more than what you need for basic messages. I've had good and easy luck with the 1-byte command format (baud rate is automatically determined, so I just use 9600 cause the signs we use - the 215C - support that).

My protocol notes:

• At least 5 null bytes to establish baud rate \x00\x00\x00\x00\x00
• SOH \x01
• Sign type code, use "Z" for all sign types
• Sign address, use "00" for all signs
• STX \x02
• Command code ("A" for write text, "B" for read text)
• File label ("A" through "Z", or "0" for priority)
• ESC (start mode field) \x1B
• Display position " " (\x20) for centered (page 18)
• Mode code "b" for HOLD mode, stationary message (page 89)
• Set color \x1C (page 82)
• Color
  • "1" Red
  • "2" Green
  • "3" Amber
  • "4" Dim red
  • "5" Dim green
• Message in ASCII characters
• EOT \x04

I have more notes and a basic module I developed that I can share with you if you want. One thing to keep in mind, you can read and write to multiple "files" on the device. I usually just use one of them since I'm sending it custom text. But if you or someone else writes to the "priority" file, then that's the only thing that will display until that file is cleared, no matter what else you write to any other file. So, use this command to clear the priority file on all signs: \x00\x00\x00\x00\x00\x01Z00\x02A0\x04. Your specific example should be \x00\x00\x00\x00\x00\x01Z00\x02AA\x1b b\x1c2hello world\x04.

You guys are the best for sure thanks so much. On a newbie side note I'm sitting at my desk using these tips and control works as intended but there was no feedback. So, after a lot of redoing, commenting out symbols I determined there was no way it wasn't working. I looked at the crestnet wiring-- looked good. Looked into the network tree in toolbox and wasn't finding it. Come to find out.. the IEC power cable was UNPLUGGED.?

I've been an RTI "programmer" for 2 years with this company and been an tech for 6 before that, I know being 27 hasn't had anything to do with it... It's always the simplest things..

Great Share ??

Welcome to the Crestron programming world!!!? and?What Olivier said!...

Also, I created this document years ago to help me remember the various behaviors of the SBUF and ABUF. I think it will be helpful going forward as you increase your knowledge and experience...
/g/crestron/files/ABUF+SBUF%20Test%20Behavior.docx

Does any of this matter if VC-4 has the offline dongle for activation? Seems to me USB LAN should be plug and play (don't care about CS like experience.?

I'm trying to figure out how to send a message to a tri color Alpha America sign.

I found a protocol manual from 2006 that goes into modes and text positions, but it doesn't mention how to set the color of the text. Does anyone have an example of how to send a basic message like hello world in green text on a tri color sign?

开云体育

Add ch processor and then import signals from

The script was pulled due to some issues with it, but VC-4 still does support dual NICs by creating the adapter.conf file in VC-4's conf directory and populating the file with the name of the NIC that you want VC-4 to use to reach out to XiO then restart the virtualcontrol service. There are also issues with using dual NICs where the OS will use the wrong NIC to send data to which will override VC-4's settings, but this can be fixed with a couple changes using NMCLI's interactive editor to set the USB-Ethernet NIC to never be the default for IPv4 and IPv6 communication.

The analog buffer will propagate value from input to output when enabled, the serial will not.
When you use buffers for feeding multiple room volumes from a single control/ramp, you want to use an Abuf for feedback, but a Sbuf for control.

It's a common mistake for beginners to assume Sbuf and Abuf are made for Analogs and Serial signals respectively, but in fact they are interchangeable and have different behaviours.

It does get confused on which NIC to use to "phone home". Definitely a problem when licensing with XiO Cloud. Pretty easy to fix with a couple of Linux commands though. You just need to change the metric number of the NIC so that the "phone home" NIC has a lower metric number, aka is used first.?

I have set up 6 systems in the last month or so with dual NICs and not using the script. They all seem to be behaving. I've found you have to make sure you run updates in the correct order but otherwise not too many issues.?

开云体育

Personally, I would not use a slider and just a gauge for feedback.? To answer you question, look at the difference between an analog and serial buffer.? You need both in this case.??

We set up a large resi system in our factory last year and as some of you may recall I was very happy with NAX.

Now the system is on site (very much a building site still) we have frequent power outages and still no AC in the AV Room.

Each night we power down the AV system down to avoid overheating when we lock the door.
Not something I'm happy about but this has exposed a few NAX issues.

The main one I'm trying to deal with but don't seem to have found a totally reliable solution is stream?initiation and getting the streams to start.

Source requirements are pretty basic:
5 X Sonos. 2 physically connected to one DM-NAX-8ZSA digital inputs, 3 connected to a second?DM-NAX-8ZSA digital inputs.

Last year when we set up at the factory, I simply went into the web UI and under NAX Streams set Auto Initiation on with default port of 5004.
This worked flawlessly at the factory, but since being on site we found the streams were not starting.

I've now implemented logic in simpl to start the streams and turned off Auto Initiation in the web UI.
This has mostly fixed the issue but very occasionally the streams will simply not start on first try.
I can force a stream stop then restart and it will then work.

In the NAX hardware def: Slot-07: DM-NAX-8ZSA —NAX > Slot-01: DM-NAX-8ZSA —TX> Slots-03 & 04:?DM-NAX-8ZSA — TX Source 3 & 4
I have defined the following:
* valid session name
* valid multicast address
* StartStream
* StopStream

I check in logic:
* I get a device ready pulse from Update Status.
* I have a valid multicast address
* Then issue the StartStream through a Truth Table when the above conditions are satisfied.
This logic works flawlessly and the StartStream digital is asserted.

I'm not checking I have a valid session name as this is set at startup & held in an MSP.

Anyone seen any of these issues and can offer any further suggestions?
I would really like to know why Auto Initiation no longer works, as I rather just do away with all the simpl logic.

Cheers