Pocket Pc emulator can support serial communication

hi , i am using Labview Pda 8.0.1

Nag123,
This topic is somewhat confusing and the documentation is not exactly accurate.
In order to configure the emulator do execute serial commands you have to first
add an emulator target to the LabVIEW project first. In order to that, create a
new project and right-click the project title and select New » Targets and
Devices...
In the new window that comes up, make sure "Existing target or
device" is selected and select the emulator you want from the PDA folder
below. Once you do this, the emulator target will be listed in the project
explorer. Right-click the target and select "New PDA VI". In this VI
you will code your program and when you run it, the emulator will be launched
and the VI will run within it. Once the emulator is running click File »
Configure and go to the peripherals tab. Here you can map the serial ports to
COM ports on your computer. You can actually only map Serial1 and Serial2 only
and I believe the reason for this is because Serial0 is restricted for
ActiveSynch.
Eli S.
National Instruments
Applications Engineer

Similar Messages

Emulator support serial communication?

Hi all
I'm trying to implement some serial communication using mobile to write to usb. But I'm surprised that is it possible to do with using emulator?
Here the problem is
String ports = System.getProperty("microedition.commports");this thing always return null when run it on my mobile. I used k510i to test this and finally got to know that jp6 (k510i) does not support serial communication.
But when this run on emulator it gives output string as COM1, COM2.
So my question is can we use emulator to do this, hence emulator does not have usb cable and does any one has an idea to convert emulator to make enable this?
If can please tell me how?

Sorry to say you that you can not touch your PC hardware from the emulator. Because the emulator runs KVM
as its runtime over the JVM. Thus if you want to touch the hardware of your PC then you have to request your
JVM from the KVM to communicate with the hardware and return you the response. Which is not at all possible.
But if you still want to use the COM1 and COM2 then run two different instances of the emulator and start a serial
communication between two emulators like a chat application.
Shan!!!

Does labview 5.0 support serial communication at a baud rate of 115200?

When I try to initialise my serial port at 115200 baud rate I get error 32, device paramter error. I'm running labview 5.0. Can anyone help me with this?

I use Serial Port Init.vi to set the baud rate to 115200 with no problem in LabView 5.0 under Windows 95.
I get error 38 when I try a non-supported baud rate.
Do you get the error when you run Serial Port Init.vi directly or just when you call it from your VI? On the diagram where you call Serial Port Init.vi, try placing a probe on the wire going to the baud rate input of Serial Port Init to see what value it's trying to set. You will have a problem going to 115200 if the control on your VI is represented as I16 or U8 or if the data range max doesn't go to 115200.

Does diadem 8.1 support serial communication at a baud rate of 115200?

Same question in English.
Regards

Hallo,
das ganze geht mit dem Script-Dac Treiber und der UDI Schnittstelle. In DIAdem 8.1 muss eine dll (gfsvbsdr.dll) registriert werden, damit der Script-DAC Treiber dann verwendet werden kann. Dort lässt sich dann im Script die Baudrate programmatisch verändern. Hilfe und eine Beschreibung dazu finden Sie unter:
http://digital.ni.com/public.nsf/websearch/BEF723E4698914DA86256FD30053397F?OpenDocument
MFG
Rebecca Fox
National Instruments, Germany
Rebecca Fox
Applications Engineer
National Instruments

UART and/or serial communication

Hello, Labview Experts,
Our sensor node uses UART protocol to communicate. We are able to convert it to serial signals. Does anyone know how we can manipulate serial communication in LabVIEW?
Thanks,
ck

Use the VISA vi's. Search for serial and VISA in the labview examples.

Using time warner road runner. when I try to open up safari to home page I get error message that this version does not support the "community toolbar" can't proceed until closing the error message. sick of seeing it

using time warner road runner. when I try to open up safari to home page I get error message that this version does not support the "community toolbar" can't proceed until closing the error message. sick of seeing it

That toolbar/ct plugin seems to cause problems for all who install it!
Close Safari, then locate and delete the following files and it should be gone:
/Library/Application Support/Conduit
/Library/InputManagers/CTLoader
/Library/Receipts/ctloader.pkg
/Library/Receipts/<Toolbar name>.pkg
/Library/Application Support/SIMBL/Plugins/CT2285220.bundle
/Users/<User name>/Library/Application Support/Conduit
where / is the root library on your Hard Disk.
If you are running Snow Leopard you should also look here:
Library/launchAgents/com.conduit.loader.agent.plist
Library/Application support/conduit plugins
Also, as mentioned by Gilli2000:
Library/Receipts - If you read it, it has information in it at the bottom referring extensively to "CT" and "community toolbar".
Maybe it is harmless, but trash those items anyway!
Note: Safari does not support any third-party toolbars except those supplied as an extension to Safari via the Extension Gallery.

