Signaling E&M-FGB not supported in 3845

I have the following problem:
When I try to configurate the interface E1 "VWIC2-2MFT-T1/E1" with this command:
"ds0-group 0 timeslots 1-15,17-31 type e&m-fgb"
router don´t received it.
GW-1(config-controller)# ds0-group 0 timeslots 1-15,17-31 type ?
e&m-delay-dial       E & M Delay Dial
e&m-fgd              E & M Type II FGD
e&m-immediate-start E & M Immediate Start
e&m-lmr              E & M land mobil radio
e&m-melcas-delay     MEL CAS (CEPT) E & M Delay Start
e&m-melcas-immed     MEL CAS (CEPT) E & M Immediate Start
e&m-melcas-wink      MEL CAS (CEPT) E & M Wink Start
e&m-wink-start       E & M Wink Start
ext-sig              External Signaling
fxo-ground-start     FXO Ground Start
fxo-loop-start       FXO Loop Start
fxo-melcas           MEL CAS (Mercury) FXO
fxs-ground-start     FXS Ground Start
fxs-loop-start       FXS Loop Start
fxs-melcas           MEL CAS (Mercury) FXS
none                 Null Signalling for External Call Control
r2-analog            R2 ITU Q411
r2-digital           R2 ITU Q421
r2-pulse             R2 ITU Supplement 7
Im using this IOS:
c3845-advipservicesk9-mz.124-24.T1.bin
Which could be problem?
Regards,
Jonathan Perez

I need the signaling E&M-FBG because I will migrate from AS5300 with this signaling --> (PBX) to 3845

Similar Messages

When connecting an HDMI adapter I get the message This device is not supported by this ipad

WWhen I connect the adapter vis an HDMI cable to my TV, I see the image of my IPad then I get the error message about not supported and the TV displays No Signal. I have a multifunction adapter that works although the connection on it is fiddly. I Use an IPad 2 with the latest version of IOS .

Howdy Gdad_Edw,
Welcome to Apple Support Communities.
Take a look at the article linked below, it provides information and troubleshooting tips that can help you resolve the no video issue with your Apple Digital AV Adapter and your iPad.
About Apple Digital AV Adapters for iPhone, iPad, and iPod touch - Apple Support
Troubleshooting
If you encounter an issue using the Apple Digital AV Adapter or VGA Adapter:
Disconnect and reconnect the adapter from the iOS device and display.
Connect directly to the TV, projector, or external display using a known-good VGA or HDMI cable.
Remove any VGA or HDMI extension cables or converters.
Note that accessories that convert a VGA or HDMI signal to other video formats (DVI, Composite, Component) are not supported.
Ensure that you are using the latest version of iOS. Some Apple Digital AV Adapters require iOS 5.1 or later.
Ciao,
-Jason

Included Mini-DVI to DVI adapter does not support HDCP and iTunes HD movies

Hi.
Just downloaded Twilight in HD (to own) from the iTunes Store and had the annoying message about HDCP not being supported by my display, and that I could not play the movie in HD.
My Mac Mini is plugged to a very HDCP-compliant Sony Bravia 40" LCD TV via Apple's mini-DVI to DVI adapter (included in the new Mac Mini's box) and a DVI to HDMI cable.
(HDCP works well for this TV with a PS3, another Sony Blu-Ray player (the 2 are for zones A and B), an AppleTV)
Since I have other recent Macs with a Mini DisplayPort, I happen to also have an Apple branded Mini DisplayPort to DVI adapter.
So I replaced the (mini-DVI to DVI) adapter by the (Mini DisplayPort to DVI) adapter and plugged it on the Mini DisplayPort on the Mac Mini.
I can now play the HD version on my Sony TV!!
This really sounds like a joke!
A joke that is going to make me go the shop and buy another (Mini DisplayPort to DVI) adapter, since I like to always have one, as well as the VGA adapter, with my MacBooks.
Let's hope there will sonn be an iTunes, Leopard, or mini-DVI to DVI adapter firmware update very soon to fix this.

