MagicRDS4 UECP

[zvykov]

Hi Jan, I've been using your app for a long time, it's good and flexible. But i ran into a coder who understands uecp commands very badly.
UECP support is declared by the manufacturer and the original encoder control program also sends via uecp, but the syntax is slightly different. I give a log from the original application. Is it possible to connect them somehow?
log:
-> "0A01004105444A20534D4153482026204E495645535441202D20506F7A766F6E69202020202020202020202020202020202020202020202020202020202020202020202020"
-> /RT (01,00) # 05 "Clear,2,Tgl" 'DJ SMASH & NIVESTA - Pozvoni                                    ' ;
-> Port: COM1(19200, NO, 1000)
-> 0000 09 45 0A01004105444A20534D4153482026204E495645535441202D20506F7A766F6E69202020202020202020202020202020202020202020202020202020202020202020202020 3B1D
-> FE000009450A01004105444A20534D4153482026204E495645535441202D20506F7A766F6E692020202020202020202020202020202020202020202020202020202020202020202020203B1DFF

[zvykov]

I tried to add various initial commands, but also did not achieve a result, any ideas? I really want to set up this system.

[Jan]

[FE 00 00 09 45 0A 01 00 41 05 44 4A 20 53 4D 41 53 48 20 26 20 4E 49 56 45 53 54 41 20 2D 20 50 6F 7A 76 6F 6E 69 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 3B 1D FF]
 Site address (0), Encoder address (0)
 MEC 0A - RT: DSN (1); PSN (0); MEL (65); '00000101' "DJ SMASH & NIVESTA - Pozvoni                                    "

I do not see anything non-standard, except the DSN field which they send with a value of 1, usually the value is 0 (current data set), effectively covering any data set. Maybe the coder does not understand the value of 0? You can specify the value of 1 in the External text tool for that coder:

sendto "Connection xxx" dsn:1

[zvykov]

Hi Jan. Tried your method, no change. The encoder behavior remains the same: normally accepts the first command, then stops. From the original, too, no longer accepts after that. Reset helps, and after that another message pops up from magicrds, which was not shown, but, apparently, got into the encoder memory. It works fine with the native app, but it's terribly inconvenient.

[zvykov]

The encoder has the ability to read what is loaded into it.

Here is from the original app:

RT[01](64) Clr, 2, Tgl, 'Egor Kann - Se lya Vi                                          '   0A0101410545676F72204B616E6E202D205365206C7961205669202020202020202020202020202020202020202020202020202020202020202020202020202020202020                             


here is from magicrds:

RT[01](64) Clr, 0, Tgl, 'Egor Kann - Se Lya Vi                                         '   0A0101410145676F72204B616E6E202D205365204C79612056692020202020202020202020202020202020202020202020202020202020202020202020202020202020

Conducted an experiment, the problem is in the marked.

[Jan]

You made a great analysis 

So the coder does not meet the UECP specs at this point:

5th byte:
Bits 4..1: 0 Indefinite transmissions

Instead of infinite loop of such RT, the RT is never transmitted. Very treasonable, making the coder almost useless in many cases. On the other hand, it must be mentioned that the UECP document is not written well in some aspects.

The Magic RDS 4 needs to be updated because this field is currently not user configurable. Please let us know the coder model and manufacturer, as this may be useful to know for other users.

[zvykov]

Thanks,  I just really want to work normally with this encoder from magicrds 
I suppose there is a chance to see this tweak in future releases?
Encoder model fora600k.

[Jan]

I'll add the field edit into the nearest update.

[zvykov]

Thank you for your responsiveness.
Is there an estimated release date?

[Jan]

Updates are usually released in 1 to 2 months periods.

[zvykov]

Okay, I will be waiting.

[zvykov]

Everything works in the new version, thanks