Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    Receive data on lopy through serial

    Scheduled Pinned Locked Moved MicroPython
    seriallopy
    48 Posts 4 Posters 21.5k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      crumble @monersss
      last edited by

      @monersss said in Receive data on lopy through serial:

              f.write('data')
      

      remove the ' around data. You write the string 'data' multiple times in your file. You shall see this, if you open the file in a text editor. Remove the ' and you will write the content of your data variable.

      1 Reply Last reply Reply Quote 0
      • M Offline
        monersss
        last edited by

        @crumble no this is not a problem, i was actually trying to write anything to sd and it does not work, even when i try to write (data) i am getting 20 bytes once and than OSError Erro 5 EIO, so i am unable to write anything to my sd running script from Atom

        robert-hhR C 2 Replies Last reply Reply Quote 0
        • robert-hhR Offline
          robert-hh @monersss
          last edited by

          @monersss Try to get Atom out of the way, since it may introduce problems of its own. Use a simple a terminal emulator like putty or screen, copy your script to the target device usiong ftp and try it there.

          1 Reply Last reply Reply Quote 0
          • C Offline
            crumble @monersss
            last edited by

            @monersss

            1. Have you switched it off and on againt? Or better have you checked that SD card is formatted in FAT 16 or 32 and can be written by other devices?
            2. have a look on the pinout PDF. UART 1 and SD card handling seems to share the same pins. Maybe you cannot use UART 1 and SD card at the same time. Try to close the UART before writing to the SD card.

            Uh, I hope 2) is not the problem. Otherwise I will run with P10 into the same trap.

            robert-hhR M 2 Replies Last reply Reply Quote 0
            • robert-hhR Offline
              robert-hh @crumble
              last edited by

              @crumble If Pin conflict is the issue, one can reassign the UART Tx/Rx to other Pins, usign the uart.init() method https://docs.pycom.io/chapter/firmwareapi/pycom/machine/UART.html

              M 1 Reply Last reply Reply Quote 0
              • M Offline
                monersss @crumble
                last edited by

                @crumble unfortunately it was a pin problem, when connected to pins 21 and 20 as serial TXD and RXD data is stored on SD without any problem

                1 Reply Last reply Reply Quote 0
                • M Offline
                  monersss @robert-hh
                  last edited by

                  @robert-hh I have managed to read and write a jpg file using lopy and store it on SD after assigning different pins for uart.
                  When i try to do the same with the same jpg and store it on flash the file is being corrupted, number of bytes is different and somewhere in the middle of a file binary data are totally different then those of original file, i am using this code:

                  from machine import UART
                  import pycom
                  import time
                  from machine import SD
                  import os
                  
                  #sd = SD()
                  #os.mount(sd,'/sd')
                  #os.listdir('/sd')
                  
                  
                  uart = UART(1, baudrate=115200, pins = ('P21', 'P20'), timeout_chars=2000)
                  while True:
                      data = uart.read(25)
                      print(data)
                      if data != None:
                          with open('/flash/pliki/mon','ab') as f:
                              f.write(data)
                              f.close()
                  

                  What may be causing file corruption?

                  robert-hhR L 2 Replies Last reply Reply Quote 0
                  • robert-hhR Offline
                    robert-hh @monersss
                    last edited by

                    @monersss Flash is way slower than the SD, so jou are simply loosing data, because there is no flow control. For SD that works, because the firmware buffers some bytes, and that grants a time window for storing. AFAIK, the receive buffer is 256 bytes. Besides that, you code is highly ineffcient, because you open and close the file for every chunk of data. You could try it this way around:

                    from machine import UART
                    import pycom
                    import time
                    from machine import SD
                    import os
                    
                    #sd = SD()
                    #os.mount(sd,'/sd')
                    #os.listdir('/sd')
                    
                    
                    uart = UART(1, baudrate=115200, pins = ('P21', 'P20'), timeout_chars=2000)
                    with open('/flash/pliki/mon','ab') as f:
                        while True:
                            data = uart.read(25)
                            print(".")
                            if data is not None:
                                f.write(data)
                            else:
                                break
                    f.close()
                    

                    The f.close() is still there, but not needed due to the with... clause. The file system has an internal 4k buffer, unless that is full or the fiel is closed, nothing will be written. You should also not print the data, because that also consumes time. If that does not work, you'll need a handshake protocol between sender and receiver.

                    1 Reply Last reply Reply Quote 0
                    • L Offline
                      livius @monersss
                      last edited by livius

                      @monersss
                      You also can decrease speed of transmision e.g 9600
                      but the best is what we suggest you at start
                      you must of course have some protocol implementing.
                      especially you can send info with e.g. md5 hash of portion of data back and if this is ok send more if not then repeat...

                      think about people first, then computers

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        monersss @livius
                        last edited by

                        @livius tried with lower speed, result is the same. I have never written a protocol So i am not really sure how to do it..
                        Another thing is That i would like my lopy to stop reading data when the whole for example 20 kB file was received, how can i do that??

                        L robert-hhR 2 Replies Last reply Reply Quote 0
                        • L Offline
                          livius @monersss
                          last edited by livius

                          @monersss by protocol implementing we mean simple thing

                          1. you send command to destination "START_JPG"
                          2. you send back e.g. "OK" or "UNKNOW"
                          3. you send e.g 200Bytes of jpg + CRC(or MD5 or what you need to verify}
                          4. you read that data and calculate CRC and compare and you send back "OK" or "retry" or "cancel"
                            ....

                          all in your hand (look in google for e.g. handshake protocol)

                          think about people first, then computers

                          1 Reply Last reply Reply Quote 1
                          • robert-hhR Offline
                            robert-hh @monersss
                            last edited by

                            @monersss At the moment, with my example, that happens when you get a timeout. But again, that would require some "out-of-band" signaling, meaning: in addition to the "payload", the jpg file, some control information must be exchanged. And that is part of a protocol. That could be pretty simple. If I grab one out of the air, it could be:
                            Define record types, where the first letter defines the type of the record, followed by 3 bytes record length, followed by the payload, like:
                            'fnnn': filename (of length nnn)
                            'd128': data
                            'x000': done
                            You would first receive 4 bytes, decode type and length, and then receive further 'length' bytes. And for every record received, your LoPy would send a confirmation, like the three bytes: "ok!" or "bad", in case of errors (or just a single byte).
                            That would implement flow control and the EOF signal. It does not have other elements like check sums and sequence control. But you might not need that.

                            1 Reply Last reply Reply Quote 0

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            • 1
                            • 2
                            • 3
                            • 1 / 3
                            • First post
                              Last post

                            Pycom on Twitter

                            Pycom