Decrypting the Vado Identity wired shower controller

Hi

So, I'm attempting to use a waterproof shower controller to control something other than the mixer it was intended for. I was looking to use a wireless controller (see here) but that may be a little beyond this first attempt.

Instead I'm attempting to use a wired version instead.

So the controller I want to hack is the Vado Identity IDE-147A-C/P or now called the Vado SENSORI
Identity IDE-147C-C/P
.
So far I've passed a multi meter across all of the pins of the mixer to see what it's outputting and the attached is what I found.

Basically the controller is 5v DC and the power is on pins 3 (-ve) and 2 (+ve). I've connected 5v to it and, sure enough, it lights up and shows the default screen. It then displays E1 which is to be expected I guess as it's not connected to the mixer.

I'm thinking that pins 1 and 4 are likely to be tx / rx but I'm not sure which is which or what the next step would be to work that out.

I've tried to read digital values on pins 1 and 4 from the controller and they set to 1 as soon as I add power and stay there.
I've also tried reading analog on pins 1 and 4 from the controller and not much happens there either other than they both go to a particular voltage and stay there.

So the next step is going to be reading the same from the mixer to see if it shows up anything.
Then I'll start looking into serial reads from the mixer and try replaying that to controller to see what happens.

So, assuming it is serial then I need to work out which baud rate to use but I think that rather than attempt to work it out it may be quicker / easier to just try the standard rates and see if I can read anything.

I only have an uno at moment with a mega coming tomorrow so I'll hopefully be able to read from serial1 and write to the serial monitor then.

Nothing much to ask right now other than any advice on where to go next and I'll continue to update this thread with my findings...

Cheers,

Russell.

So, it turns out that pin 1 is the tx pin so I assume pin 4 is the rx.

Using this code:

long baudRate = 9600;
byte serialConfig = SERIAL_8N1;

const long cycle = 1000;

void setup() {
  Serial.begin(9600);
  Serial1.begin(baudRate, serialConfig);
}

void loop() {
  int inByte;  
  while (Serial1.available()) {
    inByte = Serial1.read();
    Serial.print(inByte, DEC);
  }
  Serial.println();
}

This was the output:

025525525525525525500
025525525525525525525200
01280128024025500
0255255150000
025525525525525525500
025525525525525525525400
25401280192128255255000
255311280000
0255255255255255630
025525525525525525525400
01281280251255255000
255600000
025525525525525570
025525525525525525525400
012822425525525524800
1500128000
02552552552553100
025525525525525525525400
0128025525525525525400
6000000
0255255255127000
025525525525525525525400
019225525525525525525400
25200128128224000
2552552557000
025525525525525525500
025525525525525525525200
012800128224255000
255255311280000
255255255255255255000
255255255255255255254000001281282552550
00255255630000
25500
2552552552552552550002552552552552552552550
000012819225525500
0255150000
00
2552552552552551500
25525525525525525525400012801282552552552400
03100000
00
25525525525531000
2552552552552552552550001281922552552552552520
0700000
02550255255255255140
002552552552552552552540
001282552552552552552540
0254000012800
025525525571280
002552552552552552550
001922552552552552552520
0128128012819225500
0255255310000
025525525525525525502550
025525525525525525525200
000128224255255025500
25525570000
025525525525525525500
255025525525525525525525400
01281280192255255000255
25515000000
255255255255255310
0255255255255255255255002540
012825525525512800
25519212800000
2552552552552551400
2552552552552552552550001281282552552552552480
2550254700000
002552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
25525525525525525502552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
2552552552552552550
25525525525525525502552552552552552550
2552552552552552550
...

and the line "25525525525525525502552552552552552550" repeats every 37 lines.

It looks to me as though the baud might be too slow for starters.
Secondly, it looks as though "2552552552552552550" might be a heartbeat of sorts with 0 being the termination character.
I also wonder if the data or stop bits are the wrong length as there is a line in there ending in 5 (assuming the 0 is the termination character) although I guess that could also be because of incorrect framing.

Any ideas on how to tailor the config?

Also, any ideas on how to interpret the data?

Interpreting would be much easier if you printed in HEX! Then 3 digit numbers and 1 digit numbers would not be jammed together. Leave at least a space between what you are printing.

