Jump to content

Matthew Steel

Members
  • Posts

    74
  • Joined

  • Last visited

Profile Information

  • Location
    SC
  • About
    Live sound and recording for higher education
  • Interested in Sound for Picture
    Yes

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This is important so I am putting it into a separate post. Experimenting with these commands is dangerous, as commands to not always do what you might expect. I will use the "block" command as an example, because you mentioned it in your file as writable, and I messed something up myself doing exactly that. Documentation for the command in the context of the VRM(WB) - which is block based, and doesn't know the concept of the 3-block bands - indicates that: * The query form of the "block" command, without parameters, reports the block of the receiver frame * The query form of the "block" command, with a receiver designator (1-6, or * for all) reports the block(s) of the corresponding receiver module(s) installed. * Note that for the VRM(WB) the "set" form of the command is not documented, and indeed makes no sense for a user in this context. However, it is entirely possible that the write form of the command may exist and could be a mechanism for configuration at the factory. Now move to another device, the HMa. Serial commands for this device are entirely undocumented, but they do exist through the USB interface. Since the HMa is a band-based device, and setting the channel requires you to also set a block, you might think that the "block" command would be a mechanism of tuning the transmitter. But in fact, the "block" command in the HMa works just like the command does in the VRM(WB): * The query form of the "block" command returns the base block of the unit's band. So, an HMa A1 will report block 470. * Setting the "block" parameter WILL RECONFIGURE THE FIRMWARE to use that block as the base of the tuning range. I know this by experience. In my case I was working in block 20 and in my experimentation I believe I must have sent the command "block=20". Everything appeared fine. But months later, I had cause to change the frequency to somewhere in block 470. I found that the transmitter refused to tune below block 20, even though it was an A1 unit. I called Lectrosonics and the tech there told me it needed to be sent in to the factory. After a bit of thought I guessed that my previous experimentation might have caused the problem. I figured it was worth a try to reverse my mistake. After all, I was about to send it in anyway. Setting the block back to 470 appears to have corrected the problem. When the tech followed up with me I told him what I had done and that it appeared to work fine now. I got a response something like, "I have no idea where you might have gotten the information you used to do that fix. That is certainly not something we at the factory would have given out. You could have bricked your unit." So, long story short, BE CAREFUL.
  2. I looked again, and "su" does not appear to apply to the SRc. The following additional commands "should" be there though. I expect many of them exist for factory setup and/or testing and as such will either be boring or dangerous. "buttons" - I expect an instantaneous status of what buttons are pressed. "lockdet" - something to do with a PLL lock? "divtest" - sounds like "diversity test" but what exactly that means... "extvcc" - wouldn't be surprised if it was a power supply voltage "rpixel" - screen testing, perhaps? "windet" - sounds like it may be a status of a window detector circuit of some sort...
  3. As for your missing commands, I don't have an SRc but my sleuthing tells me the following commands should exist: irsend pilotbp ameter (should be an audio meter value) txbatt (should be transmitter battery status) rmeter (should be an RF meter value)
  4. The online help in Wireless Designer contains a section on serial commands. I don't see anything specific to the SRc, but there are sections on Venue1, Venue2, DR, DSQD, M2T; and the commands from one unit to another generally follow the same format. Note that command reference in the online help does not appear to have been updated to reflect all firmware changes. For example, the Venue1 "channel" command is documented as taking a parameter from 0-255 for 100kHz steps; but the command actually takes a parameter from 0-1023 for 25kHz steps. If the SR is like the Venue1, you might enjoy trying the commands "su?" or "p". On the Venue1 these undocumented commands are used by Wireless Designer and provide an "ASCII-compatible-binary" version of the complete setup and status respectively. But be careful - it is possible to break things by writing the wrong thing to certain parameters.
  5. As far as the memory full issue, most Android devices (maybe even all, even the cheap ones) have a micro SD slot. That could make it possible to swap out media pretty quickly.
  6. I don't know if it would be worth Lectrosonics' time to make a device like that but I wanted the IR sync capability bad enough that I made a DIY IR sync device. I built several to support the 10 VRMWB racks we have. The devices do not integrate with Wireless Designer. Essentially they are a Raspberry Pi with an IR LED and ballast resistor and connect to the VRMWB connects via USB. I set it up so that to trigger an IR sync all that is required is to press and hold the Venue front panel select button corresponding to the receiver you want to sync. I'm fairly proud of all the features I've put into them, like: * Scan function that generates a CSV scan file suitable for import into Shure's Wireless Workbench * Frequency deployment to the Venue receivers using CSV format coordination report from WWB. * IR sync from Venue receivers to LMb transmitters. * In one location, automation between the Venue, an audio recorder, and a digital console. The software end of it has some significant hard coding so it is by no means a turnkey solution. But if you want to embark on your own DIY version let me know and I can give you some key information.
  7. You didn't say how you chose your frequencies, and nobody else has mentioned intermodulation yet. So if you haven't run a calculator on your frequencies yet it would definitely be something to check.
  8. Well, well, well. Anyone care to guess what showed up in the database yesterday?
  9. If there is one coming - and I expect there is eventually - it hasn't passed FCC testing yet. I don't see any new Lectrosonics authorizations in the FCC ID database (https://www.fcc.gov/oet/ea/fccid) since January 2019, except for the 940MHz variants and the DPR/DPRA.
  10. I expect you have already tried a different frequency, but in case you haven't, I have noted a few times that two transmitters on the same frequency will create interference that could be described as a squeal. I can't remember if it was with our Lectros or other brands though.
  11. Looks like we have a couple of winners...https://www.lectrosonics.com/lectrosonics-introduces-the-dchr-miniature-stereo-digital-receiver.html
  12. 940MHz SMWB and 940MHz SMDWB were certified in July. Have they been announced?
  13. If she is that good, then it makes the audio mixer/editor's job easy. If she's not, then there is still the possibility of a lot of tedious editing to get all the audio lined up to the picture....
  14. Also places like Tai Audio, Trew Audio, Location Sound will either consign or outright purchase gear. I'm not sure whether they are still accepting 600MHz stuff, but I still see it listed at least some of those places.
  15. I have run Wireless Designer over LAN using a Raspberry Pi. The USB in the Venue Racks uses a standard FTDI USB/serial chip. So it "is" a USB serial port. The Linux USB/serial driver, on the other hand, does not recognize the USB VID/PID combination. I had to write a udev rule to tell the kernel to use the standard FTDI driver. Once you have the driver set up and you have the Venue working as a usb/serial device, you can use a program called ser2net to present it as a TCP device. Wireless Designer can then connect to it over the network without any additional hardware. I have not used this combination extensively - I would like to do so but I need another application to share the Venues and have not yet written the component to allow that.
×
×
  • Create New...