FluidNC and MKS TinyBee

Software / Firmware GRBL
21

Ok, I think I figured it out…

I used the adapter board with this wiring:

MKS TinyBee With 24V Laser (24V input)

image
image1920×665 168 KB

The FluidNC configuration is:

Laser:
  pwm_hz: 5000
  # on 3D Touch connector (has pdwn + PWM)
  output_pin: gpio.2:high:pd
  s0_with_disable: true
  disable_with_s0: true
  tool_num: 0
  speed_map: 0=0.000% 1000=100.000%
  off_on_alarm: true

I’m printing a daughter board support for teh LR3 case to put the adapter baord inside…

Only problem I have left now is that the laser briefly turns ON when I power on the main board…
I may relocate the switch from the adapter board to shut the power down manually, but it’s a bit impractical…

22

That may be just the signal line ‘floating’ during the boot sequence… or your data pin is actively being driven by the uP. You could try a (say) 10k resistor between pins 1 and 3 on the 3D Touch socket…

Having said that, I see you already have a pull down configured on the output pin so I guess a physical resistor pull down won’t help…

23

It may do. Some Micros are really bad about keeping control of their programmable IO during startup. It’s usually not a full low-impedance output mode that they go through, so adding a bit more load to pull the pin to the correct state would help, especially if the pull-down is software configured and potentially not enabled yet during the period that the pulse is occurring.

1 Like
24

Fun thread. Have any of you found a resource mapping the EXP1 connector to gpio pins? I know which pins are on it but don’t yet know which one is which. Not looking forward to figuring it out the hard way.

Edit: of course as soon as I posted I finally found it down near the bottom of:
https://raw.githubusercontent.com/makerbase-mks/MKS-TinyBee/main/hardware/MKS%20TinyBee%20V1.0_003/MKS%20TinyBee%20V1.0_003%20SCH.pdf

-dave

25

Looking at the schematic, the Schottky diodes are providing electrostatic protection to the data line, and due to leakage current they are effectively a voltage divider circuit …so there would be half Vcc on that data line until it is either driven high or low… I would think a pull down resistor might do the trick to resolve the problem. Give it a try and let us know if it works.
image

26

I’d gladly do, but I’m a bit at loss when it comes to electronics (more of a software guy…)
Is it as simple as soldering a resistor on the signal wire? if so, what value?

27

Did any of you experimented ‘COMX failed to connect: Failed to connect to ESP32: Timed out waiting for packet header’ during the flash process of this board when trying to install the wifi bat?

28

almost anything really… try a 10K between the signal and ground of the 3d_touch connector

29

If you’ve got access to through-hole resistors, it can sometimes be enough to trim the legs and poke them into the back of the connector so that they wedge in place between the plastic and the metal of the crimp terminal. The current through the pull-down resistor is miniscule, so this can be a good way to temporarily test a fix.

10K is a decent starting point, as Mike says.

30

I’ll try that, I think I still have a bunch of through hole resistors somewhere… :slight_smile:
Thanks for the explanation

1 Like
31

Maybe a silly question but I’d like to connect to a vfd using rs485, can I map the lcd rxd and txd to connect to a modbus adapter and connect my vfd this way?

32

Did you fix it? I have the same problem. :smiling_face_with_tear:

33

Hi, how many input pins exacly this board have?
22, 32, 33, 34(if disable sd card?), 35, 36. Did i miss something ?

34

Try this: edit your config on pc, disable all (all axies) hard limits (hard_limits: false). Change confing name to the same Config/Filename in “bricked” board. Delete “bad” config frome board and upload edited one from pc. Restart bee