Can i open lvm file in a Pocket PC emulator?

Hi all, can i open lvm/xls file in a Pocket PC emulator? I keep getting an error msg...
Thanx!

I was wrong. It does not appear that PocketExcel will open an LVM file, at least not in Windows Mobile 2003 on my Dell Axim X50v. However, there is a fairly easy workaround, if you have a copy of Excel (or OpenOffice, which is free). Open the LVM file in Excel, save as an Excel binary (XLS) file, then drag the Excel file to your synch folder. ActiveSync will convert the XLS file to pocket Excel format on transfer. You can then open it in PocketExcel. You can use ActiveX to save directly to an XLS file, or use the report toolkit to make your life a bit easier.
It is possible that you can do this, since I am a fairly new Windows Mobile user. I tried a simple copy of the LVM file and tried changing the file extension to .txt. I could not get PocketExcel to even look at it, although, as you mentioned, Pocket Word opened it with no problem. Diving into the documentation did not help much either. If anyone else having a bit more experience has a better solution, I would love to hear it.
This account is no longer active. Contact ShadesOfGray for current posts and information.

I w'd like to know if LabVIEW 6.0 Application Builder includes the daqdrv (for data acquisition) and serpdrv (for serial communication) support files by default.

Building an application to communicate to a device by serial port

Hi velou
The LabVIEW 6i Application Builder no longer requires daqdrv. Regardless of your Application Builder and LabVIEW version, you must always install the appropriate driver files on the target machine. For example, if your application communicates with a DAQ board and a GPIB board, then you must install NI-DAQ and NI-488.2 on your target machine. If you are using the VISA VI's for serial communication, than you have to install NI-VISA . If you are using the "old" serial VI's, than you have to include serpdrv separately.
Luca P.
Regards,
Luca

Labview PDa 8.0.1 can support visa

hi all , can u plz tell me Labview pda 8.0.1 can support modbus serial communication

Unfortunately, you cannot do modbus serial communication with LabVIEW PDA 8.0.1. In oder to do Modbus communication you would need the Modbus Library, but that requires NI-VISA and NI-VISA is not supported in LabVIEW PDA until version 8.2. Aside from this, you can do regural serial communication with PDA 8.0.1 using the Serial Compatibility VI's.
For more information please refer to the following knowledgeBase articles:
How Can I Implement Serial Communication With My PDA?
How Do I Use Serial Communication on My PDA?
Eli S.
National Instruments
Applications Engineer

Problems with Serial Communication using Labview 6 and Solaris 8

I am working on a Driver for a Temperature Controller. But I am stuck at the very basics. I am using Labview 6 and the platform is Solaris 8 on a SUN Ultra 60 Workstation. I can not get the Serial communication to work. When I am running raw (uncompiled) code it works (I can read from and write to ttya and ttyb) but once compiled I get error code 37 (device not found). I have tried the following steps to fix this with no luck.
1) I made sure that the "serpdrv" file is in the same folder with the executable. I also make sure the serpdrv file is added as a support file when building the app.
2) I changed from using traditional serial VI's to labview 6's new visa functions. With these "new" VI's when
I try to initiliaze the visa device and wire a control to the "visa reference" input only 1 serial port shows up (ASRL2, missing ASRL1). I am not sure if this is part of same problem or whole new issue.
3) I reinstalled both visa and labview 6.0.2 update hoping this would help with no luck
4) I placed the following entry into the ".labviewrc" file
labview.serialdevices: "/dev/ttya:/dev/ttyb"
If anybody has had the same problem I would love to hear about it and if you have any solutions
Jamie Shea

Hi Jamie,
1. Do you have NI-VISA driver installed on the machine on which you are running this executable?? If you are trying to run the executable on the same machine on which the development program has ran fine, then you can ignore this point.
2. If you have done all the changes that are suggested by other discussions related to this topic, then try changing the Port input to Visa Serial Configure.Vi from a control to a constant and try it. In some case, I have seen this to do the trick. I think this point should solve your problem. If it does do tell me. :-))

Windows Azure Active Directory MA - Maximum number of items that can be serialized or deserialized in an object graph is '500000'. Change the object graph or increase the MaxItemsInObjectGraph quota.