The 255 is obviously a x'FF.

Pau;

Paul_KD7HB:
Interpreting would be much easier if you printed in HEX! Then 3 digit numbers and 1 digit numbers would not be jammed together. Leave at least a space between what you are printing.

The 255 is obviously a x'FF.

Pau;

Yeah, I found that really awkward as well so I've been working with HEX since. Will post more shortly.

So, firstly, some more information. I've opened the mixer to have a look at the components.
In the attachment you'll see 4 of them highlighted:

  • connection to the controller
  • 3152EIBZ - datasheet (pdf) - this is connected directly to item 1
  • PIC16F818 - webpage
  • JFR8.000 - wondered whether this was for timing? - probably of no importance in this thread though

The data sheet for item 2 states:

Part Number Duplex Data Rate (Mbps) Rise/Fall Time (ns) Tx/Rx Skew (ns) Bus ESD (kV) Pin Count
ISL3152E Half 0.115 1100 12/4 ±16 8

So I guess that confirms the baud rate, 115200 it is. Unless that's the max rate.
The other thing is that it states half-duplex... Err, that adds some complexity, doesn't it? or does it? or???

Is there anything else that the components could tell me about how to interpret the signal?

So, here's what I'm doing:

  • There are no connections between the mixer and the arduino mega. The mixer is plugged into the wall but not switched on
  • Switch the arduino on and open the serial monitor - no output as expected
  • Connect the tx pin from the mixer to the rx pin on the mega - output starts slowly
  • Wait for 5 lines of output then switch the mixer on - output comes fast
  • Wait for the mixer to complete start up noises then turn the mixer off - after 3 lines the output slows down
  • Wait for 5 lines of output then turn the arduino off

And here's the code:

long baudRate = 115200;
byte serialConfig = SERIAL_8N1;

const int lineLength = 100;
int curLength = 0;

void setup() {
  Serial.begin(baudRate);
  Serial1.begin(baudRate, serialConfig);
}

void loop() {
  int inByte;  
  while (Serial1.available()) {
    inByte = Serial1.read();
    Serial.print(inByte, HEX);
    Serial.print(" ");
    
    if (curLength++ > lineLength) {
      curLength = 0;
      Serial.println();
    }
  }
}

The arduino is connected to a laptop which is not connected to a power supply so how am I receiving any signal without a ground connected? Am I therefore just receiving interference?
And when I do connect the ground between the mixer and the arduino I get no output at all.

Is this a step backwards? How can I shield from interference and be sure I'm only getting a signal from the mixer?
Any help appreciated...

The output looked like this anyway:

Arduino turned on

0 0 FC 0 0 0 0 0 0 0 0 FC 0 E0 0 1C 0 0 0 0 FC 0 0 0 0 E0 0 0 1C 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 E0 0 FC 0 0 0 0 0 FC 0 0 0 3 3 0 0 0 FC 0 0 0 0 0 FC 0 0 0 0 FC C 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E0 0 0 E0 1C 0 0 0 0 0 0 0 0 
0 0 0 3 0 0 0 0 0 0 FC 3 0 8 0 0 0 1C 0 0 0 0 0 0 0 0 E0 0 0 0 F0 0 FC 0 0 F0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 70 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 0 0 0 0 1E 0 0 0 0 0 1C 0 0 0 0 0 0 FC 
0 0 FC 0 0 0 FC 0 0 FF 0 0 2 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 1C 0 0 0 0 0 0 FC 0 0 0 0 0 0 FC FC 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 1C 0 0 0 0 0 0 0 0 FC 0 0 E0 0 1F 0 0 0 0 0 0 0 FC 1C 0 0 0 0 0 0 0 FC 1C 0 0 
0 0 0 0 0 0 0 0 0 C 0 FE 0 0 0 4 0 0 0 0 0 1C 0 0 0 0 0 FC 0 0 1C 0 0 0 0 0 0 0 0 0 0 1C 0 C 0 0 0 0 1C 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC 
C 0 0 1C 0 0 0 0 0 0 0 0 0 FC 0 0 0 FC 0 0 0 0 0 0 0 0 0 FC 0 0 0 FC 0 0 0 FC 0 0 0 0 0 0 0 0 0 E0 0 0 0 0 0 FC 0 1C 0 0 0 0 0 1C 0 1C 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 E0 1C 0 0 0 0 0 0 3E 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Mixer turned on

