Compact rio bloquer l'accès aux autres utilisateurs du réseau
Bonjour,
Notre école s'est équipée de système CompactRIO 9076 ainsi que de module analogique et numérique.
Tout les systèmes sont connecté au réseaux de l'école via câble RJ 45.
Ils possèdent tous une adresse IP personnel.
Notre problème est que toutes les personnes connectées au réseaux ont accès via adresses IP à TOUS les compactRIO.
Prennons un exemple: Si une personne travail sur un compact rio aux modules de sortie numérique, en me rendant sous gestionnaire de système distribué et en sélectionnant l'adresse IP de la personne (sous élément du réseaux), je peux contraindre ses I/O et donc modifier complètement son système.
Ma question est : Il y a t-il un moyen d'empêcher l'accès à toutes autres personnes que l'utilisateur travaillant sur le système de modifier les E/S de modules ?
Merci d'avance et salutations
Bonjour Nosmoglia,
Il vous est possible de limiter l'accès depuis un client FTP à vote matériel de la manière suivante :
http://digital.ni.com/public.nsf/allkb/21928AC49FB2379C86256BF4006307AD?OpenDocument
En ce qui concerne le gestionnaire de systèmes distribués, il est possible de créer un compte pour se connecter. Il est accessible depuis Actions-->Se connecter.
Veuillez trouver le lien suivant pour plus d'informations.
http://zone.ni.com/reference/en-XX/help/372572E-01/sysman/sm_securitylogin_db/
Cordialement.
Paolo_P
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France
Similar Messages
-
j'ai acheté et donc payé 34.90€ pour la saison complete de the mentalist saison 6 et je n'ai pu télécharger que les 3 premiers épisodes. Comment faire pour télécharger la totalité sachant que lorsque je vais dans le menu store on me dit que seuls ces 3 épisodes sont disponibles....
Bonsoir,
Merci pour votre réponse rapide.
Je n'avais pas pensé au moteur de rendu !!! La différence entre LR 3.5 et 4.0 ne concerne effectivement pas que les fonctionnalités.
Et du coup, vous avez tout à fait raison, il me faudra tout reprendre en rentrant pour pouvoir en bénéficier.
Autrement dit, LR 3.5 ne me servira que pour avoir un aperçu des clichés pris et pas pour faire le vrai travail de développement. Ce qui veut dire que si je n'ai pas le droit de l'installer je pourrais toujours me tourner vers une autre solution (logiciel libre par exemple) qui me permettra de faire la même chose.
Merci pour votre remarque qui m'a bien éclairé.
Laurent -
Existe-t-il un moyen de verrouiller l'accès aux réglages de l'ipad uniquement ?
Bonjour,
En cas d'utilisation de groupes, existe-t-il un moyen de bloquer par code l'accès aux réglages de la tablette ?
Nous avons mis des restrictions avec un code mais n'importe qui peut toujours accéder aux paramèttres et décider de mettre un code de verrouillage sur la tablette... Il nous faudrait pouvoir limiter l'accès aux réglages par un mot de passe, un code...C'est peut-être inexactes, mais je suis en utilisant Google Translate.
Est-ce que vous utilisez les périphériques via le configurateur? Si c'est le cas, il n'existe aucun moyen pour empêcher un utilisateur d'ajouter un mot de passe, mais vous pouvez le réinitialiser en branchant l'appareil en l'essuyant sans. -
Communication Compact RIO et Touch Panel
Bonjour,
Je suis face à un petit problème qui pourrait devenir génant.
Je dois faire communiquer un Touch Panel avec un Compact RIO de manière autonome (sans PC).
Jusque là, pour la programmation, j'avais connecté mon PC, le Touch Panel et le compact à un hub ethernet, et cela me permettait d'envoyer les programmes correspondant, sur le Touch Panel et le Compact RIO via le PC de développement, et de tester si le Touc Panel et lme compact RIO communiquaient bien ensemble. Jusque là pas de problème tout fonctionne. Mais lorsque je déconnecte le PC du hub (et donc du réseau, ce qui sera la configuration finale = juste une relation entre le compact RIO et le Touch Panel), la communication ne se fait plus!!!!
D'où vient ce problème? Est ce qu'il faut une configuration spéciale des switchs du Compact RIO pour qu'il communique de manière autonome avec le Touch Panel?
Merci d'avance pour toutes vos réponsesBonjour,
En effet, la configuration du CompactRIO ne pourra se faire que sur le port 1. En revanche, il doit être possible d'établir une communication entre le Touch Panel et le cRIO par le second port.
Vous trouverez aux liens suivants les infos nécessaires sur l'utilisation des doubles ports:
Introduction to Dual Ethernet Architectures
Getting Started with Dual Ethernet Port Real-Time Controllers
Guide du développeur CompactRIO
Cordialement,
Olivier L. | Certified LabVIEW Developer -
Error 1335 When Installing Compact RIO Module Software 2.1.4 From Hard Drive
I’m having issues with the installation of the CompactRIO Module Software 2.1.4.
Initially, problems were occurring when trying to communicate with the device, as it was denying access to it from the Development PC. Various things were tried such as adding a ‘*’ to the fields and making sure 'Allow' was selected in the communication properties on LabView RT. This didn't seem to work. A post relating to our problem is here: http://forums.ni.com/ni/board/message?board.id=170&message.id=269809&query.id=18752#M269809
As none of this was working, we decided to format the disk on the Compact RIO and reinstall the software to it. The software downloaded from Ni.com was the CompactRIO Module Software version 2.1.4 (dated May 2007). This file was unzipped using WinZIP 9.0 (on a PC running Windows XP Pro SP2 5.1.2600) and then transferred with a USB stick to the Development PC.
We attempted to install the file on the Development PC (running Windows 2000 SP3 5.00.2195) by running setup.exe. This started normally, but then proceeded to come up with an error message saying: ‘Error 1335. The cabinet file ‘Cabs.w1.cab’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.’
Attached are screen shots of the error message that appears.
As a result of this error, the installation could not be continued and the module software was not installed.
What is going wrong with the installation and how can I go about sorting it out?
Thanks very much,
Moses
RT target cRIO-9012, NI-RIO 2.1.3, LV 8.2, RT 8.2, FPGA 8.2, host ip 150.150.10.15, cRIO IP 150.150.10.4
Message Edited by Mohoyt on 09-10-2007 04:03 AM
Attachments:
Error Message CRIO Module 2.1.4.JPG 36 KBWay,
Thanks for the help overall, I finally worked it out. The problem was initially present in the unzipping of the original archive that had been downloaded from the NI.com website. When I had previously unzipped it, I had done so to a network drive which for some reason stopped autorun.inf and autorun.exe from functioning properly and so when I tried to install it on the Dev PC I got the aforementioned error. To overcome this problem I unzipped it to a local drive and (surprise!) there were no faults, so when installing the actual software, no errors appeared and it was installed correctly.
This however was not the only problem, the version that had now been installed did not want to co-operate with the RIO at all, and came up with various software errors in addition to not having all of the available software modules for the RIO available to install. The solution was then to install the newest RIO software, which is very badly labelled on the NI.com website by the way (its packaged as RIO software, so if you're looking explicitly for CRIO software you've got no chance of finding it). The newest version, 2.3 (Aug 07) as opposed to the 2.1.4 (May 07) that I was previously trying, worked fine and I was able to get all the software modules installed. So for now the problem is solved!
Thanks again for all the help.
Cheers,
Moses -
Build real-time application with Compact RIO
Good afternoon,
I am currently trying to run a VI on compact RIO and would like to control it through remote front panel. I followed steps on this link http://digital.ni.com/public.nsf/allkb/AB6C6841486E84EA862576C8005A0C26 and successfully done everything with a simple example.
However when I moved on and did the same thing to a more complicated VI (my purpose is to make this VI work), everything was fine until I reboot the compact RIO. After a few seconds connection lost between the host computer and cRIO, and I had to shut it down and delete the startup file (with extension .rtexe).
I am not sure what happened since everthing works fine with simple VI but not the complicated one. It could because the second VI has many sub VIs as well as objective functions loaded in it, it could also because the VI takes too much memories of the CRIO and stop it from connecting to the host computer.
If anyone have any ideas of how to make it work please let me know.
Thanks very much
CarlHello zzzfreedom,
There are a number of potential issues I can see with the VI you're trying to deploy as a startup executable. How do you intend to interact with this VI? Are you running the front panel as a remote panel or connecting to the VI using debug tools? A few points:
- Your VI will run immediately when the RIO boots unless you're using debugging tools to prevent this from happening, keep that in mind. It looks like you've accounted for this and required an initialize or network trigger of some sort for some of your loops, but the AI loop will start quickly and appears that it may require user input.
- You have several "user prompt" style express VIs. These will not work (or will not work as expected) on a standalone RT target. There is usually no front panel to interact with!
- Like dialogs, event structures watching for user interaction probably aren't going to do what you want.
- You are writing quite a bit of data to the VI's front panel, and there is at least one chart indicator. Again, how will the user interact with this VI? It looks like you need a host VI that will run on a machine the user will interact with.
- You're using quite a few local variables. It looks like you've taken a lot of care to protect against race conditions, but this causes a lot of data copies and tends to be error prone.
- I've not analyzed all cases, but it looks like you have a number of places where the execution of a timed loop may be blocked under certain conditions. This will likely rail the CPU due to the much higher priority of the timed loops.
- What will happen if you lose connection with the server in your TCP command loop? it doesn't look like there is any way for the user to reconnect without restarting the RIO.
If you do intend to run this as a remotely accessible VI on your RT target, another point to note is that when running from the development environment, the front panel of your VI executes on the host machine. Once you deploy it as a remote front panel or debuggable RTEXE, everything is hosted on the RIO, and this has the potential to bog things down quickly.
Here are a few references I think you might find helpful:
LabVIEW Help: Real-Time Operating Systems - see considerations for Express VIs and Front Panel interaction
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_osnotes/
LabVIEW Help: Real-Time Module on VxWorks Targets - see unsupported features
http://zone.ni.com/reference/en-XX/help/370622L-01/lvrtconcepts/rt_vxworks/
NI LabVIEW for CompactRIO Developer's Guide -lots of good general information on architecting RT applications, network communication and hosts, etc. It looks like you're using the RIO Scan Engine, so the FPGA portion might not be relevant at this time.
http://www.ni.com/compactriodevguide/
Best Regards,
Tom L. -
Compact RIO and LabVIEW run time
Dear All,
Good Morning.
We are developing a new experimental setup which will have different components, such as mass spectrometer, pressure transducers, valves and thermocouples, RTDs. We are currently having LabVIEW 8.6 Run time. We would like to control different components and acquire data using CompactRIO. I am not clear if compact RIO works with 8.5 run time. In the developers guide NI, mention about the real-time LabVIEW.
Thank you very much for help,
ZachYou need the Real-Time Toolkit (and possibly the FPGA toolkit, depending on your needs) to work with the cRIO. The version of LabVIEW installed on the cRIO must match the version you're using for programming on the PC (so you can't have LabVIEW 8.5 on the cRIO and 8.6 on your computer). The LabVIEW Real-Time is not the same as the LabVIEW Run-Time engine. The Run-Time engine lets you run compiled applications on your computer. The Real-Time toolkit lets you program real-time targets such as the CompactRIO.
-
R series intelligent DAQ, NI-Compact RIO , NI single board RIO
Hi,
I'm in the phase of choosing an FPGA to use in programming some DSP modules. The thing is that while I'm reading about the different technologies to be used, I find it difficult to know how will these devices be connected to my PC and programmed. For example, when using R series intelligent DAQs, do I have to get a compact RIO as well , or can I get a PCI-bus R - DAQ and connect it to the PC.
Some clarification of how to use each of these devices will be appreciated.
Thanks,
WalidJust to elaborate on what Venkatesh said
With a compact RIO you will connect your PC to the RIO using Ethernet, direct through a cross over or through a network hub.
This introductory video will teach you how to install, configure, and program the latest NI CompactR...
A PCI R series card, just plugs straight into your Windows computer PCI slot.
A PXI card will plug into a PXI chassis and will give you one of 2 programming options
1. If you have a PXI system controller running Windows XP with the appropriate drivers and version of LV you can program the FPGA directly in the PXI chassis
2. You can connect to the PXI chassis through Ethernet and program the FPGA from there.
Compiling and deploying your program will work the same no matter what connection you use.
-Hunter -
IMAQ FFT multiplication and MATLAB Script Nodes/Compact Rio
I would like to automatically generate a frequency kernel to multiply with the FFT of my IMAQ image. I was wondering if there was a way for LabVIEW to automatically set up 2D arrays (with a lower bound, a step size and a higher bound) like what is done in MATLAB.
I was wondering also, if someone could give me some insight as to what restrictions I face, when uploading code from MATLAB script nodes into the Compact RiO (I have a cRiO-9025).Hi Bilaln,
I think you confused about a MATLAB script node and a Mathscript node.
A MATLAB script nodes uses ActiveX to call into MATLAB, where as a Mathscript node runs in a NI built environment. The MATLAB script node requires both that MATLAB be installed and the host supports ActiveX. Since cRIO does not do either, you should use the MATHSCRIPT RT module.
Joe Daily
National Instruments
Applications Engineer
may the G be with you .... -
Reactivar compact rio en max por red
Saludos a todos!!
espero me puedan ayudar..
realicé un reinició del MAX en mi pc ya que marcaba algunos errores, por lo cual se borraron todos los registros y todas las tarjetas y módulos que estaba utilizando. ahora quiero volver a integrar el modulo compactRIO-9074 que ya tenia por medio de la IP. pero al momento de intentar agregarla, primero con el hostname dice "Unable to initialize connection to remote target(s)" y por medio de la IP me dice lo siguiente "The device at this adress is not supported by the drives installed on this host". solo puedo aclarar que mi pc requiere permisos de administrador para todas las instalaciones, ademas no he desinstalado drivers ni nada por el estilo. solo realice el reinicio del MAX debido a los problemas que presentaba. el compact rio sigue con su misma IP ya que puedo monitorearla por internet. espero me puedan ayudar con esto. gracias.
Rene Eduardo Guerrero Recio
Ing. Electrónico
COMIMSA, Saltillo.Buenos días Reno32
Le puedo platicar lo siguiente en relación a los dos mensajes que le arroja MAX al momento de conectarse por medio de "Remote Device (not on the local subnet)"
"Unable to initialize connection to remote target(s)"
Este problema se debe a que la computadora no se pudo conectar con el dispositivo, ya sea que por que la IP ingresada sea incorrecta o bien que el firewall de la computadora pudiera estar interfiriendo con la comunicación.
"The device at this adress is not supported by the drives installed on this host"
Este problema pudiera estar ligado con los drivers. Cuando trabajamos con un dispositivo en tiempo real, tanto el modulo de Real Time instalado en la computadora, y el software instalado en el controlador, deben de ser de la misma versión.
Como troubleshooting me gustaría preguntarle
- Que módulo de Real Time es con el que esta trabajando ?
- Que versión de LabVIEW es la que esta utilizando ?
- Que versión de NI RIO tiene instalada ? (esta la puede revisar en la pestaña de software dentro de MAX)
- Cuando menciona "el compact rio sigue con su misma IP ya que puedo monitorearla por internet", Qué herramienta esta utilizando para monitorearlo? o bien le aparece debajo de Remote Systems ?
Como recomendación le puedo sugrerir:
- Asegurarnos que el firewall del computador se encuentre desactivado.
- Conectar directamente el cRIO a la computadora de desarrollo por medio de un cable Ethernet (en caso de que no este conectado directamente).
- Colocar la computadora de desarrollo en la misma red que el controlador, e intentar reconocerlo en MAX.
- Si es posible agregar el controlador en MAX, actualizar el software del cRIO para asegurarnos que la versión de drivers instalada en el cRIO coincida con la versión del Módulo de Real Time instalada en la computadora.
Como referencia puede seguir los pasos de la página 6 'Installing Software on and Configuring the Controller' del manual de Getting Started
http://www.ni.com/pdf/manuals/372596b.pdf
o bien tomar como referencia el siguiente video
https://www.youtube.com/watch?v=ksaeXq84PAg
Espero que esta información le resulte últil. Estamos a sus órdenes.
Omar R.
Applications Engineer -
I can't save my report in the path that I want. The VI is running in
the Compact RIO y this is the path that it shows c:\ni-rt\startup\.
What
I think is if the VI is running in the RIO, so it is triyin to save the
report in the RIO and I don't accept paths from my laptop.
How can I save the report in my computer??
RegardsYou are absolutely right. The file I/O is happening on the cRIO since the application is running on the cRIO. You have two options over here. The first would be to save the data on the RIO and then transfer the file over to the host. The second, the recommended one, would be to transfer the data to the host where the data can be logged. There are seven network communication methods outlined by LabVIEW 2009 Real-Time Module Help: Exploring Remote Communication Methods (RT). There are also APIs based on the above methods that may simplify the transfer overhead. An example is the Simple Messaging Reference Library (STM). If you have any follow up questions, post back!
This might be helpful to you:
Best Practices for Target File IO with LabVIEW Real-Time
Message Edited by Adnan Z on 01-29-2010 07:29 AM
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies -
Can i use C Code at Compact Vision or Compact Rio?
hi,
i have a very important question!!
can i use the C code that the Vision Assistant generates, in the compact vision system, even in DLL form??? if yes, how can i download it to the compact vison?
can i use C code at the compact rio?
greets,
geraldYou can use C-Code on Realtime targets (Such as C-Rio or a Compact Vision system) as long as you compile a DLL out of it, and call this DLL from LabView. Take care that no Windows-Specific things are in the dll (MFC, ActiveX, Windows SDK etc.).
As you always need LabView, to use the dll, it would be better to create a LabView VI from the Vision Assistant, and download this VI to your Compact Vision System. -
Referenced Parameters in C library not working on Compact RIO
High level
I want to use Google Protobuf on my Compact RIO. I have it 90% of the way there and running into issues.
Details
I'm a long time C++ developer who's newish to LabVIEW. I'm using C to create a cross-compiled library to use on a Compact RIO (9025) with LabVIEW code. I'm using Linux (Ubuntu 14.04.1) with a VxWorks toolchain and CMake to create the library. I copy it over manually (looking for a better solution to that here), call it from LabVIEW via a Call Library Function, and assuming I'm doing simple things it works great! Here's a quick sample of what I have that works:
My C code
extern "C" double addNums(double in1, double in2)
return in1 + in2;
extern "C" double multNums(double in1, double in2)
return in1 * in2;
Which I cross compile to a VxWorks binary and copy over to the cRIO.
Then on the LabVIEW side, I have this.
I run it on the target cRIO and all works great.
I mentioned protobuf. Cross compiling the full blown protobuf library for VxWorks proved to be a near (if not 100%) impossible task. So I found and am using Nanopb. I'm able to cross compile and get the following code using Nanopb to actually run on the cRIO and spit out the expected response:
extern "C" double testPbuf()
uint8_t buffer[128];
size_t message_length;
bool status;
std::ofstream file;
file.open("testOutput.bin", std::ios::out | std::ios::binary);
//! Create a message
ExampleMsg message;
message.value = 13;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
status = pb_encode(&stream, ExampleMsg_fields, &message);
//! Decode the message
ExampleMsg message;
pb_istream_t stream = pb_istream_from_buffer(buffer, message_length);
status = pb_decode(&stream, ExampleMsg_fields, &message);
return message.value;
return 0;
Not terribly important, but if you know protobuf, here's the proto message I'm using
message ExampleMsg {
required int32 value = 1;
So then I call this function from LabVIEW very simply:
I run this and it works! I see my 13 as expected. Jump for joy, protobuf works on the Compact RIO! Ok no jumping yet...
Now what I want to do is get the C library to generate and output the actual serialized protobuf message because I need to send it over UDP from the Compact RIO. So here's my attempt so far:
extern "C" const void getPacket(uint8_t* packet)
uint8_t buffer[128];
uint16_t packetSize;
bool status;
ExampleMsg msg;
pb_ostream_t stream = pb_ostream_from_buffer(buffer, sizeof(buffer));
msg.value = 14;
status = pb_encode(&stream, ExampleMsg_fields, &msg);
packetSize = stream.bytes_written;
//! If something failed we should see an 'X' in the first byte
if (!status)
buffer[0] = 'X';
memcpy(packet, buffer, packetSize);
And on the LabVIEW side, I'm initializing an array of unsigned int 8s to the proper size and feeding it into the function, and reading the packet parameter as output.
When I run this I never get any output on packet except whatever I set the initializer to. I have also changed the code to try to output a string as a parameter argument, with this declaration:
extern "C" const void getPacket(char* packet)
And memcpy() appropriately and can't seem to get the output properly in LabVIEW using strings in place of the U8s. I need to figure out how to get this serialized protobuf data into LabVIEW so I can send it over UDP as a message.
I have seen several examples in the LabVIEW installation directory, but they're referring to objects and libraries which are meant for Windows DLLs and not easily used in a cross compiled environment. I also have seen many threads on here relating to this but none have helped so far. Any help would be greatly appreciated!
I would hate to do a file write to solve this as it would add a whole new lag to the system. I did end up with a solution, which is essentially what I posted above. It seems like the real issue I was having was that the dll was not being reloaded on subsequent rebuilds/tests. So I would make changes to the DLL to test and they wouldn't be reflected even when I copied the DLL to the Compact RIO. Turns out I have to completely close the project and re-open it if I change the dll file. This is really strange behaviour. I could even *delete* the DLL from the Compact RIO and the VI would still run with the previous "copy" somehow.
Anyhow it looks like I have protobuf working from the Compact RIO, though still have a few issues with encoding certain data types. If anyone is interested in the full solution I may do a write up. -
How can I control 4 sets of compact RIO system with my host PC?
Hi all,
As the title.
I want to control 4 sets of compact RIO system at the same time.
I have written TCPIP connection for two PC before.
But I never program to connect more than one PC.
If I need to connect more than one PC, should I set the PC's connection port different?
Could you provide me an example?
Thank you a lot.
Solved!
Go to Solution.Hi StephenCh...,
you can calculate the transfer rate it depends on your network card. You'll find very good examples on that in the example finder, search for tcp/ip. You can use the server code on each of your cRIOs. Use the client to connect to your servers (cRIO), you only need to change the IP. If you need to connect to all at the same time, then you have to change the client program a bit, so that you are able to build four connections.
Where do you have problems? Did you already see the examples?
Mike -
Deploying exe into compact rio
Dear Labview Users,
We are using compact rio 9002 and labview 8 version. We made a program to acquire the data through 9215 module, doing some calculations and transmitting to radio through serial port. My problem is, I want to deploy this program permanently into the compact rio, because when power goes and comes the program must start automatically without human intervention.
For this I tried the procedures given in our NI site, but the problem we facing is when we switch OFF and ON the program doesn't start automatically. When we rebooted it by software and reset manually then only its working. But I want this is to rectified, Can anybody help me by providing solution to the same.
Labview LoversShivkumar,
1st: Include the bitfile as supported file to the application (the step before is to add the bitfile to the project)
2nd: If you have finished the configuration make a right click on the application and choose "Set as Startup"
3rd: Afterwards make a right click one more time and click Build and then Download
BR,
ThSa
http://www.newgistics.com
Maybe you are looking for
-
Promoto to OD Master - errors in slapconfig.log and slapd.log
After a lot of promoting to OD Master and demoting to Standalone I have finally a OD Master that seems like it's working. At least I can bind my clients to it and then (after reboot of the client) work with networked home-dirs Smile. BUT I have a cou
-
Search Help for custom data element
Hi experts, I have a small question regarding accessing data on different clients. Can I have an abap program where I can make reference to data /tables in different client AAA, assuming the system (AAA) with data is logically connected to the cl
-
NcSetAttr not working when setting Transmit mode
I am using a NI-USB 8472 (low speed CAN @ 33333kbps) device and am trying to set it up for the wakeup mode which states in the devices spec that it has this capability. However, attached is the quick test code that returns and error when using the n
-
Gurus, If i am maintaining split valuated material in 2 storage location,can i run the MRP for one.Can i run it thro MDBT. Edited by: acapulcosdn on Jul 3, 2010 11:53 AM
-
Real Player is not working properly.It downloads videos but when I click "play" ,it doesn't reproduce the video. I tried resetting Real Player but nothing happens. It worked fine up until a couple of dyas ago. What can I do?