I am actually very surprised that your miniDisplayPort to DVI transition works with HD content.
I'd consider that a bonus and cherish it until Apple removes that functionality in a future update.
It is probably a bug as it should not work.
The thing to keep in mind is that DVI cables do not support the necessary DRM/encryption signals for HD video content.
This is one of the main reason DisplayPort was introduced.
So I am not surprised that miniDVI to DVI to HDCP does not play HD content on your TV.
In fact this is +expected behavior+ due to the lack of DRM/encryption signals.
No matter how you convert from miniDVI to DVI, the port cannot create something that it doesn't have in the first place.
The more I am surprised that the miniDisplayPort to DVI to HDCP transition provides these signals. I would have expected them to be filtered out in the DVI cable in the middle as this cable cannot pass something on that DVI is not designed to carry (HD DRM/encryption signals).
It could very well be a 'bug' in the miniDisplayPort to DVI cable controller, which Apple might 'fix' in a future driver update.
It is likely a mistake that this works.
What you really need is a miniDisplayPort to DisplayPort to HDCP conversion. Or directly a miniDisplayPort to HDCP cable. Those are the only routes that are guaranteed to work passing HD video DRM/encryption signals along.
But as far as i know neither of these two cables are available yet.
Which might be the reason why Apple - for the time being - allows your miniDisplayPort to DVI route to work. Emphasis on +for the time being+.
I would not count on the fact that this will work forever.
And I would certainly not count on a software update that will make the DVI route work. This will never work due to DVI's incapacity of providing DRM/encryption signals for HD content.

G5 with samsung 52" tv Mode not supported

Does anyone know how I can make my Powermac G5(single 1.8 ATI Radeon 9800pro) work with my Samsung 52 inch TV at HD resolution
I am attempting to convert my old Powermac G5 into a media computer. At some point I may want to add a blu-ray drive.
When I use the DVI on the G5 with a DVI to VGA adapter and connect to the TV via its VGA input. There is no picture and the TV says "mode not supported".
When I connect a second monitor to the ADC (via ADC to DVI) I can get the G5 to show up on the TV in mirror or extended mode (if I set the resolution to 1024 x 768 or less).
I have tried hocking up a monitor via VGA, setting the resolution to 1024x768, then shut done, restart with TV attached and still "mode not supported"
I have also tried making the TV as the main desktop in extended mode then restarting without the second monitor and still "mode not supported"
I tried a DVI to HDMI adapter but I got nothing "searching for signal" I would assume this should work so it might have been bad so I am going to exchange it and get a new one and try that.
?

I had to do the same, that is, accept a lower resolution for my LCD TV.
Using a Geforce 6800 GT, I have an interesting mix of "i" and "p" resolutions, but, as with the 9800 Pro, no 1920x1080p.
Just as well, though, as I couldn't read the text at highest resolution.
I'm pretty sure that this is simply a case of the high resolution 16:9 ratios not being supported in these older cards.
The resolutions that are available in the firmware of the cards are predominately for 16:10 ratio screens.
Remember, HDTV is a lot newer than most all AGP graphics cards.
I guess, when I have time, I'll have to play with DisplayConfigX and see if there is hope.

2008 Airport Express utility doesn't work all of a sudden, name reverted to ID, lost security, message not supported.

The Airport Express I purchased in 2008 worked fine this morning, but when I tried to use Wi-Fi with my cell phone and iMac the light was green on the AE but no signal. I unplugged AE and unplugged my modem, plugged in my modem, plugged in my AE, it turned green but no signal - that is, the name I had given it did not appear on either my iMac of cell phone. Then, out of the blue, the original ID for my AE shows up on the iMac and phone and when I selected it my Wi-Fi worked, and is working. The problem is there now is no security. I got a message that Airport Utility did not support or something like that. So then I took the old CD that came with AE (in 2008) and loaded that on my iMac so I could re-establish WPA security. It seemed to load okay but then the following message popped up, "AirPort can't be installed on this disk [my Macintosh HD]. The version of Mac OS X on this volume is not supported." Well, yes, since I'd purchased my AE I'd gone through all the cats and recently had upgraded to Mountain Lion, 10.8.5, several weeks ago. But since this morning I had done nothing new.
So, it's 12:30am, Apple Care is not open - I'm not even sure I'm still covered - so maybe some night owl out there can tell me what I need to do. I'm beginning to suspect it might have to do with my operating system upgrade, but don't understand why this problem should suddenly crop up after several weeks. Any ideas out there? Oh, and incidentally, my AE was cutting off a lot about a year ago and I took it into an Apple Store and they did something with the software in the device and the cutting off improved but still would occur at least twice a week - something I just lived with.