FC 0 0 0 E0 4 E0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF FF F0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF FC 0 0 0 0 0 0 0 FE 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 
F8 0 0 0 0 0 0 0 0 FE E0 C 0 0 0 0 0 F8 0 0 0 0 0 0 0 0 0 0 0 F0 F8 0 0 0 0 0 0 0 0 0 F8 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 FC 0 0 FC 0 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 FF E0 0 0 0 0 
0 0 0 0 0 0 0 0 C0 0 0 0 0 0 0 0 0 0 0 0 0 FF FF F0 0 0 0 0 0 0 FF FF 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FC F8 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FC C0 0 0 0 0 0 0 FF FC 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 FE 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FC F0 0 0 0 0 0 0 0 FE FC 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 0 0 FC C0 0 0 0 0 0 0 0 0 FC E0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 F8 FE 0 0 0 0 0 0 
0 0 FC 0 1C 0 0 FC 0 0 FC FF 0 0 0 0 0 0 0 0 0 0 0 F8 F0 0 0 0 0 0 0 0 0 0 FF F8 E4 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 F8 0 0 0 0 0 0 0 0 0 FC C0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF 0 FF E0 0 0 0 0 0 0 0 0 0 0 FF FF F8 0 0 0 0 0 
0 0 0 0 0 0 0 FE 0 0 0 7 0 0 0 0 0 0 0 0 0 F0 F8 C 0 0 0 0 0 FE FF 0 FC 0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 0 FF F0 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 F8 0 0 0 0 0 0 
0 0 0 0 0 0 FE FC C0 38 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FF E0 0 0 0 0 0 0 0 FF F8 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 FC F8 0 0 0 0 0 0 0 0 FE FF F8 FC 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 FC F8 0 0 0 0 
0 0 0 0 FF FC 86 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 0 F0 FC 0 0 0 0 0 0 0 0 C0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF 0 0 F0 E0 0 0 0 0 0 0 0 0 0 FC F8 C 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 F0 0 0 0 0 0 0 0 0 0 0 FF FC F8 0 0 0 0 0 0 0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 3 0 0 FC F8 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC FE F8 0 0 0 0 0 0 FE 0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 0 F0 1C 
0 0 0 0 0 0 FE FE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF E0 0 0 0 0 0 0 0 F8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 F8 FC 0 0 0 0 0 0 0 FF FE F8 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 FE F0 0 0 0 0 0 0 0 0 FE FC F0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 FE FF 0 0 0 0 0 0 0 0 0 0 0 0 0 FE 0 0 0 0 0 0 0 0 0 0 0 C0 F 0 0 0 0 0 0 0 0 F0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 F8 0 0 E0 0 0 0 0 0 0 0 0 FF 0 E0 F8 0 0 0 0 0 0 FF 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 FF FC FC 0 0 0 0 0 FC 0 0 0 0 0 0 0 F0 0 0 E0 0 0 0 0 0 0 0 0 0 0 FE E0 0 0 0 0 FC 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FF 0 0 F8 0 0 0 0 0 0 FC E 0 0 0 0 0 0 0 0 0 0 FF E0 0 0 0 0 0 FF 0 F8 FF 0 
0 0 0 0 0 F8 0 0 0 0 0 0 0 0 0 0 0 FF 0 F0 F0 1C 0 0 0 0 0 0 FF FC 0 0 FE 0 0 0 0 FF 0 FE 0 0 0 0 0 0 0 0 0 0 0 FE FC 0 0 0 0 0 0 0 FE 0 0 0 0 3 F8 0 0 FC 0 0 0 0 0 0 0 0 0 FC FC C0 FE 0 0 0 0 0 0 0 FC FF 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 FE E0 0 0 0 0 0 0 0 0 FC F0 E 0 0 0 0 0 0 FC FE 0 0 0 0 0 0 0 0 0 0 0 FE F0 0 0 0 0 0 0 FF 0 0 FC 0 0 0 F8 0 0 F8 0 0 0 0 0 0 0 0 0 0 0 F8 F0 0 0 0 0 0 0 0 0 0 F8 FE 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 FC 0 0 B8 0 0 0 
0 0 0 0 7 0 FC FC 1C 0 0 0 0 F0 0 0 0 0 0 0 0 0 0 0 E0 0 0 0 0 0 0 0 0 0 0 FC FC 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E0 FE 0 0 0 0 0 0 0 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 0 0 FF F0 0 0 0 0 0 0 0 FF 0 0 
0 0 0 0 40 0 0 0 0 0 0 0 0 0 0 0 0 FF FC F8 0 0 0 0 0 0 FE F8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FE FE 3 38 0 0 0 0 0 0 FE 0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 7 0 0 0 FC 80 0 0 0 0 0 0 0 F0 0 0 0 0 0 FF 0 0 0 0 0 0 0 0 0 0 
FC 0 F8 F0 0 0 0 0 0 0 0 0 FE F0 0 0 0 0 0 FE 0 0 1C E0 0 0 FC FC 0 F8 0 0 0 0 0 0 0 0 0 FC 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FE 0 0 E0 0 0 FC FF 1C 60 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Mixer turned off

