12-04-2012 01:15 AM
Hi Jeff and Bill,
Sorry to keep you guessing on the device interface. Its one of those devices that seems -to-meet-your-need-but-unbranded. Particularly when you buy over the net its even more tough as you only have the few pages of documentation that they give. This particluar device ( I dont want to mention the brand lest it should come as a negative publicity..) has exactly 15 commands and all of them have the same format but different lengths : I send xxxxxx <CR> and the device responds with yyyyyyy <CR> . In case my command has a syntax error it sends a <BEL> instead of <CR> . So thats it for the manual. Nothing more . Nothing less.
And so I have this device. Then I have the Bluetooth link up to the PC. And finally its CANopen valve on the other side of the device. Merging all this happens with the LV code. So when things dont happen as expected, any of the item in the chain could be at fault. And getting at "that" fault is the pain.
12-04-2012 10:27 AM
@Raghunathan wrote:
Hi Jeff and Bill,
Sorry to keep you guessing on the device interface. Its one of those devices that seems -to-meet-your-need-but-unbranded. Particularly when you buy over the net its even more tough as you only have the few pages of documentation that they give. This particluar device ( I dont want to mention the brand lest it should come as a negative publicity..) has exactly 15 commands and all of them have the same format but different lengths : I send xxxxxx <CR> and the device responds with yyyyyyy <CR> . In case my command has a syntax error it sends a <BEL> instead of <CR> . So thats it for the manual. Nothing more . Nothing less.
And so I have this device. Then I have the Bluetooth link up to the PC. And finally its CANopen valve on the other side of the device. Merging all this happens with the LV code. So when things dont happen as expected, any of the item in the chain could be at fault. And getting at "that" fault is the pain.
It all seems so straightforwad... I know I'm missing something here. 😞