Then, out of the blue, the original ID for my AE shows up on the iMac and phone and when I selected it my Wi-Fi worked, and is working.
My first thought is that the AirPort Express is normally good for 4-5 years on average, so you may be getting some signals in that regard.
The AirPort Express reset itself back to factory default settings. The big question now is if you re-configure it again whether it will hold those settings. Not likely....my opinion.
The other problem that you have is that Mountain Lion operating system no longer supports the older version of the AirPort Express that you have.
Oh, and incidentally, my AE was cutting off a lot about a year ago and I took it into an Apple Store and they did something with the software in the device and the cutting off improved but still would occur at least twice a week
It's really time for a new AirPort Express, which will offer much faster reliable performance....and it will be compatible with AirPort Utility on the Mountain Lion operating system.

One or more devices do not support multidevice tasks.

Hi,
I'm working with 2 USB X series DAQs (USB 6356). I am acquiring analog voltage data from all 8 channels on both DAQs (so 16 analog input channels total). I need the data acquisition to be synchronized and to trigger from an external digital source (a signal that I currently have wired into PFI0 of Dev A). I am using a sampling rate of 800 kHz, and a buffer size of 400 kS.
I have tried using one express vi for both devices; two separate express vis for each device; and recently changed to the DAQmx icons (as pictured in the attachment). Either way I get an error (error -201426: One or more devices do not support multidevice tasks.). It then references DevA and DevB as the devices that don't support the tasks. I was under the impression that multidevice tasks are okay with X series devices. I am using NI DAQmx 9.5.5.
In the attached picture, I have left out most of the while loop. The part of the diagram I left out is just for visualizing and saving the data, I have included the parts I felt necessary for describing my problem.
I would really appreciate any advice.
Thank you,
Leslie
Solved!
Go to Solution.
Attachments:
multidevice daq vi.PNG ‏24 KB

Thank you both, for shedding some light on my setup and this error. The information I was finding on the NI website did not seem to specify that USB Xseries devices were an exclusion to the statement made.
I have changed my program and built two separate tasks, which has eliminated the error 201426 message. I have attached a picture of my newest program. It is still not functioning, however no error messages are sent. for(imstuck), I'm not sure what you mean by "build an array of tasks" or read inside a for loop. We view the digitized signal from each channel (DevA ai0:7 and DevB ai0:7) separately anyway, so would concatenating the waveforms be necessary? When I run the program and "highlight execution" the program seems to get stuck on the DAQmx read tasks, no errors, it just doesn't proceed or send the waveform data. Am I missing something or is the for loop/concatenating the waveforms necessary?
Thanks again,
Leslie
Attachments:
separate tasks.PNG ‏41 KB

HT201310 what do you do when apple tv says mode not supported

My apple tv stopped working and the tv says either no signal or mode not supported. I have restarted, unplugged the HDMI cables and restarted again. I have not updated any software. This Apple tv is new since December 14. The TV I have is older Samsung HD.
Can anyone assist?
Thanks

sounds like you raised the resolution to fullhd 1080p and the samsung can't cope
To select a video mode:
Press and hold both Menu and Menu up/scroll on the Apple Remote for about 6 seconds. Apple TV will cycle through different display resolutions.
When Apple TV reaches an acceptable display resolution and "If you can see the Apple logo, select OK" appears on your TV screen, press the Play button on the Remote.

Apple TV - Nothing displaying "Mode not supported"

Hi,
My Apple TV arrived today. I connected it all up using a HDMI-HDMI cable. I selected the HDMI channel on my TV (Samsung LE32R74BDX) but all i am getting is "No Signal"/"Mode Not Supported". I've tried the Menu and + to change the video settings but nothing comes up. Also tried restoring to factory settings with no luck.
Does anyone have any suggestions on what i can try?
Thanks
MacBook Pro Mac OS X (10.4.9)