E0 0 FC 0 0 0 0 0 FC 0 0 0 0 FC E0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC E0 0 0 0 0 0 0 0 FC 0 0 0 0 E0 E0 0 0 0 0 0 0 0 0 0 0 E0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 1C 0 0 0 0 0 0 0 0 FC 0 0 0 0 
0 0 0 0 0 0 0 0 E0 0 0 0 0 0 0 0 0 0 0 FC 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E0 E0 0 0 0 0 0 0 3 C 0 FC FC FC 0 0 0 0 0 0 0 0 0 0 1C 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 FC FC 0 0 FC 7C E0 0 0 
0 0 0 0 0 0 FC FC 0 0 0 0 0 0 0 0 0 0 0 0 1C 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 1C 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC 3 F8 1C 0 0 0 0 0 0 0 0 0 7F 0 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 1C 0 0 0 0 FC 0 0 0 0 0 0 0

output slows

0 FC 0 1C 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 E0 0 0 0 0 1C 0 0 0 0 0 0 0 0 FC 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 1C 0 0 0 0 FE 0 0 0

arduino turned off

Ok, another step forward...

I've now set the internal pullup on the mega's rx pin and worked out that the cable that connects the mixer to the controller "crosses over" such that the pins on the mixer's connector are the same as the pins on the controller. I'm now bypassing the cable the connects the 2 which was causing me an issue with the + / - round the wrong way.

When looking at the connector face on with the notch at the bottom working in a clockwise direction from the bottom left:
On the plugs, pin 2 is +ve, pin 3 is -ve
On the cable, pin 3 is +ve, pin 2 is -ve

Pin 1 on the mixer connected to Serial2 on the Mega, pin 4 connected to Serial1.

I now only get a signal when power is applied to the mixer and the ground pin is connected. Thumbs up.

So, I'm investigating the mixer and, with this code:

long baudRate = 38400;
byte serialConfig = SERIAL_6E2;

void setup() {
  Serial.begin(baudRate);
  Serial1.begin(baudRate, serialConfig);
  Serial2.begin(baudRate, serialConfig);
  
  pinMode(17, INPUT_PULLUP); //Serial2
  pinMode(19, INPUT_PULLUP); //Serial1
}

void loop() {
  int inByte;
  if (Serial1.available()) {
    Serial.print("S1 - ");
    while (Serial1.available()) {
      inByte = Serial1.read();
      Serial.print(inByte, HEX);
      Serial.print(" ");
    }
    Serial.println();
  }

  if (Serial2.available()) {
    Serial.print("S2 - ");
    while (Serial2.available()) {
      inByte = Serial2.read();
      Serial.print(inByte, HEX);
      Serial.print(" ");
    }
    Serial.println();
  }
}

My output is as follows:

S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 38 0 
S2 - 0 0 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 
S2 - 0 
S1 - 38 38 0 
S2 - 0 0

This pattern then repeats.
I've changed the baud and config on the serials to 38400 / SERIAL_6E2 as 115200 / SERIAL_8N2 was only giving 0's.
So I'm still not convinced this is the correct baud and config but at least I'm getting consistent results now.
Next step is to try replaying the mixer's output to the controller and see what happens...

