Here are the commands for the Novastar presets. Strings can be sent UDP port 6000, commands start and end with square brackets.

 

preset1 (dual 16x9)-  [{"cmd":"W0605","deviceId":0,"screenId":0,"presetId":0}]

 

preset2 (single 16x9 centered)- [{"cmd":"W0605","deviceId":0,"screenId":0,"presetId":1}]

 

layer off (power off)- [{"cmd":"W0605","deviceId":0,"screenId":0,"presetId":2}]

If you're doing RS232, here is the pinout we used:

Terminate the RJ45 as normal 568B, then connect as follows to the Crestron RS232 block:

 

Pin 1 (Orange Stripe) to RX

Pin 2 (Orange) to TX

Pin 3 (Green Stripe) to Gnd

It does respond back with the string you sent and an OK acknowledgement appended to it. 

Hi Tony,

 

I just came across your post. Hopefully you can answer a few questions for me.

We have two H2's installed on a site & I have UDP comms working to both, although these don't have all the cards fitted yet so are incomplete.

I was able to get an API doc from the manufacturer in China on pain of death which I cannot share publicly.

 

The documentation is truly awful and does not match up with what I'm seeing on site.

 

* Preset recall:

Like you I'm issuing [{ "cmd":"W0605", "deviceId":0, "screenId":0, "presetId":0 }]

The expected response should be:

[{ { "name":"preset1", "presetId":0 }, { "name":"preset2", "presetId":1 } }] etc.

Then

[{"cmd":"W0605", "deviceId":1,"ack":"Ok"}]

 

Instead I'm seeing a string with length of 801 bytes beginning like this:

[{"deviceId":0,"screenId":0,"presets":[{"deviceId":0,"presetId":0,"layoutTemplateId":1,"name":"Preset 1","createTime":"1732182845.3510883","startTime":"","OSD":{"wordEnable":0,"picEnable":0},"bkg":{"bkgEn":0},"screen3D":{"enable":0,"type":0,"LeftFirstThenR

 

The string is being truncated in debugger (I think although difficult to tell at this point)

Is this what you have seen as well?

 

* ID's

Nowhere in the API doc does it describe what the following actually mean:

> deviceId

> screenId

 

I've only being testing with one Novastar for the time being and being using a deviceId: 0 & screenId: 0

 

There is no mention in the user manual of setting up deviceId or screenId and a Google search on Novastar device ID/screen ID returns nothing useful (I've tried various spellings as well)

 

Do I need to concern myself with this or will an ID of zero in both instances suffice?

 

Cheers

s