I had the same problem initially, different TV
though. I was about to send it back when I realized
that the message was "Mode not supported" rather than
"No signal". While the TV manual was completely
unhelpful I assumed that the TV was getting a signal,
just not one it supported.
I don't have the Apple TV manual with me but in the
troubleshooting section it give a remote combination
(I think it was menu and play) that causes the Apple
TV to cycle through all the modes it has for TV
resolution.
When I did this I did finally hit on a resolution
(720p, which obviously was not the default) that
displayed the setup screen. I was using composite
not HDMI, but this may help since it wasn't obvious
in the manual.
It's worth a try.
The key combination is 'Menu' and '+' at the same time for 5-6 seconds.
The Apple TV will then cycle through the resolutions, when you get a picture you are happy with press 'OK'
Ian

Scrollable resultsets are not supported in my application

I want to use scrollable resultsets.But when i am writing the code
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
          String url = "jdbc:odbc:pmora";
          Connection con = DriverManager.getConnection(url,
"jbel", "jbel");
          Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_READ_ONLY);
ResultSet srs = stmt.executeQuery(
"SELECT COF_NAME, PRICE FROM COFFEES");
while (srs.next()) {
     String name = srs.getString("COF_NAME");
     float price = srs.getFloat("PRICE");
     System.out.println(name + " " + price);
To get support for scrollable resultsets, what driver we should use?Where we can get it?
#database is oracle 8
#driver version 2
#jdbcodbcbridgedriver
#While running the class, The followingmessage is getting displayed
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D366658
Function=[Unknown.]
Library=D:\j2sdk1.4.0_01\jre\bin\client\jvm.dll
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
     at sun.jdbc.odbc.JdbcOdbc.setStmtAttrPtr(Native Method)
     at sun.jdbc.odbc.JdbcOdbc.SQLSetStmtAttrPtr(JdbcOdbc.java:4676)
     at sun.jdbc.odbc.JdbcOdbcResultSet.setRowStatusPtr(JdbcOdbcResultSet.java:4473)
     at sun.jdbc.odbc.JdbcOdbcResultSet.initialize(JdbcOdbcResultSet.java:171)
     at sun.jdbc.odbc.JdbcOdbcStatement.getResultSet(JdbcOdbcStatement.java:423)
     - locked <02A3D7F0> (a sun.jdbc.odbc.JdbcOdbcStatement)
     at sun.jdbc.odbc.JdbcOdbcStatement.executeQuery(JdbcOdbcStatement.java:253)
     at ScrollableRS.main(ScrollableRS.java:27)
Dynamic libraries:
0x00400000 - 0x00406000      D:\j2sdk1.4.0_01\bin\java.exe
0x77F50000 - 0x77FF9000      C:\WINNT\System32\ntdll.dll
0x77E60000 - 0x77F45000      C:\WINNT\system32\kernel32.dll
0x77DD0000 - 0x77E5B000      C:\WINNT\system32\ADVAPI32.dll
0x77CC0000 - 0x77D35000      C:\WINNT\system32\RPCRT4.dll
0x77C10000 - 0x77C63000      C:\WINNT\system32\MSVCRT.dll
0x6D330000 - 0x6D445000      D:\j2sdk1.4.0_01\jre\bin\client\jvm.dll
0x77D40000 - 0x77DCD000      C:\WINNT\system32\USER32.dll
0x77C70000 - 0x77CB0000      C:\WINNT\system32\GDI32.dll
0x76B40000 - 0x76B6C000      C:\WINNT\System32\WINMM.dll
0x6D1D0000 - 0x6D1D7000      D:\j2sdk1.4.0_01\jre\bin\hpi.dll
0x6D300000 - 0x6D30D000      D:\j2sdk1.4.0_01\jre\bin\verify.dll
0x6D210000 - 0x6D228000      D:\j2sdk1.4.0_01\jre\bin\java.dll
0x6D320000 - 0x6D32D000      D:\j2sdk1.4.0_01\jre\bin\zip.dll
0x6D250000 - 0x6D25A000      D:\j2sdk1.4.0_01\jre\bin\JdbcOdbc.dll
0x1F7B0000 - 0x1F7E1000      C:\WINNT\System32\ODBC32.dll
0x77340000 - 0x773CB000      C:\WINNT\system32\COMCTL32.dll
0x763B0000 - 0x763F5000      C:\WINNT\system32\comdlg32.dll
0x772D0000 - 0x77333000      C:\WINNT\system32\SHLWAPI.dll
0x773D0000 - 0x77BC4000      C:\WINNT\system32\SHELL32.dll
0x71950000 - 0x71A34000      C:\WINNT\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\comctl32.dll
0x1F850000 - 0x1F866000      C:\WINNT\System32\odbcint.dll
0x0AF30000 - 0x0AF99000      E:\Oracle\Ora81\BIN\SQORA32.DLL
0x60600000 - 0x60682000      E:\Oracle\Ora81\BIN\oracore8.dll
0x60800000 - 0x60848000      E:\Oracle\Ora81\BIN\oranls8.dll
0x10000000 - 0x1001A000      E:\Oracle\Ora81\BIN\OCI.dll
0x0B0B0000 - 0x0B0BF000      E:\Oracle\Ora81\bin\sqresUS.dll
0x60400000 - 0x60502000      E:\Oracle\Ora81\bin\OraClient8.Dll
0x0B1D0000 - 0x0B1D6000      E:\Oracle\Ora81\bin\oravsn8.dll
0x60200000 - 0x60264000      E:\Oracle\Ora81\bin\oracommon8.dll
0x60000000 - 0x6011F000      E:\Oracle\Ora81\bin\orageneric8.dll
0x60350000 - 0x60356000      E:\Oracle\Ora81\bin\orawtc8.dll
0x60A00000 - 0x60A2B000      E:\Oracle\Ora81\bin\oranl8.dll
0x60B00000 - 0x60BAA000      E:\Oracle\Ora81\bin\oran8.dll
0x60E00000 - 0x60E10000      E:\Oracle\Ora81\bin\orancrypt8.dll
0x61100000 - 0x61137000      E:\Oracle\Ora81\bin\oranro8.dll
0x71AD0000 - 0x71AD8000      C:\WINNT\system32\WSOCK32.dll
0x71AB0000 - 0x71AC5000      C:\WINNT\system32\WS2_32.dll
0x71AA0000 - 0x71AA8000      C:\WINNT\system32\WS2HELP.dll
0x0B1E0000 - 0x0B23E000      E:\Oracle\Ora81\bin\orannzsbb8.dll
0x61500000 - 0x6150E000      E:\Oracle\Ora81\bin\oranldap8.dll
0x61700000 - 0x6171C000      E:\Oracle\Ora81\bin\oraldapclnt8.dll
0x771B0000 - 0x772CA000      C:\WINNT\system32\ole32.dll
0x77120000 - 0x771AB000      C:\WINNT\system32\OLEAUT32.dll
0x61900000 - 0x61906000      E:\Oracle\Ora81\bin\oranhost8.dll
0x62100000 - 0x62106000      E:\Oracle\Ora81\bin\oranoname8.dll
0x0B240000 - 0x0B246000      E:\Oracle\Ora81\bin\orancds8.dll
0x62300000 - 0x62306000      E:\Oracle\Ora81\bin\orantns8.dll
0x62500000 - 0x62508000      E:\Oracle\Ora81\bin\orannds8.dll
0x0B250000 - 0x0B26C000      E:\Oracle\Ora81\bin\orannms8.dll
0x62700000 - 0x62741000      E:\Oracle\Ora81\bin\ORATRACE8.dll
0x62900000 - 0x62B1B000      E:\Oracle\Ora81\bin\orapls8.dll
0x63100000 - 0x63108000      E:\Oracle\Ora81\bin\oraslax8.dll
0x63200000 - 0x63272000      E:\Oracle\Ora81\bin\orasql8.dll
0x1F800000 - 0x1F818000      C:\WINNT\System32\odbccp32.dll
0x77C00000 - 0x77C07000      C:\WINNT\system32\VERSION.dll
0x71A50000 - 0x71A8B000      C:\WINNT\System32\mswsock.dll
0x76F20000 - 0x76F45000      C:\WINNT\System32\DNSAPI.dll
0x76D60000 - 0x76D75000      C:\WINNT\System32\iphlpapi.dll
0x76DE0000 - 0x76E06000      C:\WINNT\System32\netman.dll
0x76D40000 - 0x76D56000      C:\WINNT\System32\MPRAPI.dll
0x76E40000 - 0x76E6F000      C:\WINNT\System32\ACTIVEDS.dll
0x76E10000 - 0x76E34000      C:\WINNT\System32\adsldpc.dll
0x71C20000 - 0x71C6F000      C:\WINNT\system32\NETAPI32.dll
0x76F60000 - 0x76F8C000      C:\WINNT\system32\WLDAP32.dll
0x76B20000 - 0x76B35000      C:\WINNT\System32\ATL.DLL
0x76E80000 - 0x76E8D000      C:\WINNT\System32\rtutils.dll
0x71BF0000 - 0x71C01000      C:\WINNT\System32\SAMLIB.dll
0x76670000 - 0x76754000      C:\WINNT\System32\SETUPAPI.dll
0x76EE0000 - 0x76F17000      C:\WINNT\System32\RASAPI32.dll
0x76E90000 - 0x76EA1000      C:\WINNT\System32\rasman.dll
0x76EB0000 - 0x76EDA000      C:\WINNT\System32\TAPI32.dll
0x76F90000 - 0x76FA0000      C:\WINNT\System32\Secur32.dll
0x76DA0000 - 0x76DD0000      C:\WINNT\System32\WZCSvc.DLL
0x76D30000 - 0x76D34000      C:\WINNT\System32\WMI.dll
0x76D80000 - 0x76D9A000      C:\WINNT\System32\DHCPCSVC.DLL
0x762C0000 - 0x7634A000      C:\WINNT\system32\CRYPT32.dll
0x762A0000 - 0x762AF000      C:\WINNT\system32\MSASN1.dll
0x76F50000 - 0x76F58000      C:\WINNT\System32\WTSAPI32.dll
0x76360000 - 0x7636F000      C:\WINNT\System32\WINSTA.dll
0x76FB0000 - 0x76FB7000      C:\WINNT\System32\winrnr.dll
0x76FC0000 - 0x76FC5000      C:\WINNT\System32\rasadhlp.dll
0x64700000 - 0x6470C000      E:\Oracle\Ora81\bin\orantcp8.dll
0x71A90000 - 0x71A98000      C:\WINNT\System32\wshtcpip.dll
0x64500000 - 0x6450D000      E:\Oracle\Ora81\bin\orannts8.dll
0x71F80000 - 0x71F84000      C:\WINNT\System32\security.dll
0x76C90000 - 0x76CB2000      C:\WINNT\system32\imagehlp.dll
0x6D510000 - 0x6D58C000      C:\WINNT\system32\DBGHELP.dll
0x76BF0000 - 0x76BFB000      C:\WINNT\System32\PSAPI.DLL
Local Time = Thu May 15 14:59:26 2003
Elapsed Time = 5
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002D5
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.0_01-b03 mixed mode)