So, on to the controller...
If I send nothing to the controller then the screen displays E1 and there is no output to the rx pin on the mega.

HOWEVER...
I replayed "38" from the mega to the rx on the controller and it no longer goes into error. Rather it now displays "00" which is the normal "off" state. The backlight stays lit, however, which is not right but it's progress.

Also, it now starts singing like a bird.
So, with this code:

long baudRate = 38400;
byte serialConfig = SERIAL_6E2;

void setup() {
  Serial.begin(baudRate);
  Serial1.begin(baudRate, serialConfig);
  
  pinMode(18, INPUT_PULLUP); //Serial1 tx
  pinMode(19, INPUT_PULLUP); //Serial1 rx
}

void loop() {
  int inByte;
  bool addLine = false;
  if (Serial1.available()) {
    while (Serial1.available()) {
      inByte = Serial1.read();
      if (inByte != 0) {
        addLine = true;
        Serial.print(inByte, HEX);
        Serial.print(" ");
      }
    }
    if (addLine)
      Serial.println();
  }

  inByte = Serial1.write(38);
  inByte = Serial1.write(0);

  delay(100);
}

I get the following:

38 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
3C 38 38 38 38 38 38 38 38 38 
1E 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38 
F 38 38 38 38 38 38 38 38 38 
38 38 38 38 38 38 38 38 38

And on it goes.
Next I need to work out what else I should or shouldn't be sending it...

After putting this down for a little while, I did some further poking around with the controller and the transceiver chip uses RS-485 for its serial communications. So it's not quite as simple as a tx and an rx pin. This also necessitated the use of a couple of RS-485 modules for the arduino to convert the comms to something the arduino can use.

Furthermore, I'm still unsure of what the baud rate is as I seem to be able to retrieve apparently real data at a variety of bauds. I therefore thought it would be worth trying an oscilloscope to help detect the baud rate.

Using the instructions / code / app from here I managed to set up an oscilloscope using the arduino. It's certainly not perfect but it definitely appears to give some useful information.

From here it suggests measuring the shortest pulse and using a formula you can work out the baud.

I measured the shortest pulse at about 400 µs and that makes it really close to 2400 baud (allowing for errors in display and measurement).

I'm yet to test with this baud but, again, another step forwards perhaps...

Using the scope trace you should also be able to work out the number of data bits and stop bits used.

Riva:
Using the scope trace you should also be able to work out the number of data bits and stop bits used.

So I've done some measurements using the arduino oscilloscope and I'm not entirely sure it has suitable resolution to be completely confident about the individual bits.

Anyway, I've attached a screenshot with what it outputs and it shows the following:

The red line measurement shows a "packet" is 8 ms long.
The 2 pink dots on the red line are 1.2 ms apart.
The green line measurement shows the gap between spikes is about 0.4 ms.
The 2 pink dots on the green line are 3.5 ms apart - probably not that useful.

I've tried listening on Serial1 (the mixer) on the Mega and replaying any input to Serial2 (the controller) and vice versa but it's not working.

I have a feeling that there might be timing issues in that you may need to wait between bytes or something...

Any thoughts?

As your measuring the differential signal you only need to measure either the A or B side (or the UART input to the chip) on a single channel and this should increase the scope resolution.
Failing that then maybe invest in a cheap logic analyser like this that will be ideal for a job like this.

It's difficult to tell but looking at your image it looks like you will have only 7 bits per frame and assuming it includes one start and one stop bit that means only 5 data bits.

Riva:
As your measuring the differential signal you only need to measure either the A or B side (or the UART input to the chip) on a single channel and this should increase the scope resolution.
Failing that then maybe invest in a cheap logic analyser like this that will be ideal for a job like this.

It's difficult to tell but looking at your image it looks like you will have only 7 bits per frame and assuming it includes one start and one stop bit that means only 5 data bits.

Tried only reading one channel but it didn't seem to make any difference.
Also tried increasing the baud on the Arduino and the oscilloscope program to 250000 but, again, no dice.

I've ordered a logic analyser and it should turn up today or tomorrow so I'll give that a go and see what happens...

OK, so, logic analyser here and this is what I've managed to find so far.

