Forum Replies Created

Viewing 15 posts - 1 through 15 (of 37 total)
  • Author
    Posts
  • AmirFAmirF
    Moderator
    Post count: 37

    Hi Tom,

    First of all, in FCG1.0.1 and FCG1.0.0, the LSO feedback signals are not functional. This was due to a hardware issue that is fixed in the FCG2.0 version. So, the LSO feedback pins will appear to be stuck high in your hardware, even in case of thermal shutdown.

    Second, there is another known issue on FCG1.0 in which the current measurement pins (ADC pins) on the HSO7,HSO8, HSO9, and HSO10 are not functional. However, the rest of the HSOs are connected correctly and are functional. Please be advised that the current reading pins on HSO channels are just reflecting the amount of current draw and you can’t use them to detect short to GND or short to VBATT.

    Please take a look here for the list of know issues we fixed for FCG2.0. Revisions and Known Issues

    I took a look at your code. Your description is accurate to what I observed. However, I noticed that the data store memory block of “cfg_HSO_FBEnable” was connected to the wrong Dio_Write channel. You can fix that and read the HSO11 current measurement, when cfg_HSO_FBEnable is set to High.

    Cheers,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hi,

    Please see the following page for all the possible credentials needed for SSH connection to the MPU.

    You do not need any initial setup for connecting for the first time.
    Also please make sure that the Ethernet pins on your harness match the datasheet on the website.

    Thanks,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Craig,

    I tested and looked up the source of this issue. We found out that the CM4 is not meant to have voltage on the GPIO pins before booting up. This is causing the MPU to show unwanted behavior and not function correctly.

    There is a workaround for this issue, and that is if you can switch the pull-up on MPU DIs after the MPU is booted up. You can either do it manually using the dip switch or use an external relay to switch the pull-up switch.

    Thanks for your patience, and let me know if I can help you with anything else.

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Craig,

    I did test on my FCB1.2 and I am seeing the same behavior as you described. Let me investigate more and get back to you in a couple of days.
    Thanks,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hello Joephi,

    Unfortunately, you don’t have access to UART on the header pins of FCG.
    There is an RS232 signal pair exposed on the header pins, but in the default image of the MPU, SSH through UART is disabled. You are welcome to give it a try, but I doubt that it will resolve the issue.
    The OS flashing through the header will be available from FCG2.2, which will be available soon.
    You can send the unit back to us to reflash the OS on the MPU. Please use the RMA form on the website.

    Thanks,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hi OB_DC,
    Unfortunately, Wake on CAN and Wake on LIN are not available on FCG_v1.
    This feature will be available on FCG2.2, which is the next revision that will be released soon.

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Craig,

    Sorry for my delayed answer.
    I investigated the last photo you sent and noticed a diode is missing on your board. This is the diode that is responsible for pulling up the MPU_DIs.
    So, let me know if you are comfortable with doing the rework or if you want to send the device back, and we can fix it for you.
    If you decide to do the rework, here is the simplified instruction:
    1. Please probe both pads of the diode. You need to verify that one pad has V_Batt on it, and the other pad is connected to the dip switch.
    2. The simple fix is to directly pour solder on pads and short them to have V_BATT for pull-up voltage. But remember, you will have a back-powering issue. (If VBATT is off and you put voltage on DIs, you can wake up the device)
    3. The clean, but harder fix is to populate the diode on that footprint. (MPN: BAS516,135) Anode to VBATT and Cathode to dipswitch.

    Let me know what your decision is and how I can assist you further.

    Amir

    Attachments:
    You must be logged in to view attached files.
    AmirFAmirF
    Moderator
    Post count: 37

    Where are you measuring the 1.5V on DI? Is it measuring 1.5V on the external screw terminal pin?
    Please make sure you activate only one of the Pull dip switches at any time.
    Please also note that the dip switch controls the pull for the whole MPU digital input terminal. So, all of them can be set to either pull down or pull up. In case you need different pulls on MPU DI, you should add them externally.

    Attachments:
    You must be logged in to view attached files.
    AmirFAmirF
    Moderator
    Post count: 37

    The pull up voltage on MPU DI will be the same as the V_BATT. So if 12V is connected to V_BATT, the pull up will be 10K ohm to 12V.
    This is the same as DI pull ups for MCU.

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Craig,
    There has been an issue with the setup of RS232/RS485 on FCB1.2. However, I remember we did apply a fix on the FCB unit that was sent to you. So on your FCB1.2, the RS232 is active by default. You don’t need to change any dip switches on the board to make it available.(I have also attached a picture of that area of the board.)
    Unfortunately, RS-485 won’t be accessible because of the hardware issue on FCB1.2. Sorry about that.
    For RS232 communications on RPi-CM4, you can use the UART0 on pins 51 and 55.
    Thanks,
    Amir

    Attachments:
    You must be logged in to view attached files.
    AmirFAmirF
    Moderator
    Post count: 37

    Hi Mathew,

    The control pilot pin on FCG is muxed with DI12(pin B45).
    Also, ADC12(pin A26) acts as a Proximity Pilot with a 1/2 voltage divider ratio.
    You don’t need any activation for either pins, which are activated by default.

    Cheers,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Nikhil,

    Thanks for your patience.
    I would be able to have a more reasonable understanding if you could perform the voltage difference test I mentioned earlier.
    Please redo the fault scenario and then measure the voltage difference between the GND_IN pin(J2-5/6) and the big GND pads on the PCB, or the enclosure itself if it is closed.

    Thanks,
    Amir

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Nikhil,

    Thanks for the detailed description of the issue.
    I still have some questions regarding the issues happening. The answer will clear up the problem for us.
    You stated that the LSOs are driving the solenoids. How much is the total current draw for the LSOs from all the LSOs?
    If the overall current draw from all LSOs is 20A or more, can you measure the voltage difference between the GND_IN pin(J2-5/6) and the big GND pads on the PCB, or the enclosure itself if case is closed, when the FCG is in a faulty state?
    Are the HSOs also driving inductive loads? Do you have an estimation of the inductance?
    Have you utilized external flyback diodes in your setup?

    AmirFAmirF
    Moderator
    Post count: 37
    in reply to: FCG Setup #19188

    Hi Mobina,

    FCG doesn’t support virtual here.
    You can have virtual here only on FCS controllers.

    AmirFAmirF
    Moderator
    Post count: 37

    Hi Kantesh,

    What is the signal you are reading with DI12?
    Please keep in mind that low-level threshold on DI12 is 1.5V.
    Have you tried the sample code on the website?
    Let me know what are the exact upper/lower bands, frequency, and duty cycle of the signal you are trying to read on DI12?

Viewing 15 posts - 1 through 15 (of 37 total)