You definitely don't need to be using the Sun JDBC-ODBC driver, as this will not support scrollable ResultSets. There are several drivers out there that do, ... for a list of drivers check out
http://industry.java.sun.com/products/jdbc/drivers

"Function or method not supported" error at IviRFSigGen InitializeWithOptions.vi

Error 1074135023 at "IviRFSigGen Initialize With Options.vi", Primary Error (Hex 0xBFFA0011) "Function or method not supported". Error occurs when using Agilent IVI driver for RF Signal Generator (E4437B) with LabView. Instrument also does not switch to remote mode in response to the IVI initialize command from LabView, but direct communication using NI-488.2 Communicator works.

It looks like you are using the NI IVI Class Drivers, and have configured them to use the Agilent IVI-C driver under the hood. For some reason, it looks like the class drivers aren't happy with the Agilent driver, and that's the cause of the error.
You should first confirm your IVI configuration in MAX. You should make sure IVI Logical Name is pointing to the right Agilent driver, correct instrument address, etc. That name is what you pass into Initialize with Options.
If this doesn't pan out, it looks like you'll have to debug things.
First of all, do you need to use IVI? If not, then I'd recommend you download our LabVIEW instrument driver for this instrument, so that you can get LabVIEW source code.
It's available on http://ni.com/idnet/ at
href="http://zone.ni.com/idnet97.nsf/9b2b33e1993d877786256436006ec498/539916348394adc7862568ab005fbb....
If you do need IVI, then I'd suggest you try NI's IVI-C driver for this instrument, also on http://ni.com/idnet/ at this link. This includes LabVIEW Wrapper VIs for the driver.
If you want to use Agilent's driver, did they provide LabVIEW support with their driver? That is, did they include LabVIEW wrapper VIs? If so, you might try just calling the "AGE4437B InitializeWithOptions.vi" directly and see if you get an error. If they did not provide wrapper functions, I'd call them up and ask if they can give them to you.
I hope this helps. Let us know what you figure out.
Brian