I'm using sigrok to interpret the data from the analyser.

The following is connecting the analyser solely to the mixer, i.e. without the controller in the picture...

The image attached (full data.png) is the full set of data captured from when I turned the mixer on to when I turned it off.

The gap between the final peak of one packet and the first peak of the next packet is 47.3 ms

All the "packets" shown are the same and a single packet can be seen in the attached image (single packet.png). Each packet is 7.9 ms long and consists of 7 peaks. Are there start and stop bits at either end that are not peaks?

The attached image (peak.png) shows that a peak is 1 ms long and a trough (trough.png) is 0.1 ms long.

trough.png

Next installment...

Now I've connected the mixer and the controller to a breadboard and have the signal analyser effectively listening in to the conversation.

From the conversation, it appears that there's a lot more going on than the single "packet" from the previous post. Having seen the data in the conversation I've measured the smallest pulse and it's about 0.1 ms which (according to here) correlates with a baud of 9600.

So, with that in mind I added a UART protocol decoder (according to here, it's the only protocol decoder that mentions RS485) and set the settings in PulseView as shown in uart.png, started reading data and then turned on the mixer. After a period of time I turned off the mixer and stopped reading data.

The attached file (sample.png) shows the first 11 chunks of data.

A couple of things of note before getting to the data:

  • There is about 39.15 ms between the end of one chunk to the start of the next chunk.
  • PulseView seems to suggest there are a lot of Frame Errors but that may be because the protocol isn't really UART... perhaps

It looks like there are 7 bytes from the mixer (As there were 7 peaks in my last post) followed immediately by 7 bytes from the controller.
Only the final byte from the mixer ever appears to contain any data but then I haven't pressed any buttons on the controller yet.

The data is as follows:

00 00 00 00 00 00 00    00 00 00 00 00 02 00
00 00 00 00 00 00 41    33 F2 02 16 07 02 00
00 00 00 00 00 00 B3    33 F2 02 16 07 02 00
00 00 00 00 00 00 21    33 F2 02 36 07 02 00
00 00 00 00 00 00 B3    13 72 02 36 07 02 00 
00 00 00 00 00 00 41    13 72 02 16 07 02 00
00 00 00 00 00 00 B3    33 F2 02 16 07 02 00
00 00 00 00 00 00 04    33 F2 02 16 07 02 00
00 00 00 00 00 00 53    33 F2 02 36 07 02 00
00 00 00 00 00 00 24    13 F2 02 36 07 02 00
00 00 00 00 00 00 B3    13 72 02 36 07 02 00

I can definitely see a pattern there but I'm unsure what it means just yet.

The next thing I'll be trying is to see if I can replicate the data sent by the mixer using an arduino or it'll all be for nothing...

uart.png

UART decoder is probably the one to use.
RS485/RS422 describe the electrical differential signal to reduce/cancel noise induced in the cables so you can transmit signals further in electrically noisy environments.

Does the protocol decoder have an auto mode to determine the correct baud rate, start/stop bits, data bits and parity or did you select them manually.
Assuming it is Serial data then it looks like it could be configured as 9600,6N1 is this what you was using?
That's 1 start bit, 6 data bits and one stop bit. Other options could be 5N2, 5E1, 5O1

UART signals are normally high in an idle state so you might have the logic probe connected to the wrong leg of the RS485 A/B line as your captures show the signal as idle low. You might be able to invert the logic in the protocol decoder instead.

There's no auto mode that I can find so I had to select everything manually.

I've tried loads of different options and the closest I've come to a match is the one I've got to here which is 9600, 8N1.
I think it's more likely 8N2 as when I add a parity bit (of any type) and set 1 stop bit the length is perfect but the parity bit is often wrong but there's no option to add 2 stop bits in PulseView.

I'm actually monitoring both the A and B but was only showing 1 of them in the images to save space. Both signals are the same, as you'd expect, except being the opposite. The idle high signal shows exactly the same data.

You will know if the data is correct if you never get UART framing errors.
I mentioned about the A/B high idle as adding a UART protocol decoder to the wrong one may cause wrong data values and framing errors to be returned in the decode data.

This is just the sort thing I like working on and even looks at the Vado unit for playing with but it would be too expensive for just the fun of it.

Riva:
You will know if the data is correct if you never get UART framing errors.
I mentioned about the A/B high idle as adding a UART protocol decoder to the wrong one may cause wrong data values and framing errors to be returned in the decode data.

This is just the sort thing I like working on and even looks at the Vado unit for playing with but it would be too expensive for just the fun of it.

Had to put this down for a bit again as I've been really struggling with it.

When I use the RS485 modules I can't seem to replicate the unit's initial pattern in a sensible way. I set the baud to 9600 but when I send a character it's so much shorter than the pattern from the unit.

The only way I've managed to get close is with the following but it's not using the RS485 module at all so I don't think it'll work with the unit:

long unsigned lastCom = 0;
long unsigned curMicros = 0;

const int digPinHigh = 30;
const int digPinLow = 31;
const int byteLen = 7;

bool valArray[] = {HIGH, HIGH, HIGH, HIGH, HIGH, HIGH, HIGH, HIGH, HIGH, HIGH};

const int bitLen = 104;
const unsigned long comPeriod = 55000;

void setup() {
  pinMode(digPinHigh, OUTPUT);
  pinMode(digPinLow, OUTPUT);
  digitalWrite(digPinHigh, LOW);
  digitalWrite(digPinLow, HIGH);
}

void loop()
{
  curMicros = micros();
  if ((curMicros > (lastCom + comPeriod)) || (curMicros < lastCom)) {
    lastCom = curMicros;

    for (int j = 0; j < byteLen; ++j) {
      for (int i = 0; i < sizeof(valArray); ++i) {
        digitalWrite(digPinHigh, valArray[i]);
        digitalWrite(digPinLow, valArray[i] == HIGH ? LOW : HIGH);
        delayMicroseconds(bitLen);
      }
      digitalWrite(digPinHigh, LOW);
      digitalWrite(digPinLow, HIGH);
      delayMicroseconds(bitLen);
    }
  }
}

Monkey3:
When I use the RS485 modules I can't seem to replicate the unit's initial pattern in a sensible way. I set the baud to 9600 but when I send a character it's so much shorter than the pattern from the unit.

What if you use a lower baud rate, 300, 1200, 2400 and 4800 are standard rates below 9600 but it could also be custom.
Does your logic analyser protocol decoder have an auto baud option where it will try to figure out the baud rate for its self?

Riva:
What if you use a lower baud rate, 300, 1200, 2400 and 4800 are standard rates below 9600 but it could also be custom.
Does your logic analyser protocol decoder have an auto baud option where it will try to figure out the baud rate for its self?

Firstly, thank you Riva for your help on this. It's very much appreciated and is really keeping me invested.

ok, another step forwards perhaps...

I changed the arduino code that utlilises the rs485 module to the following:

long baudRate = 9600;
byte serialConfig = SERIAL_8N1;

#define TxControlMixer      3   //RS485 Direction control
#define RS485Transmit       HIGH
#define RS485Receive        LOW

long unsigned lastCom = 0;
long unsigned curMicros = 0;
const unsigned long comPeriod = 55000;
const int bitLen = 104;

byte message[] = {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

void setup() {
  Serial1.begin(baudRate, serialConfig);

  // Init Transceiver
  pinMode(TxControlMixer, OUTPUT);  
  digitalWrite(TxControlMixer, RS485Receive);
}

void loop()
{
  curMicros = micros();
  if ((curMicros > (lastCom + comPeriod)) || (curMicros < lastCom)){
    lastCom = curMicros;
    digitalWrite(TxControlMixer, RS485Transmit);  // Enable RS485 Transmit
    for (int i = 0; i < sizeof(message); ++i) {
      Serial1.write(message[i]);
      delayMicroseconds(bitLen);
    }
  }
}

The main point being I've removed the line that sets the RS485 module to receive. This means that the arduino is constantly in transmit which could be a problem when I connect the controller up but I'll get to that later.

This gave the right sort of pattern, as shown on the top line in the attached image.

Once I got to there I then changed the baud to 8750 (with some trial and error) which gave me the middle line.

The bottom line is the mixer.

Note:

  • the scale is not the same on each line
  • rather the measure at the top of each line shows the duration

So the overall length of a packet looks right but the individual segments look a little too short.