Announcement

Collapse
No announcement yet.

VDI-RODERICO

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hello! I finally got this set up. I flashed the controller, inserted it into the socket, applied power and ... and nothing. The display shows nothing. The contrast is adjustable, but there is no indication. The display is serviceable --- stood on the Turkish VDI DM-1. It seems that PIC18F25K22 does not start. All voltages are present, the parts are in good condition, the installation has been checked several times. Where else to look, I have no idea. The archive contains the firmware that was flashed, a diagram, a printed circuit board drawing and screenshots from PicKit3. Thanks!
    Attached Files

    Comment


    • Did you check with an O'scope PIC output pins to display and see if they toggled when powering the PIC?
      Did you adjust the display Contrast?

      Looks like the jumper wires above the PIC may be SHORTED. Ensure they are NOT touching (should have had insulated wire for the long ones).

      The code should be using the Internal PIC Oscillator. This is set in the 'CONFIG1H' bits.
      Code:
      // PIC18F25K22 Configuration Bit Settings
      
      // 'C' source line config statements
      
      // CONFIG1H
      #pragma config FOSC = INTIO67   // Oscillator Selection bits (Internal oscillator block)
      #pragma config PLLCFG = OFF     // 4X PLL Enable (Oscillator used directly)
      #pragma config PRICLKEN = ON    // Primary clock enable bit (Primary clock enabled)
      #pragma config FCMEN = OFF      // Fail-Safe Clock Monitor Enable bit (Fail-Safe Clock Monitor disabled)
      #pragma config IESO = OFF       // Internal/External Oscillator Switchover bit (Oscillator Switchover mode disabled)
      The PICKit3 shows this to be 0x2800 which is correct to enable 'internal oscillator'.

      Code seems good so check first items I list.
      Attached Files

      Comment


      • I checked the jumpers first of all --- there are no short circuits, all tracks were viewed under a magnifying glass and rang by a tester. Everything is great. The contacts in the PIC socket are also good. And, here's where to look with an oscilloscope (on which pins) and what should I see there? For example, on pins OSC1 and OSC2 should there be an internal oscillator frequency (4MHz, sort of) or not?

        Comment


        • With the Internal oscillator there is not a clock on the pins (9&10). See figure 2-1 in the PIC data sheet.

          Only pins I would check are the PIC pins to the Display.
          These should output commands and data to the display upon power up or RESET (SW1).
          Check the Display pins, EN, RS, RW, CS1 & CS2 as well as data pins, DB0-DB7. Some/most of these pins should have activity.

          Have you ADJUSTED the CONTRAST Pot??? These displays will show nothing unless the contrast adjustment is just right.

          Comment


          • Good day! I took measurements with an oscilloscope --- nothing ... There is no signal on any of the outputs ... none at all, only noise. There is only voltage. It seems that the PIC does not start at all. The reset circuit is working. The contrast is adjustable in a wide range, but the display is empty ... Anyway, to hell with it. I'll put it in the archive --- harvesting is starting now, I have to go to the dig. I apologize for wasting your time and thank you for your willingness to help.

            Comment


            • I would replace one of the jumpers that looks like they are touching with a wire as waltr suggested, but if everything is fine I think it might be the display, could you post a picture of the back of the display or do you know the model? It looks like a clone of KS0108 if so you would need to use VDI_S6B0108_P18F26K22.hex instead of VDI_KS0108_P18F25K22.hex or it won't work, could you give it a try?

              Comment


              • Roderico,
                Shouldn't he see some activity on the Display control pins when resetting the PIC?
                That was the only way I could think of to determine if the PIC is actually running code.

                I was thinking he didn't have a good display but want to check that the PIC was running first.

                Comment


                • Hello Roderico! Everything is fine with jumpers --- checked with a tester. The PCB is also normal (I checked everything several times). To exclude the display, connected the second. He has a 100% controller KS0108. However, nothing has changed, everything is the same. Maybe it was necessary to put a tick in front of the MCLR item in PICkit3?? I bought PIC18F25K22 in a trusted store. Just in case, I connected the first display to the DM-1 ... everything works. In general, I will continue to think ...
                  The second display bought in this store
                  https://www.aliexpress.com/item/2251801546541893.html?
                  Attached Files

                  Comment


                  • Just in case, here is PCB
                    Attached Files

                    Comment


                    • did you try VDI_S6B0108_P18F25K22.hex firmware? these displays are clones the built in controller says KS0107B or equivalent, yo need to power the pcb for the pic to be detected by pickit3 as you probably you did the first time as in the images you attached the first post

                      Comment


                      • Originally posted by waltr View Post
                        Roderico,
                        Shouldn't he see some activity on the Display control pins when resetting the PIC?
                        That was the only way I could think of to determine if the PIC is actually running code.

                        I was thinking he didn't have a good display but want to check that the PIC was running first.
                        yes he should see some activity although the display is not responding but he also needs to setup the oscilloscope properly and so on, but if the could flash the firmware without errors then the pic probably is fine, I was suggesting and easy test just to check the other firmware for these displays, if everything else is correct

                        Comment


                        • Originally posted by ArchibaldSTM View Post
                          Hello Roderico! Everything is fine with jumpers --- checked with a tester. The PCB is also normal (I checked everything several times). To exclude the display, connected the second. He has a 100% controller KS0108. However, nothing has changed, everything is the same. Maybe it was necessary to put a tick in front of the MCLR item in PICkit3?? I bought PIC18F25K22 in a trusted store. Just in case, I connected the first display to the DM-1 ... everything works. In general, I will continue to think ...
                          The second display bought in this store
                          https://www.aliexpress.com/item/2251801546541893.html?
                          for display 12864-2 you need VDI_S6B0108_P18F25K22.hex firmware, for display 12864TXD v1.0 try both firmwares S6B0108 and KS0108, you also need to reduce the contrast to see something in the display, in the image you posted it looks like it is at maximum and with that contrast you would not be able to see if it works or not

                          Comment


                          • Works! I flashed the firmware that you said. God... I never would have guessed in my life that this was the case... Roderico, I take off my hat and my respect! Thank you all, now I will make out in the case. P.S. Both displays work
                            Attached Files

                            Comment


                            • we had the same problem at the beginning with kroman1's displays the problem was that the clones use the opposite logic with CS1 and CS2 than KS0108 maybe because they are clones so that's why there are two firmwares for these displays S6B0108 and KS0108 (both identical except for CS1 and CS2), I'm very glad you made it work at the end

                              Comment


                              • Now I will know about it too. I will do it as an independent VDI prefix to Whites IDX and Tesoro Bandido. Thank you very much again!!!

                                Comment

                                Working...
                                X