Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


pcorcoran last won the day on January 28 2018

pcorcoran had the most liked content!

About pcorcoran

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

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

  1. Hello Erwan, Thank you for your message. What do you see after importing the data files into Symphonie Data Retriever and then pressing Events? The Event log should show if its the SD card (MMC Card Failure) or if it's the logger itself is having issues (Reboots). My suggestion would be to try a new SD card and see if that helps. Feel free to send the last week's worth of data files to us at support@nrgsystems.com. Thank you, Pearse
  2. Additionally - if the North notch of the sensor is 160 degrees then the offset should be 160. Slope = 0.351 Offset = 160
  3. Hello yutthasak, Thank you for your email. You should be able to use a W200P on a SymphoniePLUS data logger just like you would use a NRG 200P. It can be placed on channels 7-8 without a SCM card, or on 9-12 with a #3152 200P SCM card. You should be able to use the slope of 0.351. The offset will be based on the direction that the North mark is pointing. Please reply with any questions or email us at support@rngsystems.com. Thank you! Pearse
  4. An additional pieces of information regarding this topic: If replacing or reformatting the SD card does not fix the iPackGPS.RWD issue, then the logger needs to be replaced. The iPackGPS.RWD files are the result of the iPackGPS being unable to pull the data file from the logger. Often this is because the SD card is corrupted and the iPackGPS cannot find and pull the right data file, and send the iPackGPS.RWD in place of the valid data file. If the SD card and been replaced and the issue continues then the iPackGPS is having trouble navigating through the logger to the SD card. This indicates that the logger is damaged and needs to be replaced.
  5. Hello Ryan, Thank you for your post. My colleague who is highly qualified to answer this question is currently out of the office. I've forwarded your question on to him and hope to have a response for you shortly. If you don't hear from us by the middle of next week shoot an email over to support@nrgsystems.com. Thank you! Pearse
  6. Hello Nicolas, Thank you for your post. The behavior your describing will happen when the data files are encrypted, or when they are corrupted. In this case it sounds like there might a little bit of currpution in the file, which is causing the CRC message. Sometimes we are able to remove the corruption from the files. Please send us some of these files at support@nrgsystems.com and we'll take a look. Thank you! Pearse Technical Services
  7. Hello, Thank you for confirming the battery voltage. It sounds like the driver has been installed properly considering COM3 shows up in the Symphonie Data Retriever application. The DB9 to DB25 cable does not require its own driver. It is starting to seem like the iPack itself might be damaged. Do you have another iPack available that you know is working and can use to test the connectivity of the cables? Let me know what you find, Pearse
  8. Hello, Thank you for your reply. If moving the sensor to a different channel fixed the performance issue, then it is safe to assume that the logger channel is damaged. Does the logger have an iPack Voltmeter SCM card installed on it? If so, is the iPack battery voltage above 10.5 v DC? If the iPack battery voltage falls below 10.5 v DC the logger and Symphonie Data Retriever (SDR) application might not be able to connect to it. This should be ruled out before proceeding. 7.07.06 is the current version of SDR. There should not be a problem with the software itself. Sometimes getting USB to Serial Adapter cables to work can be challenging, especially if the cable is not a brand that we know. I suggest looking up the manufactures website and checking to see if they have a driver you can download for the cable. Then install the driver and confirm in Windows Control Panel that the device has been properly installed. At that point you should be able to open SDR, go to 'Site' and choose 'Modify iPack Settings'. From there go 'Options' and choose 'Comm Port'. Click on the drop down and select the available COM port. Close the window and you should be able to connect. Click on the image below to see a quick .gif of the process: Please let me know if this works. Pearse
  9. Hello, Thank you for your email. If the voltage output of the sensor is logical, then it is fairly safe to assume that the sensor is working properly. Moving the sensor to another channel would be the next logical option. If possible bring a spare 110S Temp Sensor SCM card with you in case the current SCM card sustained some damage. Generally speaking, if the sensor is okay then the next likely culprit is the logger's wiring panel. Moving the sensor to a different channel will verify if the channel is the effected part. Usually the SCM cards don't get damaged but it can happen. Let us know what you find. You can always email us at support@rnrgsystems.com. Thank you! Pearse
  10. Hello, Thank you for your email. I'm not sure exactly which App Note you are referring to, although I think it's the "Technical Background Supporting Removal of the Lightning Ground Wire on NRG TallTowers". The document gives RNRG's reasoning in not recommending down tower ground wire anymore. I'm afraid I cannot give you any advice regarding the third party wind turbine because I don't know anything about it. I would check with the manufacturer and see if they have some sort of schematic or standard installation guide for the turbine. Let me know if you have any questions by emailing support@rnrgsystems.com. Thank you, Pearse
  11. Hello Dave, Thank you for your post. There are many ways to extract data from an email account like Outlook. I know a number of customer's who also use scripting and rules to manage their data files. I don't see any problems with this method, so if it works for you then keep at it! Pearse
  12. Hello, Thank you for your email. Symphonie Data Retriever can be called up via command line and run in 'Silent' mode. More information can be found here: https://www.renewablenrgsystems.com/services-support/documentation-and-downloads/app-notesinstruction-sheets/detail/automation-of-symphonie-data-retriever. Let us know if you have any questions at support@rnrgsystems.com. Thank you! Pearse
  13. Hello Dmitry, Thank you for your post. It sounds like the data files have been corrupted somehow. Please send them to us at support@rnrgsystems.com and we'll see if we can correct them and identify the cause of the issue. Sincerely, Pearse Corcoran Technical Services
  14. Thank you for the update Sebastián! Please let me know if anything else comes up. Pearse
  15. Hello Sebastián, Thank you for your reply. Looking back at your email I see the iPack serial number was listed as 716900147. This serial number belongs to an iPackACCESS unit. These iPacks are thicker then GSM and CDMA iPack (similar to a Satellite iPack). The iPackACCESS is used to transmitting real time data through a network via MODBUS protocol. I think the iPackACCESS is unable to connect to the logger in the field is because of the model of that unit. The office logger is a SymphoniePLUS3, which is compatible with iPackACCESS. If we can find out the serial number of the logger in the field by guess is that it will be a Symphonie (serial number starting with 3090...) or SymphoniePLUS (serial number starting with 4280...). Neither of these iPacks are compatible with the iPackACCESS. Do you have any data files from the logger in the field? I can use that data file to confirm the serial number of the logger. Please send a couple 14 kb data files from the site to us at support@rnrgsystems.com and reference this post. Thank you! Pearse
  • Create New...