Bose v35 Lifestyle

Ant

Hello,

Does anyone have a module for control a Bose V35 Lifestyle, it uses a 3.5mm to serial into the Data Port at the rear of the unit.

I received the protocol from Bose and thus far have tried
- Setting the Baud to 19200
- Sending various Query and Set commands to the device.

It responds with what looks like error messages.
Ex. $07$82$01$$FE$FF$01$04$07$01$00

The House Code is 15 and Room Code is B.

Is there anywhere i need to setup the console for serial comms? I can't find anything in the setup menu.


Thanks,
Ant

vining

Without posting the protocol and what you're sending to it we can't really say whether the return is good or bad. I don't recall any previous discussions on this device so there might not be anyone familiar with it so a more complete post is required.

Ant

Hey - thanks for responding.

Protocol is attached

I've tried sending
TO: KP %26$0D
RX: $07$82$01%$FE$FF$01$04$07$01$00

TO: $0b,$00,$01,$04,$02,$02,$2c,$01,$00,$0e,$00,$2d
RX: $07$82$01,$FE$FF$01$04$07$01$00

TO: $0b$00$01$04$b3$01$2c$01$0F$01$9F
RX: $07$82$01$$FE$FF$01$04$07$01$00

TO: $05$00$04$01$00
RX: $07$82$01$$FE$FF$01$04$07$01$00

The House Code is 15 and Room Code is B.


Not sure what i'm doing wrong

ericmedley

Ant wrote: »

Hello,

Does anyone have a module for control a Bose V35 Lifestyle, it uses a 3.5mm to serial into the Data Port at the rear of the unit.

I received the protocol from Bose and thus far have tried
- Setting the Baud to 19200
- Sending various Query and Set commands to the device.

It responds with what looks like error messages.
Ex. $07$82$01$$FE$FF$01$04$07$01$00

The House Code is 15 and Room Code is B.

Is there anywhere i need to setup the console for serial comms? I can't find anything in the setup menu.


Thanks,
Ant

I don't see an attachment.

Ant

Eric,


I've re-attached.


It responds with what looks like error messages.
Here are samples of TX and RX Msgs thus far:

TO: KP %26$0D
RX: $07$82$01%$FE$FF$01$04$07$01$00

TO: $0b,$00,$01,$04,$02,$02,$2c,$01,$00,$0e,$00,$2d
RX: $07$82$01,$FE$FF$01$04$07$01$00


TO: $0b$00$01$04$b3$01$2c$01$0F$01$9F
RX: $07$82$01$$FE$FF$01$04$07$01$00


TO: $05$00$04$01$00
RX: $07$82$01$$FE$FF$01$04$07$01$00


Thanks for your help.

ericmedley

Ant wrote: »

Eric,


I've re-attached.


It responds with what looks like error messages.
Here are samples of TX and RX Msgs thus far:

TO: KP %26$0D
RX: $07$82$01%$FE$FF$01$04$07$01$00

TO: $0b,$00,$01,$04,$02,$02,$2c,$01,$00,$0e,$00,$2d
RX: $07$82$01,$FE$FF$01$04$07$01$00


TO: $0b$00$01$04$b3$01$2c$01$0F$01$9F
RX: $07$82$01$$FE$FF$01$04$07$01$00


TO: $05$00$04$01$00
RX: $07$82$01$$FE$FF$01$04$07$01$00


Thanks for your help.

I still don't see it??? Perhaps it a file type not allowed? what kind of doc is it?

vining

$07$82$01 % $FE$FF$01 (FYI %=$25 in this packet)

Does appear to be an error for PACKET_TIMEOUT followed by

$04$07$01$00

which appears to be a ready packet

Maybe it's in low power mode:

