| Products > Test Equipment |
| Talking to an Anritsu PSN50 |
| (1/3) > >> |
| tombi:
So I bought one of these PSN50 power sensor modules pretty cheaply off ebay. I thought there was PC software you could use with it but apparently the software is only used for calibration and retails for like $3K. The unit is supposed to connect to a sitemaster or whatever unit to measure power. As a result Anritsu won't tell me how to talk to it (fair enough I suppose). Before I put it back on ebay I thought I'd play with it to see if I could make it work. lsusb gives me this which looks promising (see the AT command interface) --- Code: ---Bus 004 Device 002: ID 0b5b:ffc8 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 2 Communications bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0b5b idProduct 0xffc8 bcdDevice 0.00 iManufacturer 1 Anritsu Company iProduct 2 PSN50 Power Sensor iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 67 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 2 Communications bInterfaceSubClass 2 Abstract (modem) bInterfaceProtocol 1 AT-commands (v.25ter) iInterface 0 CDC Header: bcdCDC 1.10 CDC ACM: bmCapabilities 0x02 line coding and serial state CDC Union: bMasterInterface 0 bSlaveInterface 1 CDC Call Management: bmCapabilities 0x00 bDataInterface 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 2 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 10 CDC Data bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0001 Self Powered --- End code --- Even better - I found there is a device at /dev/serial/by-id/usb-Anritsu_Company_PSN50_Power_Sensor-if00 So I poked some commands at it but whatever I send I get a response of 'BAD CMD' The fact that is responds seem like good new but does anybody have any ideas what it might be expecting? I tried *IDN?, ATZ (see if AT commands might work), help, ? 'read' and a bunch of other stuff. Thanks, Tom Biskupic |
| tombi:
Ok I made some progress! IDN? Give me ANRITSU,PSN50,0748037,0748037,1.00 STATUS? gives me a byte but I haven't figured it out yet (I'm using a terminal) TEMP? Gives me the current temperature. ZERO gives no response for a while and then says "OK" AVG? Gives me 1 if I say AVG 0 it says Ok and then AVG? says 0 Tried PWR? NPWR? POWER? Any other guesses worth trying? These were found by guessing based on the MA24106A manual but it is clearly different. Tom |
| luma:
This document from another one of their models suggests the following commands might be in play: CommandDescriptionSTARTPuts the power sensor in measurement modeSTOPStops the measurement mode and puts the sensor in idle modeIDN?Gets identification information from the sensorPWR?Gets the power reading from the power sensor.NPWR?Gets a new power reading from the sensorFREQ?Gets the current cal factor frequency value from the sensorFREQSets the cal factor frequency valueZEROZeros the power sensorTMP?Gets the current temperature from the sensorSTATUS?Gets the error status byte from the sensorHATSets High Aperture Time modeLATSets Low Aperture Time mode edit: here's documentation from another model from their site, check out page 13-1 for a huge list of remote commands you might try. edit2: just re-read your post, looks like we're already working from the same document. Have you tried PWRALL? |
| tombi:
Thanks for the tip! No - NPWR? PWR? PWRALL? Don't work either. I tried a random selection of commands from the power expert document you linked but no further hits. Super infuriating! I even had a peek inside in the hope I could grab some firmware but the uC is on the other side of the board so I would have to peel off stickers, unscrew the main connector etc to get to it (at which point I think its cal would be gone). I'll keep guessing. Oh and I might very nicely ask Anritsu support for a hint. You never know. Tom |
| luma:
I should note that POWERALL doesn't have a trailing ?, despite my placing one there in my question. |
| Navigation |
| Message Index |
| Next page |