Trying to use WAAD with FIM 2010 R2 SP1 (4.1.3496.0) and during export several objects cause a warning/info with:
Maximum number of items that can be serialized or deserialized in an object graph is '500000'. Change the object graph or increase the MaxItemsInObjectGraph quota.
I looked, this appears hard coded into the MA, anyone know what causes this? My best guess is something like a large group membership? Does anyone know what the limits around the WAAD MA are?
Here is the indepth error logged during the failure:
ProvisioningServiceAdapter::ExecuteWithRetry: Action: Export, Attempt: 0, Exception: Microsoft.Online.Coexistence.ProvisionRetryException: Unable to communicate with the Windows Azure Active Directory service. Tracking ID: e94e6020-8434-4aa7-9a29-b2edf7fe6b2e
See the event log for more details. ---> System.ServiceModel.CommunicationException: There was an error while trying to serialize parameter http://schemas.microsoft.com/online/aws/change/2010/01:syncObjects. The InnerException message was 'Maximum number
of items that can be serialized or deserialized in an object graph is '500000'. Change the object graph or increase the MaxItemsInObjectGraph quota. '. Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException:
Maximum number of items that can be serialized or deserialized in an object graph is '500000'. Change the object graph or increase the MaxItemsInObjectGraph quota.
   at System.Runtime.Serialization.XmlObjectSerializerContext.IncrementItemCount(Int32 count)
   at WriteArrayOfstringToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
   at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at WriteSyncObjectGroupToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , ClassDataContract )
   at System.Runtime.Serialization.ClassDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeAndVerifyType(DataContract dataContract, XmlWriterDelegator xmlWriter, Object obj, Boolean verifyKnownType, RuntimeTypeHandle declaredTypeHandle, Type declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.SerializeWithXsiType(XmlWriterDelegator xmlWriter, Object obj, RuntimeTypeHandle objectTypeHandle, Type objectType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle, Type
declaredType)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerialize(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at System.Runtime.Serialization.XmlObjectSerializerWriteContext.InternalSerializeReference(XmlWriterDelegator xmlWriter, Object obj, Boolean isDeclaredType, Boolean writeXsiType, Int32 declaredTypeID, RuntimeTypeHandle declaredTypeHandle)
   at WriteArrayOfSyncObjectToXml(XmlWriterDelegator , Object , XmlObjectSerializerWriteContext , CollectionDataContract )
   at System.Runtime.Serialization.CollectionDataContract.WriteXmlValue(XmlWriterDelegator xmlWriter, Object obj, XmlObjectSerializerWriteContext context)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObjectContent(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.DataContractSerializer.InternalWriteObject(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dataContractResolver)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameterPart(XmlDictionaryWriter writer, PartInfo part, Object graph)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameterPart(XmlDictionaryWriter writer, PartInfo part, Object graph)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameter(XmlDictionaryWriter writer, PartInfo part, Object graph)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeParameters(XmlDictionaryWriter writer, PartInfo[] parts, Object[] parameters)
   at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.SerializeBody(XmlDictionaryWriter writer, MessageVersion version, String action, MessageDescription messageDescription, Object returnValue, Object[] parameters, Boolean
isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.OperationFormatterMessage.OperationFormatterBodyWriter.OnWriteBodyContents(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.Message.OnWriteMessage(XmlDictionaryWriter writer)
   at System.ServiceModel.Channels.BufferedMessageWriter.WriteMessage(Message message, BufferManager bufferManager, Int32 initialOffset, Int32 maxSizeQuota)
   at System.ServiceModel.Channels.BinaryMessageEncoderFactory.BinaryMessageEncoder.WriteMessage(Message message, Int32 maxMessageSize, BufferManager bufferManager, Int32 messageOffset)
   at System.ServiceModel.Channels.HttpOutput.SerializeBufferedMessage(Message message)
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Online.Coexistence.Schema.IProvisioningWebService.Provision(SyncObject[] syncObjects)
   at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel)
   --- End of inner exception stack trace ---
   at Microsoft.Online.Coexistence.ProvisionHelper.CommunicationExceptionHandler(CommunicationException ex)
   at Microsoft.Online.Coexistence.ProvisionHelper.InvokeAwsAPI[T](Func`1 awsOperation, String opsLabel)
   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.<>c__DisplayClass1.<Export>b__0()
   at Microsoft.Azure.ActiveDirectory.Connector.ProvisioningServiceAdapter.ExecuteWithRetry(String actionName, Action action).

Hi gdedshg,
>>Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota
When meet the above exception, please try to do the following configuration:
On the server side:
Add the following to the server's config file:
<behaviors>
<serviceBehaviors>
<behavior name="MyServiceBehavior">
<dataContractSerializer
maxItemsInObjectGraph="2147483647" />
</behavior>
</serviceBehaviors>
</behaviors>
And reference it in the service using the following code:
<services>
<service
behaviorConfiguration="MyServiceBehavior"
name="serviceName">……
On the client side:
Add the following:
<behaviors>
<endpointBehaviors>
<behavior name="MyClientbehavior">
<dataContractSerializer
maxItemsInObjectGraph="2147483647"/>
</behavior>
</endpointBehaviors>
</behaviors>
And reference it in the endpoint using the following code:
<endpoint address="serviceAddress"
behaviorConfiguration="MyClientbehavior"
For more information, please try to refer to the following article:
http://blog.aggregatedintelligence.com/2011/01/wcf-maxitemsinobjectgraph-error.html .
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Maximum number of items that can be serialized or deserialized in an object graph is '65536'.

I meet the this error:
Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota.
How to solve the above error?

Hi gdedshg,
>>Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota
When meet the above exception, please try to do the following configuration:
On the server side:
Add the following to the server's config file:
<behaviors>
<serviceBehaviors>
<behavior name="MyServiceBehavior">
<dataContractSerializer
maxItemsInObjectGraph="2147483647" />
</behavior>
</serviceBehaviors>
</behaviors>
And reference it in the service using the following code:
<services>
<service
behaviorConfiguration="MyServiceBehavior"
name="serviceName">……
On the client side:
Add the following:
<behaviors>
<endpointBehaviors>
<behavior name="MyClientbehavior">
<dataContractSerializer
maxItemsInObjectGraph="2147483647"/>
</behavior>
</endpointBehaviors>
</behaviors>
And reference it in the endpoint using the following code:
<endpoint address="serviceAddress"
behaviorConfiguration="MyClientbehavior"
For more information, please try to refer to the following article:
http://blog.aggregatedintelligence.com/2011/01/wcf-maxitemsinobjectgraph-error.html .
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

I use LabVIEW 7.1 but I have some problem when, I use LabVEW to read the data from serial communication

I use LabVIEW 7.1 but I have some problem when, I use LabVEW to read the data from serial communication.
I use LabVIEW to read the data from serial communication then, i open the example (.vi) from Serial Communication - Advanced Serial Write and Read from LabVIEW Example. BUT it have some error message that : Error - 1073807202 occured at property node in visa configure serial port (instr).vi -> advance serial write and read .vi
this error code is undefined. no one has provide a description for this code, or you might have wired a number that is not an error code to the error code input.
I don't know why? please help me. thank you.

When I copy that code into "Explain Error" I get: "VISA: (Hex 0xBFFF009E) A code library required by VISA could not be located or loaded."
You may have a bad install of VISA or the wrong version of VISA loaded. Try re-installing VISA. You can get the latest version from the NI support site: http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C0E91?opendocument&node=1....
Also ensure that you are not pointing the example towards a serial port that does not exist.
Please let us know what you find and what gets this working for you.
Rob

Windowsphone Emulator can't be installed

As I'm using VS Express 2013 to develop WP app, the Emulator can't be loaded. Then I clicked to install it, but an error appeared, which shows the requirement of the installation is 64bit edition Win8.1 pro and windows enabled Hyper-V. But my PC
meets all the requirement. Please help me fix it.

Hi,
Your issue is out of support range of VS General Question forum which mainly discusses
the usage of Visual Studio IDE such as WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
Now your issue is on Windows Phone Emulator, I suggest you to consult your issue on Tools for Windows Phone development forum like this thread:
http://social.msdn.microsoft.com/Forums/en-US/6dba40fa-7b21-4a36-a7fe-963b5c65f5a1/cant-start-the-windows-phone-emulator?forum=wptools
for better support.
Thanks,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Dsc modbus - Serial communication input/holding registers

Hello,
I am trying to create a labview application to act as a Modbus master and control multiple stepper motors. I have the DSC module in labview and am using a serial communication with an RS-485 converter. I have followed this guide: http://www.ni.com/white-paper/13911/en/ However, the driver I am using does not support coils, it only uses input and holding registers and I have not found a guide or tutorial that shows me how to create a labview application that can read and write to a specific address. For now all I want to do is turn the motor on and off using labview. I have used a modbus simulator to communicate with the driver and can do everything I want to do through the simulator. I can not get labview to do anything for me. I would be very happy if someone could direct me to a tutorial that can help me understand labview dsc module for reading and writing to addresses using modbus.
Meesh

Ok, so this is really strange. I solved my problem in a round about sort of way. I'm using a modbus simulator (mdbus) to help me communicate with the driver/stepper motor so I know which address to use. But after I use the simulator I get a communication port error when I try to use Labview. It's like the port is locked in with the simulator and I can't end the connection and let Labview use the same communication port. I can't find anyway to fix the problem except going to this NI site: http://www.ni.com/download/labview-run-time-engine-6.1/746/en/ downloading this software and using the "repair" function. Then I can do a system restart and cycle the power on the driver/motor and then Labview with work again through the correct port. But if I need to use the simulator again then I have to go through this whole process again. Does anyone know what the heck is going on? Or if there is a better way to clear the communication port??

Pocket Pc emulator can support serial communication

Similar Messages

Maybe you are looking for