5.5 Low Power Mode The console transitions from Normal Power to Low Power Mode when both Zone1 and Zone2 sources have been in the OFF source (see section 6.8 SR - Query Zone Source) for ALL_OFF_TIME. The system automatically turns off all rooms and enters Low Power Mode if no key press has been received for INACTIVITY_TIME. The only way to bring the system out of Low Power Mode is by sending a key which turns on the Console such as BOSE_ON_ASSERT or BOSE_INPUT1. Some keys have no meaning when the Console is in Low Power mode (e.g. BOSE_LEFT_ARROW) and are not processed. If Hard Key Press Notification has been enabled all (hard) key presses are echoed in both Low Power and Normal Power mode. Since a Power failure or system crash is rare but can be detected by the Uptime command (see section 6.12 UpTime - Query System Up Time) or the Query Key Press Notification command (see section 6.3.1.3 Query Hard Key Press Notification State) since notification is reset to false after a reboot. Use the SysRdy command (see section 6.11 SysRdy - Query System Ready) to determine if the Console is in Low or Normal Power Mode.

6.1 VR - Query Version The version command requests the Software version of the Console. Note the Console must not be in Low Power Mode (see section 5.5 Low Power Mode) to get a valid response. Otherwise an Error packet will be sent. Use the SysRdy command to query the Low Power State of the system. (See 6.11 SysRdy - Query System Ready.) Client sends: 05 00 04 01 00

Try sending the SysRdy query:
07 00 01 1d 00 00 1b

Maybe that will give you a proper response.

Ant

Thanks for looking at this guys, appreciate it.

I'll be back on site today and give it go and leave you know the progress

Ant

Guys,

Thanks for your help. It worked. Just ensure to place to $0d when send strings from control a device ;p

Here are commands that worked for me.


cmdQZone_Src[] = {$08,$00,$01,$0a,$00,$18,$18,$03,$0d} // Query Main Room Current source
cmdQZone_Vol[] = {$07,$00,$01,$15,$00,$1e,$0d,$0d} // Query Main Room Current Volume

cmdVol_Set_GA[] = {$07,$00,$01,$15,$01,$46,$54,$0d} // Set Volume to 70%
cmdVol_Set_RmSrc[] = {$07,$00,$01,$15,$01,$19,$0b,$0d} // Set Volume to 25%

cmdAmp_IP_1[] = {$0b,$00,$01,$04,$B3,$00,$2c,$01,$00,$00,$90,$0d} // Select Inputs
cmdAmp_IP_2[] = {$0b,$00,$01,$04,$12,$00,$2c,$01,$00,$00,$31,$0d}
cmdAmp_IP_3[] = {$0b,$00,$01,$04,$13,$00,$2c,$01,$00,$00,$30,$0d}
cmdAmp_IP_4[] = {$0b,$00,$01,$04,$15,$00,$2c,$01,$00,$00,$36,$0d}

cmdAmp_Pwr[] = {$0b,$00,$01,$04,$4C,$00,$2c,$01,$00,$00,$6F,$0d}

cmdVol_Mute[] = {$0b,$00,$01,$04,$01,$00,$2c,$01,$00,$00,$22,$0d}
cmdVol_Down[] = {$0b,$00,$01,$04,$02,$00,$2c,$01,$00,$00,$21,$0d}
cmdVol_Up[] = {$0b,$00,$01,$04,$03,$00,$2c,$01,$00,$00,$20,$0d}


Thanks again

vining

Glad to see you got it working but that's definitely contradicts their own manual, last line.

4 Packet Format
All interactions between the Client and the Console are in the form of complete packets. A Packet always begins with a Header field which contains the Length, Status, and Operation
Code. The Payload field contains any required parameters. Packets from the Client must also include a Checksum field.
<Header> [ <Payload> ] <Checksum> Client to Console <Header> [ <Payload> ] Console to Client -- Note: no Checksum Note: Packets are NOT terminated with a Carriage Return or Line Feed.

Duncan Ellis

I did some work on this when it first came out and havent really touched it since. You have to take the protocol doc with a pinch of salt and just work it out. I found that hitting the unit with a source command worked for me. The response told you if it was off or was on and had made the switch and then you have to poll the unit until you find it is ready. Its not straight forward to make it work well...not really a pro product I think, just adapted.