Search Results

In many cases you need to run a task in a few seconds. The solution for such cases is to create a timer and then execute the task in the timer's Tick event. This is good for a single task. However if you need to run multiple tasks then it becomes difficult to maintain. This small class makes it muc
link: As you know, you can get a warning if you declare a Timer elsewhere than in Process_Globals. Here you declare a Timer in a sub; I suppose that the war
link: Starter.csu.CallSubPlus2(Me, "Sub_2", 1000, Array("Value 1", 0815)) 'run in one second CallSubPlus2 is sending an Array of Object. It i not an Array a
link: That's true. If you declare a global timer then it should be declared in Process_Globals instead of Globals. Otherwise, new timers will be created eac

Platform specific API -> Cross platform API: This is of course relevant when there is a cross platform API. Some developers have a misconception that the cross platform features have drawbacks compared to the platform specific API. Node / Pane / Button / ... -> B4XView Canvas -> B4XCanvas All kinds

CallSubPlus makes it a bit simpler. CallSubPlus - CallSub with explicit delay
link: You can never know exactly when the other side received the data. Add a short delay (one second) with CallSubPlus before you close the connection.

CallSubPlus is similar to a timer that fires once. CallSubPlus allows you to run a sub after a specified duration. Like a timer it doesn't block the thread. Blink example based on CallSubPlus: Sub Process_Globals Public Serial1 As Serial Private pin13 As Pin End Sub Private Sub AppStart Se
link: B4R rocks. Well done Erel!
link: Very nice Erel

DigitalWrite(True) 'lights up the green LEDs (there are places left) ' NB: The green LEDs will be lit by default at the start because there are 3 free places pinRedLED.DigitalWrite(False) 'turns off the Red LEDs (The parking lot is no longer full) Loc

Dear @Erel ; thanks for info. This function is very practical but not enough for fast drive. I listed underbelow. CallSubPlus("x",1,1) >> 150RPM CallSubPlus("x",2,1) >> 75RPM CallSubPlus("x",3,1) >> 50RPM CallSubPlus("x",4,1) >> 37RPM CallSubPlus("x",5,1) >> 30RPM CallSubPlus("x",6,1) >> 25RPM Th
link: Using delay to control the program flow is always a mistake. Use CallSubPlus instead.

B4R maintains a queue of tasks. CallSubPlus adds a scheduled task to the queue. The queue is processed whenever the single thread is free to process the queue. This means that you should expect some inaccuracies and changing the time unit will not really matter. Combining CallSubPlus with DelayMicro
link: For such accuracy you should combine CallSubPlus with DelayMicroseconds. Start with CallSubPlus with 2ms and then measure the actual time and use Dela
link: Thanks Erel for the advice, in this application I have a lot of communications (4 RS-485, 12 SPI, 6 I2C and 1 TFT over SPI) and I'm pushing the ESP32
link: Thanks for the pointers, I am modifying all the code so that the operating system manages more free time. I've removed the loops and am trying to run

callsubutils._plusimpl(callsubutils.java:153) at b4j.example.callsubutils._callsubplus2(callsubutils.java:167) at b4j.example.callsubutils._callsubplus(callsubutils.jav a:81) at b4j.example.main._dostep(main.java:124) at b4j.example.main._scan(main.java:290) at b4j.example.main._
link: There is no reason to use CallSubPlus. Change your code to: Sub DoStep Sleep(5) StepUp Sleep(5) StepDown End Sub
link: Sorry Erel, That doesn't work. The For Next is: For stepsdone = 0 To stepstodo -1 Step 1 DoStep Next . Sub DoStep Sleep(5) StepU

You should use CallSubPlus2 CallSubPlus2
link: Look at Thread ' CallSubPlus - CallSub with explicit delay' https://www.b4x.com/android/forum/threads/b4x-callsubplus-callsub-with-explicit-delay.6087
link: I don't think this is the explanation for the issue. In callSubPlus you can pass whatever you want. I think you mixed write eeprom parameters. Look at
link: thanks for your reply's. i enclose a screenshot of the intelisence in my B4R IDE, about callSubPlus, you can see it is demand a "tag as Byte". how e

Solucionado, el error es que CallSubPlus pasa un parámetro y en la rutina es necesario recolectar dicho parámetro. CallSubPlay("Rutina_Nombre",ms,etiqueta) .... Private Sub Routine_Name (Etiqueta como byte) Muchas gracias
link: Hello, very good and delighted to be with you again. I am making a program in which I use RS485 communication with a transmission Enable Pin. To Trans

Powered by ColBERT