HT4108 Vga adapter for ipad not supported

I've been using the vga adapter with a projector, but of late I've not been able to use it with my ipad2.

Hi nlrutt,
You do not mention whether your issue - a 30 pin to VGA adapter not working with your iPad - is with an Apple adapter or not. I will assume that it is and therefore it should function correctly.
I would suggest that you troubleshoot using the steps in this article -
iOS: About Apple Digital AV Adapters
Specifically -
Troubleshooting
If you encounter an issue using the Apple Digital AV Adapter or VGA Adapter:
Disconnect and reconnect the adapter from the iOS device and display.
Connect directly to the TV, projector, or external display using a known-good VGA or HDMI cable.
Remove any VGA or HDMI extension cables or converters.
Note that accessories that convert a VGA or HDMI signal to other video formats (DVI, Composite, Component) are not supported.
Ensure that you are using the latest version of iOS. Some Apple Digital AV Adapters require iOS 5.1 or later.
Note: When using an Apple Digital AV Adapter manufactured before early 2012 with iPad (3rd generation), you may see the "This accessory is not supported" alert. Dismissing the alert will allow you to use the adapter.
Thanks for using Apple Support Communities.
Best,
Brett L

Suddenly " display does not support HDCP " - March 2014

Hello Sky peoples Having had no trouble with my Sky+ HD and my LG TV for months and months I am now getting this "does not support HDCP" dialog every time I switch on. The TV was on then suddenly it blacked out and wouldnt restart - so I had to de-power at the socket. After restart, this error dialog always appears - and no HDMI signal I have tried all the remedial actions, power-down restarts, cable switchovers, updated box software, unplug/replug The display still works fine on bluray and xbox 360The sky box is still putting out a signal on composite video. yinch'14

