Ankündigung

Einklappen
Keine Ankündigung bisher.

Making first setup work ...

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

    Making first setup work ...

    New thread to handle fluppies setup issues.
    Splitted from "Erfahrungsberichte"
    Zuletzt geändert von tuxedo; 07.04.2016, 09:37.

    #2
    Hi all, I'm sorry I can't write/speak German... I'm trying to compile the example for a Arduino Nano. I get the following error:


    In file included from C:\Users\Philippe\Documents\Arduino\libraries\Konn ektingDeviceLibrary1.0.0b2/KnxDevice.h:36:0,
    from DemoSensor_Temp_RH_KNXtest.ino:17:
    C:\Users\Philippe\Documents\Arduino\libraries\Konn ektingDeviceLibrary1.0.0b2/KnxTools.h:32:20: fatal error: EEPROM.h: No such file or directory
    #include <EEPROM.h>
    ^
    compilation terminated.
    Fout bij het compileren.


    Anyone has an idea what causes this? I just copied the library to my Arduino (v 1.6.5) libraries folder.

    Kommentar


      #3
      You're missing the EEPROM library... Check your library manager for EEPROM lib.

      regards,
      Alex

      Kommentar


        #4
        Hi Alex, the EEPROM library is a standaard Lib and is on my system: C:\Arduino1.6.5\hardware\arduino\avr\libraries
        Which version are you using with Konnekting?

        Kommentar


          #5
          We use the default. EEPROM.h.
          If it's available on your system, then I currently have no idea why it is not found ...

          Which Arduino IDE do you use? The one from arduino.cc or arduino.org?

          We use arduino.cc. Currently I'm using 1.6.7.

          Kommentar


            #6
            I tried 1.6.7 on my work laptop, looks like it's compiling! Tonight I'm going to try it out. I'll be using a Siemens 5WG1117-2AB12 and an Arduino Nano v3.

            Kommentar


              #7
              It should work with 1.6.5 as well. But if it's working with 1.6.7... just upgrade.

              5V or 3.3V Nano? The Siemens BCU is working with 5V level.

              br,
              Alex

              Kommentar


                #8
                It's this one: http://www.dx.com/nl/p/arduino-nano-...7#.VugFYdDVDGs working on 5V

                Kommentar


                  #9
                  That should work. Keep an eye on the used USB-UART-IC. We faced issues with an FTDI-replacement named "CH340G". With an original FTDI it works well.

                  Kommentar


                    #10
                    If it won't work I'll try my Atmega32U4 based funky module: https://harizanov.com/product/funky-v3/ it behaves like a 'miniature' Arduino Leonardo

                    Kommentar


                      #11
                      You can also try the ProMicro, either with 5V/16Mhz or 3.3V/8Mhz (same formfactor as Pro Mini)
                      https://www.sparkfun.com/products/12640

                      You get a compatible module for about 7eurs shipped from germany and for about 5eur shipped from china ... at ebay. Just search for "arduino pro micro".

                      Or if size does not matter, you can also go for Arduino Micro (same formfactor as Nano).

                      Kommentar


                        #12
                        Finally some time to experiment further. Compiling the arduino example is no problem. With the suite I have connection issues.

                        Code:
                        2016-03-30 23:28:32.264 INFO [main] de.konnekting.suite.Main.main: LaF Name: 'Metal'
                        2016-03-30 23:28:32.295 INFO [main] de.konnekting.suite.Main.main: LaF Name: 'Nimbus'
                        2016-03-30 23:28:32.311 INFO [main] de.konnekting.suite.Main.main: LaF Name: 'CDE/Motif'
                        2016-03-30 23:28:32.311 INFO [main] de.konnekting.suite.Main.main: LaF Name: 'Windows'
                        2016-03-30 23:28:32.311 INFO [main] de.konnekting.suite.Main.main: LaF Name: 'Windows Classic'
                        2016-03-30 23:28:32.483 INFO [AWT-EventQueue-0] de.konnekting.suite.Main.<init>: KONNEKTING Suite - Version 1.0.0-BETA2 Build 2016-02-23_19-57-37
                        2016-03-30 23:28:47.031 SEVERE [AWT-EventQueue-0] de.konnekting.suite.Main.<init>: Error creating knx access.
                        de.root1.slicknx.KnxException: Error connecting to KNX: timeout connecting to control endpoint /192.168.1.5:3671
                            at de.root1.slicknx.Knx.<init>(Knx.java:174)
                            at de.konnekting.suite.Main.<init>(Main.java:183)
                            at de.konnekting.suite.Main$16.run(Main.java:739)
                            at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
                            at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
                            at java.awt.EventQueue.access$500(EventQueue.java:97)
                            at java.awt.EventQueue$3.run(EventQueue.java:709)
                            at java.awt.EventQueue$3.run(EventQueue.java:703)
                            at java.security.AccessController.doPrivileged(Native Method)
                            at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
                            at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
                            at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
                            at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
                            at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
                            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
                            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
                            at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
                        Caused by: tuwien.auto.calimero.exception.KNXTimeoutException: timeout connecting to control endpoint /192.168.1.5:3671
                            at tuwien.auto.calimero.knxnetip.ClientConnection.connect(ClientConnection.java:188)
                            at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init>(KNXnetIPTunnel.java:131)
                            at tuwien.auto.calimero.link.KNXNetworkLinkIP.<init>(KNXNetworkLinkIP.java:142)
                            at tuwien.auto.calimero.link.KNXNetworkLinkIP.<init>(KNXNetworkLinkIP.java:180)
                            at de.root1.slicknx.Knx.<init>(Knx.java:167)
                            ... 16 more
                        EDIT:
                        I need to read... I had 2 VMware virtual network adapters. After disabling them I'm able to connect. Funny thing is that ETS5 has no problems to connect to the system with the adapter enabled
                        Zuletzt geändert von fluppie; 30.03.2016, 23:21.

                        Kommentar


                          #13
                          Can you please give some more details about this issue?
                          Is your suite running in an VMWARE Container? Or is it running natively on your vmware host?

                          Kommentar


                            #14
                            I have VMWare Workstation running on my WIndows 8.1 Laptop. I launch the suite natively under W8.1 .
                            The only thing I needed to do, to get it working, is disable the two virtual network adapters.

                            Kommentar


                              #15
                              Now I can load a device config XML. But after clicking parameter "temperatur" I get some errors: http://pastebin.com/WZ2fPBY8 or http://pastebin.com/raw/WZ2fPBY8

                              Kommentar

                              Lädt...
                              X