Hi there Yinchy,
Thank you very much for joining us on the community forum and posting your query.
I am extremely sorry to see that you are experiencing this issue.
There are a number of things that you can do to try to resolve this.
Firstly, Reset the HDMI signal.
Using the Sky remote:
1) Press Standby on the Sky remote. Standby light displays.
2) Switch off the power supply or remove the plug at the mains socket.
3) Switch connection equipment to standby and disconnect at the mains socket.
4) Confirm no lights remain on the Sky box or any connected equipment.
5) Wait 60 seconds, then switch the TV on at mains socket.
6) Switch the TV to the correct HDMI or DVI input.
7) Switch the Sky box on at the mains socket.
8) Wait 2 - 4 minutes after the standby light displays.
9) Switch on all connected equipment at the mains socket.
10) Press Sky to switch on the Sky box. The green light displays.
Please let me know how you get on with this and I will be able to help you further if required.
Many Thanks,

"Your computer does not support video chatting." Sometimes.

Hi, I'm on a MacBook late '08 and my pal has some earlier macbook.
We are on each other's bonjour list. The problem is that sometimes we can have a video conference no problem, and at other, random times, the option is grayed out, and if I go to preferences, the iSight green light goes on, but the window says my computer does not support video chatting, and that's the end of the story. How do I troubleshoot that? Thanks.

Hi,
In the 5 years since iChat 2 came on the scene I have only managed 3 Video chats with people on Satellite connections.
The Issue is the time it takes to bounce the Signal Up and back to the Host server.
When you send for a Web page you send little data packets of requests.
Your computer does not send the next until the first is acknowledged.
It tends to improve once it is started and you may notice any downloads you do seem to get faster the longer they are going.
iChat requires for Video chat that the packets are almost Instantly responded to/acknowledged and most domestic modems do not do this.
Some commercial servers provide a Buffer at one end or the other that acts like the acknowledgement was sent speeding up the process and effectively getting the fastest service you can get out of the connection.
Speed testing your Connection tends to take long enough for the Acknowledgement issue to be reduced and will tell you the max speed you will possibly get
http://www.speedtest.net/ but not the start up speed.
With some services you can pay for the Buffering (I forget the actual name for it)
More http://en.wikipedia.org/wiki/SatelliteInternetaccess
See TCP Acceleration as well
8:24 PM Friday; November 6, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

What can I do if I want to use a route that is not supported by my device

I am using a refrence trigger Vi. and I want the source of the trigger to be Ai\ start trigger but this route is not supported by my S series DAQ device.
since I want the source of triggering to be one of the analog input signals that I'm acquiring by my device, I have to use a refrence trigger Vi.
otherwise the source and destination of my triggering would be the samewhich will give me an error.
Is there any other way I can do my triggering by my device or I need to change my device?
Attachments:
vi pic.jpg ‏3547 KB

sorry. I did not attach the vi because i think you may not be able to run it. and also it has some errors in it. here's my Vi.
Attachments:
OFDR 10.28.2014.vi ‏51 KB

ERROR:MapLib:973 - Tri-state buffers are not supported in this architecture.

Hi,
I face a ERROR:MapLib:973 problem with inout port in a pcore component.
I need ton instantiate an inout port at the top level to communicate wih my peripherical.
This inout port is driven by an XPS IP core (pcore).
The .mpd is :
PORT fdata = "", DIR = INOUT , VEC = [31:0], ENABLE=SINGLE, THREE_STATE = TRUE,TRI_I = fdata_I, TRI_O = fdata_O, TRI_T = fdata_T
PORT fdata_I = "", DIR = I , VEC = [31:0]
PORT fdata_O = "", DIR = O , VEC = [31:0]
PORT fdata_T = "", DIR = O
The .vhd is :
fdata_o : out std_logic_vector(31 downto 0);
fdata_i : in std_logic_vector(31 downto 0);
fdata_t : out std_logic ;
I got ERROR:MapLib:973 - Tri-state buffers are not supported in this architecture messages for each
signals of my fdata PORT, while mapping !
Thanks for you help.

What device are you targeting, and what version of the software are you using?
I target a xc7k325t-fbg676-2.
I use ISE 14.3 form platgen to xst and 14.7 from map to bitgen.
What does your top level HDL (verilog or VHDL) file look like (where the IO must be instantiated)?
It is a .vhd in whitch i wrapp my top XPS core, described by .mhs
The problematic IO port is instantiated into the mb_core.vhd (generated by XPS).
If i open it, i could see that the tool correctly infer the corresponding IOBUF's :
component mapping :
fdata_I => FX3_DQ_I,
fdata_O => FX3_DQ_O,
fdata_T => FX3_DQ_T,
One IOBUF infered:
iobuf_1 : IOBUF
port map (
I => FX3_DQ_O(31),
IO => FX3_DQ(31),
O => FX3_DQ_I(31),
T => FX3_DQ_T
Top level port :
FX3_DQ : inout std_logic_vector(31 downto 0);
THEN FX3_DQ signal is dirrectly branched in my upper level (top level) vhd file, with the same name.
What do your constraints file look like (where the pin number and names get declared)?
The port is only constrained in .ucf, like that:
NET FX3_DQ[0] LOC = "B24"| IOSTANDARD = LVCMOS33 ;
NET FX3_DQ[31] LOC = "G26"| IOSTANDARD = LVCMOS33 ;#Bank 14

Signaling E&M-FGB not supported in 3845

Similar Messages

Maybe you are looking for